On 25/01/10 13:53, Allan McRae wrote:
On 25/01/10 12:23, Tavian Barnes wrote:
2010/1/24 Dan McGee<dpmcgee@xxxxxxxxx>:
You probably want a login shell, e.g. /bin/bash -l
Thanks. That fixed the PATH issue I was having but it turns out that was
not my real issue... see below
I'd go with (untested):
#!/bin/sh
exec linux32 /bin/bash "$@"
This fixes my real issue but then the issue with my path remains.
<snip>
Both fix something so why did I not try the combination...
This works:
#!/bin/bash
exec linux32 /bin/bash -l "$@
Allan
