OK, thanks. BTW that's the worst doA,doB,doC..writeup that I've seen
lately, considering that rPi's declared aim is to 'educate the kids'.
--
And by example, here's the 'mental model' approach which could educate:
by watching the boot-log, it's seen that 'login' happens right after the
hardware has been setup. `pstree` shows the heirarchy of processes.
--
And it's known that 'init' is the BOSSman process.
Apparently the instruction-sheet that `init` uses is 'inittab'.
These instructions are in a tree-format or multi-dimensional-array,
where 2 dimensions are: run-level & process.
--
Apparently most most gate-way processes: that allow entry to other
processes need `login`; like getty.
So some process which does NOT need `login` must be found/used.
--
Because the tree/matrix of processes is complex/canOworms,
[slak13, Lenny, Etch, FC1 all have different format/syantax]
problems lurk. Just reading the scripts' comments exposes the black-art
nature of this part of *nix.
--
Because I operate from different locations, and just transfer my IDEs,
the inittab-controlled-pid-sequence is brittle.
Could the <repeat spawning: wait 5 minutes> error be caused by the dead
PS2-mouse being replaced by a USBone?
--
BTW I tested/confirmed the google-hit's PRINCIPLE on Etch, but am not too
confident that rPi will work when I can get it to a 'display'.
DoA, doB, doC is only good for the herd who've got the SAME model that
they all bought from Wallmart last week.