On 25/01/10 13:53, Allan McRae wrote:
On 25/01/10 12:23, Tavian Barnes wrote:
2010/1/24 Dan McGee:
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
On 25/01/10 12:23, Tavian Barnes wrote:
2010/1/24 Dan McGee:
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
2010/1/24 Dan McGee :
>
> You probably want a login shell, e.g. /bin/bash -l
>
I'd go with (untested):
#!/bin/sh
exec linux32 /bin/bash "$@"
--
Tavian Barnes
On Sun, Jan 24, 2010 at 7:49 PM, Allan McRae wrote:
> I am trying to seamlessly run an x86_64 kernel on my i686 machine. I have
> enough aliases that most things work right (prefixing with linux32), but
> bash can not handle setting e.g. "./configure" as an alias and there is
> always something I
I am trying to seamlessly run an x86_64 kernel on my i686 machine. I
have enough aliases that most things work right (prefixing with
linux32), but bash can not handle setting e.g. "./configure" as an alias
and there is always something I have missed.
So, I came up with a cunning plan... Crea
5 matches
Mail list logo
