Bill Allombert <[EMAIL PROTECTED]> writes: > I am of two mind with that. On the positive side it removes the promise > to the users that the system works with _any_ POSIX-compliant /bin/sh, which > is something we never actively tested. > > On the other hand, it more or less mandates that /bin/sh is /bin/bash > (because /bin/sh is not a config file, and baring policy authorization, > users are not supposed to change symlinks in /bin). This looks like a > regression a regression in user choice: I expect there are sufficiently > many Debian installation where /bin/sh is /bin/dash for us to claim > that /bin/sh pointing to /bin/dash is a supported and tested configuration.
The /bin/sh should really point to a reference shell that is accepted for the release builds (like /bin/dash). It's is unfortunate that in the distant past someone made a decision to simply soft link it to bash. I suppose it is impossible to make an etch+1 change to remove the /bin/sh => /bin/bash coupling. Jari -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
