RFC - Bugs 688 & 732

Greg Schafer gschafer at zip.com.au
Wed Jan 21 00:15:55 PST 2004


I want to close these 2 bugs as wontfix. Bringing here for discussion before
doing so.


This bug was opened by me but I've now changed my mind after thinking long
and hard about it. I still believe that mounting from within the chroot is
technically not sound, but it ain't so bad in the overall context of an LFS
build. Sure, /proc/mounts and the real /etc/mtab can get out of sync, but
the consequences of this aren't too worrisome when it's only some virtual
file systems we're dealing with.


is suggesting we use "mount -n" to suppress the:

"warning: can't open /etc/fstab: No such file or directory"

when mounting from within the chroot. While using the "-n" certainly gets
rid of the warning, it leads to other confusion. If you're inside the chroot
and you type "mount" to see what's mounted, if mtab is missing (which it is
due to use of "-n") then you get the output of /proc/partitions which is all
the real mounts as viewed from outside the chroot! Nasty.

Currently, the first mount of proc gives the warning of "can't open
/etc/fstab" but it does create an mtab file inside the chroot resulting in
further mounts not bitching. It also means typing "mount" to see the current
mounts gives the right results.

In summary, I don't think it's a problem getting the initial "can't open
/etc/fstab" warning. If we really wanted to get rid of the warning we could
always "touch /etc/mtab" before mounting like we used to. But that was
removed when is was realised that the first mount of /proc creates /etc/mtab
anyway (albeit with a warning about missing /etc/fstab).

Confused? I hope not :-)

Unless there are some major objections, I'll close these 2 bugs as wontfix
making a ref back to this thread.


More information about the lfs-dev mailing list