[lfs-support] Why are /usr/bin, /usr/sbin, /sbin in chroot command?
lfs65 at cruziero.com
Wed Dec 28 06:16:08 PST 2016
> From: ssmtpmailtesting ssmtpmailtesting <ssmtpmailtesting at gmail.com>
> Date: Wed, 28 Dec 2016 07:13:56 +0600
> Subject: [lfs-support] Why are /usr/bin, /usr/sbin, /sbin in chroot command?
> chroot "$LFS" /tools/bin/env -i \
> HOME=/root \
> TERM="$TERM" \
> PS1='\u:\w\$ ' \
> PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \
> /tools/bin/bash --login +h
> Why are /usr/bin, /usr/sbin, /sbin, /bin in chroot command? Aren't these
> directories empty after completing temporary system? Aren't all packages
> installed in /tools/bin not in /bin, /usr/bin, /usr/sbin, /sbin?
Why not - if not already - follow the book past (& indeed up to &
including) that point; think, observe, keep your question in mind,
and see if it gets addressed satisfactorily in due course.
And similarly in general (at least): for the first 1/2/.../few builds of
the book, do it manually, and follow the book carefully; and >= many/most
queries (that are likely to be had early-on) are likely to be addressed
at least substantially; and then one is more likely to have a better
understanding of the why/why-not.
More information about the lfs-support