Date: Tue, 26 Oct 1999 13:38:44 -0500 (CDT) From: Marius Strom <marius@alpha1.net> To: Bill Fumerola <billf@chc-chimes.com> Cc: Roger Marquis <marquis@roble.com>, freebsd-isp@FreeBSD.ORG Subject: Re: root access problem please help. Message-ID: <Pine.LNX.4.10.9910261337180.10433-100000@swedishchef.alpha1.net> In-Reply-To: <Pine.BSF.4.10.9910261336100.13675-100000@jade.chc-chimes.com>
next in thread | previous in thread | raw e-mail | index | archive | help
True, however, even with libraries and dynamic binaries on the same FS, it's trouble. I had a linux system (yes, yes..) that a co-admin was trying to RPM upgrade the libc (yes, another bad move, but it wasn't me! =]) and broke it. Voila, statically linked sh worked, but I couldn't cp, mv, ch(mod|own). sash(1) is your friend. -- Marius Strom <marius@alpha1.net> Professional Geek/Unix System Administrator Alpha1 Internet <http://www.alpha1.net>; http://www.marius.org/marius.pgp 0x5645C228 In theory, there is no difference between theory and practice... ...In practice, there is a big difference. On Tue, 26 Oct 1999, Bill Fumerola wrote: > On Tue, 26 Oct 1999, Roger Marquis wrote: > > > > For God's sakes: If you made the dumb move of making a dynamically linked > > > binary your root shell you're going to have to pay consequences. > > > > It would only be a dumb move if neither the shell nor the linked > > libraries were on the root filesystem. I've been using dynamically > > linked tcsh and bash as the root shell for over a decade with no > > problems. Splitting /usr onto a separate filesystem, however, can be a > > dumb move if you're not restricted to 1GB drives. > > Obviously. I'm refering to the plethora of users who have the typical > /, /usr, /var, swap install, and the plethora of users who > > # cd /usr/ports/shells/bash2 && make install clean > # chsh > [...] > # <do something stupid that borks their /usr> > > And then file a PR. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.10.9910261337180.10433-100000>