Mailinglist Archive: opensuse-factory (689 mails)

< Previous Next >
Re: [opensuse-factory] why are raw scripts forced into /bin/sh instead of user's shell (a Suse patch to bash)
On Fri, Mar 01, 2013 at 10:47:10AM +0100, Andreas Jaeger wrote:
El 2013-02-27 a las 22:52 -0600, Larry Finger escribió:
On 02/27/2013 09:59 PM, Linda Walsh wrote:

Why do you think this is SUSE only. Every distro has a default shell, which
is what you get when you do not specify the shell to use.

/bin/sh is a link to a shell. Linda, find out which it is in your system.

You miss the point. The upstream bash invokes script using the same
name under which it has been started:

/* The name of this shell, as taken from argv[0]. */
char *shell_name = (char *)NULL;

(open?)SUSE patch forces script to always run with /bin/sh

There must be some reason why it was changed. I would be interested to
know it too.
the patch changing this is bash-3.2-longjmp.dif.

and the changes entry is:
Wed Mar 9 12:00:48 CET 2011 - werner@xxxxxxx

- Avoid siglongjmp, compare with
use temprary solution from Chet

Chet is the upstream bash author.

Might need to be revisited...

Sorry but this is wrong. The change for siglongjmp() versus set longjmp()
has nothing todo with this patch. The patch belongs to memory corruption
ahd happen with several bug reports like:

that is that after the siglongjmp() the bash had showed memory corruption.
This seems to be fixed in bash 4.2 ... nevertheless it could come back
again as memory management together with setjmp()/longjmp() or
sigsetjmp()/siglongjmp() has to managed thorough to not run into the
same problems as in the bugs above.

This is the only reason why this patch is still alive. And yes I've read
the thread


"Having a smoking section in a restaurant is like having
a peeing section in a swimming pool." -- Edward Burr
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >
List Navigation