Date: Tue, 11 Nov 2008 08:55:37 +0100 From: Mel <fbsd.questions@rachie.is-a-geek.net> To: freebsd-questions@freebsd.org, Polytropon <freebsd@edvax.de> Subject: Re: root /etc/csh Message-ID: <200811110855.37855.fbsd.questions@rachie.is-a-geek.net> In-Reply-To: <20081111063854.fcad80f2.freebsd@edvax.de> References: <20081110110805.GK1302@obspm.fr> <4918CE42.3050504@ccstores.com> <20081111063854.fcad80f2.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 11 November 2008 06:38:54 Polytropon wrote:
> On Mon, 10 Nov 2008 16:13:54 -0800, Jim Pazarena <fquest@ccstores.com>
wrote:
> > 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 ;)
--
Mel
Problem with today's modular software: they start with the modules
and never get to the software part.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200811110855.37855.fbsd.questions>