Follow-up to SUMMARY: Using other than Bourne shell for root on Solaris 10

I said that on Solaris 10, /sbin/sh was still statically linked.

I'm wondering:

On a Solaris 9 machine:
# ldd /sbin/sh
ldd: /sbin/sh: file is not a dynamic executable or shared object
# ldd /usr/bin/bash
        libcurses.so.1 =>        /usr/lib/libcurses.so.1
        libsocket.so.1 =>        /usr/lib/libsocket.so.1
        libnsl.so.1 =>   /usr/lib/libnsl.so.1
        libdl.so.1 =>    /usr/lib/libdl.so.1
        libc.so.1 =>     /usr/lib/libc.so.1
        libmp.so.2 =>    /usr/lib/libmp.so.2
        /usr/platform/SUNW,Sun-Fire-V210/lib/libc_psr.so.1

I just got my hands on a Solaris 10 machine:

# ldd /sbin/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
# ldd /usr/bin/bash
        libcurses.so.1 =>        /lib/libcurses.so.1
        libsocket.so.1 =>        /lib/libsocket.so.1
        libnsl.so.1 =>   /lib/libnsl.so.1
        libdl.so.1 =>    /lib/libdl.so.1
        libc.so.1 =>     /lib/libc.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


So, it seems that /sbin/sh is now dynamically linked.

Though the safest would still be to put the shell into .profile, I guess.
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers