vze24938 at verizon.net
Tue Jan 9 19:29:30 PST 2001
Ah, okay...didn't know you could do that!
For error checking, I could create some file with a weird name ("touch
loony") right under /mnt/lfs and then check in the post-chroot script if
that file exists ("if [ -f /loony ]").
Cool! I'm gonna see if appending the script to the chroot command
instead of /bin/bash works....
It works! Thanks man, you're a lifesaver!
> I haven't tried anything like this, so it's just a stab in the dark, but...
> Instead of calling 'bash' in the chroot command, how about calling the chroot
> version on your script (as long as it's available in the chroot environment.)
> i.e. instead of 'chroot $LFS env -i HOME=/root bash --login' do something
> like 'chroot $LFS env -i HOME=/root CHROOTSCRIPT' since the script should
> start with a shebang line of #!/bin/bash, bash will still be running.
> - --
> GPG public key / Geek Code block available at
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.4 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
> -----END PGP SIGNATURE-----
> Unsubscribe: send email to lfs-apps-request at linuxfromscratch.org
> and put unsubscribe in the subject header of the message
Unsubscribe: send email to lfs-apps-request at linuxfromscratch.org
and put unsubscribe in the subject header of the message
More information about the blfs-support