On 7/7/05, Tao Chen <[EMAIL PROTECTED]> wrote: > On 7/7/05, Sunil <[EMAIL PROTECTED]> wrote: > > I remember there was a "library dependency" argument against changing the > default shell for root. > However at least in Solaris 10: > > # ldd /bin/sh > libgen.so.1 => /lib/libgen.so.1 > libsecdb.so.1 => /lib/libsecdb.so.1 > libc.so.1 => /lib/libc.so.1 > libnsl.so.1 => /lib/libnsl.so.1 > libcmd.so.1 => /lib/libcmd.so.1 > libmp.so.2 => /lib/libmp.so.2 > libmd5.so.1 => /lib/libmd5.so.1 > libscf.so.1 => /lib/libscf.so.1 > libdoor.so.1 => /lib/libdoor.so.1 > libuutil.so.1 => /lib/libuutil.so.1 > libm.so.2 => /lib/libm.so.2 > > I guess the argument it's no longer true? >
taken from : http://www.blastwave.org/howto.html Solaris 10 is different. Solaris 10 has a default Bourne Shell /sbin/sh that is not statically linked anymore. This was done intentionally when the single/multi threaded process model was unified and the statically linked libc was removed. Solaris 10 commands in /sbin should only link with things in /lib. There are symlinks in /usr/lib to /lib for some libraries for backwards compatibility reasons. In fact, Solaris 10 is so smart that both su and login will fall back to /sbin/sh if the shell you specify in /etc/passwd for root can not be executed for some reason. What I am saying here is that you can change root's shell in Solaris 10 and still sleep well at night. Dennis _______________________________________________ opensolaris-discuss mailing list [email protected]
