Re: itp: static bins / resolving static debian issues
On Tue, 24 Aug 1999, Michael Stone wrote:
> That wasn't the point. Did you try what I wrote? The point was that
> bash's return code is the return code of the program last executed by
> bash--it's not necessarily something determined by bash itself. You
> can't rely on the content of bash's return code because you have *no*
> control over what I run in my bash session, or what it might return. And
> no, it's not better to be safe than sorry if your idea of "safe" has the
> possiblity of starting *two* shells when I use root's shell.
If the launcher is a C program, then it can check errno after the
unsuccessful launch of bash. For that matter, a C program might be able to
exec bash then exec sash, although I haven't tried this technique.
Reply to: