Am 2006-06-12 08:54:22, schrieb Cameron Simpson:
> The bash scripts are already broken. Nobody should write for bash and use a
> "#!/bin/sh" script header line. That is really bad. Saying "#!/bin/sh" means
> you expect a POSIX capable Bourne shell (and possible slightly less), but
> certainly no more. Dash is supposed to be POSIX compliant.
> It would have been far better to fix the broken scripts, as they will
> just cause you trouble AGAIN on another system where /bin/sh is not
> bash.
Not realy right, because in my BASH scripts I have #!/bin/bash.
I have found that the problem was, that I run BaSH on the console
and use startx. The scripts in startx are using /bin/sh which is
a symlink to /bin/dash. Which mean, I have allready lost. Since
I source some scripts (no shebang availlable) the scripts do not
more work.
Since fvwm use Exec with /bin/sh by default, I have a DaSH. Now
even if I have the #!/bin/bash in my scripts, my environement was
trashed...
It seems, that: Exec program
span a dash, which execute the program which has bash. And bash
is not a login shell.
How can someone solve such things?
Oh, puting
#!/bin/bash -l
in the script run a login shell and all is working fine.
(but its crap)
Greetings
Michelle Konzack
--
Linux-User #280138 with the Linux Counter, http://counter.li.org/
##################### Debian GNU/Linux Consultant #####################
Michelle Konzack Apt. 917 ICQ #328449886
50, rue de Soultz MSM LinuxMichi
0033/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com)
