> How to make trivial things looking complicated ?? > > Two linear steps: > #0) A dynamically linked bash should go into > /sbin/bash (or, better, /sbin/sh)
I said the former of those already (it ought to be in /sbin/bash). Expect serious opposition to any notion of putting it in either /sbin/sh or /usr/bin/sh (see below). > #1) its dependencies go into /lib. This is already the case - do an ldd /usr/bin/bash on Solaris 10 or later, and you should see all the libs are in /lib. > Both are inside the rootfs and are always accessible. > > So what? > The old bourne shell is "slightly" outdated. > Has too many restrictions in virtually every aspect > (i.e. limited language syntax, maximum length of > command line very short, no rc-file, no history, no > cmd-line-editing). > > I can name many concrete examples, where scripts do > break: IF /bin/sh is _not_ bash. Scripts that require /bin/sh == bash don't already exist on Solaris. They should remain in the hell that spawned them, or have the first line #! /usr/bin/bash and any other changes needed to free them of that evil assumption. Or alternatively, they should be rewritten to work using the least common denominator of /bin/sh functionality among various vaguely Bourne shell like variants and clones. That is, they're already non-portable, and that's not _our_ problem. If you want to blame someone, blame the POSIX folks for not having a magic non-pathname token to use with #! to get a real (i.e. POSIX compliant) shell (which arguably bash isn't entirely, although it's probably closer than Bourne). Scripts that would be broken by /bin/sh == bash already exist on Solaris. That's enough reason to forbid that change, IMO. This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
