Date: Fri, 30 Jun 2000 21:38:28 -0500 (CDT) From: Mike Meyer <mwm@mired.org> To: cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/contrib/isc-dhcp - Imported sources Message-ID: <14685.22948.963677.663648@guru.mired.org> In-Reply-To: <bulk.18338.20000630183419@hub.freebsd.org> References: <bulk.18338.20000630183419@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> From: Will Andrews <andrews@technologist.com> > On Fri, Jun 30, 2000 at 06:28:13PM +0100, Brian Somers wrote: > > No I didn't, I used su -m :-) > That requires being in the wheel group, which requires root.. :^) I typically boot systems single user after the install to apply final touches. The default shell then is "/bin/sh". Changing roots shell at that point would avoid the problem. Of course, my preferred shell is bash, and I'm not going to make that root's shell (nothing outside of core). So the question is moot - I use "su -m", or just su and then exec bash. I'm never in the shell long enough to *care* what it is. I'm just curious as to what the point of changing it is. If you're the only, make it part of your post-install script. With multiple admins, make the script install aliases in .cshrc (or .profile, if you insist on changing it) that source different scripts for each admin so they can go to their favorite shell with a single command after doing an su. <mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14685.22948.963677.663648>