Date: Sun, 11 Jul 2004 01:08:34 -0700 From: Henrik W Lund <henrik.w.lund@broadpark.no> To: Kristian Holdich <kjholdich@yahoo.co.uk> Cc: freebsd-questions@freebsd.org Subject: Re: Newbieish Desktop Questions Message-ID: <40F0F582.9060609@broadpark.no> In-Reply-To: <1089468142.26300.46.camel@slide.hopto.org> References: <40F00DDD.7772.12F6CBB@localhost> <1089468142.26300.46.camel@slide.hopto.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kristian Holdich wrote: >On Sat, 2004-07-10 at 14:40, Kjell Midtseter wrote: > > >There's one glaring problem with that, if for some reason you need to go >into single user mode under FreeBSD's default slicing scheme root wont >have a shell as /usr isn't mounted. It's always good practice to keep >the shell root uses in /sbin or /bin. > >You can change the shell root, or any other user uses by using chpass >also, and so long as the shell is in /etc/shells it will be valid. > >I was actually more interested in understanding whether any critical >scripts would start barfing if the shell got changed, I know on Solaris >I got into the habit of keeping root using /sbin/sh. > > As far as I know, you're prompted for a root shell whenever you enter single user mode anyways (I am, at least, and I use /bin/csh for root normally. I'm still prompted every time). So, whatever shell you use for root in multiuser mode shouldn't matter, as single user mode is a different kettle of fish altogether. Granted, getting into the habit of using one shell for root in multiuser, then having to switch into an unfamiliar shell for single user could complicate work slightly... As for vital scripts failing, I doubt it. Unless you start symlinking like crazy, things should work fine, as scripts starting with #!/bin/sh will always use /bin/sh and so on (so unless /bin/sh is a symlink to /usr/bin/wish or some such exotic setup, nothing will barf. :-) -Henrik W Lund
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40F0F582.9060609>