Kevin,
I am glad to see it worked for you. When I tried to do this manually
from the initrd shell I would run:
chroot /mnt/sysimage /bin32/bash
and it would still fail. I thought by specifying the command in addition
to the target you would bypass the need for the SHELL variable.
On Fri, 2004-02-20 at 16:14, Kevin Murphy wrote:
> On Fri, 2004-02-20 at 15:57, Jeff Johnson wrote:
> > This is interesting. I tried making a /bin32 directory on the golden
> > client image and putting a 32-bit bash and other binaries in there but
> > could not make it work. The chroot from ramdisk into the newly imaged
> > tree would always die. Even once the chroot failed and the script drops
> > into shell I have been unable to manually execute a chroot from a 32-bit
> > PXE kernel environment into the 64-bit tree. Even when there was a
> > 32-bit bash in a /bin32 directory in the new image with the 32-bit
> > binaries.
> >
> > What did you use for a 32-bit shell?
>
> I installed bash into the 32 bit binary directory.
>
> The problem is that if you don't specify the SHELL, it'll try to run
> /bin/sh, which is a 64 bit binary.
>
> chroot will inherit the environment from the parent shell, so you have
> to add something like
>
> export SHELL=/bin32/sh
> export PATH=/bin32:$PATH
>
> before the chroot in the autoinstall script.
--
Jeff Johnson <[EMAIL PROTECTED]>
Western Scientific, Inc
http://www.wsm.com
Powerful cluster computing, server and storage solutions.
"Rome did not create a great Empire by holding meetings. They did it by
killing all those who opposed them."
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Sisuite-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
