Mike Bird <[EMAIL PROTECTED]> writes: > On Mon February 11 2008 09:08:24 Russ Allbery wrote:
>> So switch your /bin/sh back to bash when the Release Notes tell you >> about the change and move on with your life. That's why it's >> configurable. > Why force millions of Debian users to do this? I disbelieve in your statistics. > Furthermore, some will ignore the release notes or misread them or > misunderstand them and data loss will result. I disbelieve in your alarmism. > Why inflict all this pain - all of which will reflect in bad karma for > Debian - when it's so easy for Debian to do the right thing - use > #!/bin/sh.minimal for Debian scripts and not change what users have come > to expect of /bin/sh. I disbelieve in your definition of "the right thing." Maybe it's because I came from a Solaris background originally, where anyone who thought /bin/sh was bash was laughed out of the room, but treating /bin/sh as always being bash is one of those things that is most closely associated with people who have no idea what they're doing and who have never looked at anything that isn't Linux. I don't have a tremendous personal interest in enabling that sort of short-sightedness when there are real gains to be had in using other shells, particularly when Debian has never guaranteed that /bin/sh is bash. All the world is not a VAX. When we upgrade gcc to a newer version that no longer compiles broken code, we don't cripple gcc to maintain its backward compatibility with broken code. We tell people to fix their broken code. This is similar, and we provide a *trivial* workaround for people who aren't ready to, aren't able to, or don't want to. I run Debian on hundreds of production servers for a major site, including with random vendor applications and random user shell scripts, and expect that when Debian switches default shells, we will too. If there are problems, we'll fix them. It's really not that hard. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
