-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2008-01-08 at 06:35 -0700, Bill Anderson wrote:
Bill Anderson wrote:
Bourne shell compatibility. You might also note that under Linux it is /usr/bin/sh, /usr/bin/ksh, and /bin/bash.
No, not really:
cer@nimrodel:~> l /bin/sh /usr/bin/sh lrwxrwxrwx 1 root root 4 2007-11-03 02:13 /bin/sh -> bash* lrwxrwxrwx 1 root root 9 2007-11-03 02:13 /usr/bin/sh -> /bin/bash*
cer@nimrodel:~> l /bin/ksh /usr/bin/ksh lrwxrwxrwx 1 root root 16 2007-11-03 16:07 /bin/ksh -> /lib/ast/bin/ksh* lrwxrwxrwx 1 root root 16 2007-11-03 16:07 /usr/bin/ksh -> /lib/ast/bin/ksh*
cer@nimrodel:~> l /bin/bash /usr/bin/bash ls: cannot access /usr/bin/bash: No such file or directory - -rwxr-xr-x 1 root root 604040 2007-09-22 00:16 /bin/bash*
My original comment about /bin being linked to /usr/bin applied only to Solaris, AIX, and HPUX. Yet, all the examples of why I am wrong are from Linux. If you were on a Unix system, there would not be a /lib/ast/ksh, as KornShell is in /usr/bin. The other difference you will notice is that AIX now has bsh for Bourne Shell. Those who use Unix also notice the emphasis on hard links in Unix versus symbolic links in Linux.
You said: ]>>>> Bourne shell compatibility. You might also note that under Linux ]>>>> it is /usr/bin/sh, /usr/bin/ksh, and /bin/bash. Notice you speak in this paragraph about Linux, and that's the one I was comenting about. Also, notice that symbolic links are needed to cross partitions: that's why they are preferred sometimes (specially for files in /usr) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHg36PtTMYHG2NR9URArzPAKCWFTJRgelgnmOADKSmFsgONrsl+gCferTq wHIgFzXl1EiIEeflwjV3jts= =PUeG -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org