On Tuesday 11 November 2008 06:38:54 Polytropon wrote:
> On Mon, 10 Nov 2008 16:13:54 -0800, Jim Pazarena <[EMAIL PROTECTED]>
> > isn't the "main reason" because other shells may reside on a filesystem
> > which isn't necessarily mounted in maintenance/single user mode? Or,
> > libraries for the same?
> At least, it's a valid reason. When in trouble, the system just
> mounts / as ro where /bin/sh (the system's standard scripting
> shell) and /bin/csh (its standard dialog shell) are available.
> Bash may be on another partition that's not mounted yet, so no
> maintenance access would be possible.
In single user mode, no login is done at all and the path to the shell is
asked for. When a system comes to halt at boot, it will go to single user
mode. If it doesn't make it there, then not much is lost anyway by rebooting
and pressing 4 when chuck greets you.
The problem is lies with remote logins through means of ssh and being unable
to change to root, to - for example - change the shell ;)
Problem with today's modular software: they start with the modules
and never get to the software part.
email@example.com mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"