On Fri, Feb 06, 2015 at 05:43:03PM -0500, [email protected] wrote:
>
> The error message read, "mountpoint: /proc: no such file or directory,
> /procmount: mount point /proc does not exist, mountpoint: /sys: no such file
> exists.
> But I expected this. That it continued to detect devices was encouraging.
>
> My question is how to best recreate the proc, sys & /dev/pts environment in
> sda3. They exist in sda1 but to my knowledge neither tar nor rsync will
> properly copy these directories. Believe repeating LFS steps may accomplish
> this but after examining the 7.6 docs it isn't clear which ones would do it.
You do not need, nor want, to copy the contents of those directories.
All you need is the mountpoints (specifically /proc, /sys and /dev).
As root on the host, with the LFS partition mounted at /mnt/lfs,
mkdir -v /mnt/lfs/{dev,proc,sys}
If you need to go back in to chroot for any reason, mount the
contents from the host:
mount --bind /dev /mnt/lfs/dev
mount --bind /proc /mnt/lfs/proc
mount --bind /sys /mnt/lfs/sys
We seem to make some effort to ensure /dev/pts is mounted in
chroot, but for me (normally, on LFS hosts, but occasionally on a
rescue system) binding /dev ensures that /dev/pts is present.
/proc and /sys are a view of the running kernel. /dev is the
devices, as mediated by udev and the kernel in most modern systems
(if you really wanted, you could avoid udev and use static devices
but for most uses udev is easier and LFS expects you to use udev, or
more specifically eudev).
ĸen
--
Nanny Ogg usually went to bed early. After all, she was an old lady.
Sometimes she went to bed as early as 6 a.m.
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
