Filippo
10-22-2002, 05:35 PM
Oh stupid stupid stupid!
I installed and ran sb as root, then forgot about it and got off shell w/o shutting it down first.
I could not get to root shell again, I could not kill the process as user (duh!) and I assumed a user level shutdown would do anyway.
Wrong. Shutdown stalled.
On restart, boot failed due to missing inittab.
I guess I made inittab dirty by running sb, which I imagine writes into inittab that it has to autostart on boot.
Then, the messed up shutdown did not let the change be committed to, and the file marked clean.
I can't imagine inittab being totally wiped out...
QUESTIONS:
1) Does sb indeed affect inittab?
2) Is there anything about sb that should hijack root access?
It may look like a pair of my dumbaceous question,
please bear w/ me,
I've just started learning how to live off the command line
and to catch my food barehanded...
TIA from Milano
Filippo
I installed and ran sb as root, then forgot about it and got off shell w/o shutting it down first.
I could not get to root shell again, I could not kill the process as user (duh!) and I assumed a user level shutdown would do anyway.
Wrong. Shutdown stalled.
On restart, boot failed due to missing inittab.
I guess I made inittab dirty by running sb, which I imagine writes into inittab that it has to autostart on boot.
Then, the messed up shutdown did not let the change be committed to, and the file marked clean.
I can't imagine inittab being totally wiped out...
QUESTIONS:
1) Does sb indeed affect inittab?
2) Is there anything about sb that should hijack root access?
It may look like a pair of my dumbaceous question,
please bear w/ me,
I've just started learning how to live off the command line
and to catch my food barehanded...
TIA from Milano
Filippo