Mailinglist Archive: opensuse-factory (689 mails)

< Previous Next >
Re: [opensuse-factory] Re: why are raw scripts forced into /bin/sh instead of user's shell (a Suse patch to bash)
  • From: Anders Johansson <ajh@xxxxxxxx>
  • Date: Mon, 04 Mar 2013 08:01:17 +0100
  • Message-id: <13113942.lZDH96VkBB@panic>
On Friday 01 March 2013 13:58:11 Linda Walsh wrote:
Carlos E. R. wrote:
Hash: SHA256

El 2013-03-01 a las 10:48 +0100, Joerg Schilling escribió:
If /bin/sh may be linked to different shells, you need to know that many
scripts on Linux are not Shell complatible as they depend on bashisms.

If they do and the shebang does't point to bash, they have to be
reported in bugzilla, IMO.

Yeah, someone tried to report a global cleanup bug for that,

But it ended up on the "won't fix" list -- for reasons Guido mentions --
The best he was able to manage was an rpmbuild-advisory message.
Apparently making it a build-error didn't go over too well. ;-)

None of this solves the current problem of not executing the
scripts under the user's shell.

Really Linda, unless you have a #! line in your script specifying which shell
you want/need for it, you are relying on some undocumented effect that just
happened to work in the past. This is not a good way of maintaining a system.

If you want to be sure which script is used, use the documented way of doing
that and start your script with #!/bin/bash, anything else is just relying on

And saying "but it used to work" or "it works on system xyz" is just saying
"but I want my luck to continue"

If the default root password in the past was foobar and you never set it, and
relied on its continuing to be foobar in future, and it then changed, would
you also file a bug report against that?

Use the feature available for determining which shell is used

To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >
List Navigation
Follow Ups