On Sun, Sep 7, 2014 at 12:51 PM, Bruce Dubbs <[email protected]> wrote: > I don't like the idea of some things auto-magically mounted at boot time.
Right, and I've accepted your decision on this. But don't you think it's wrong then that the current boot script includes the mount options for the virtual filesystems? This is confusing, and implies it *is* trying to automount. To your earlier point, this also clobbers any user options. So either include the -t <fstype> option so those commands succeed, or change them to be a pure 'mount <dir>' and assume everything is fully specified in fstab. It's the current "in-between" logic that seems wrong to me. > As far as the error message goes, perhaps you should file a bug with > util-linux. Well if mounting proc fails, mount is right: /etc/mtab -> /proc/self/mounts does not exist. Perhaps the util-linux guys should prefix the error with '/etc/mtab: ', but if changing it to a regular file ensures a much more user friendly error, is there some compelling reason to leave it as a symlink? I don't think the performance advantage of symlinking to /proc/mounts matters on a base LFS install. I absolutely understand your point that "if people just follow the book they won't get this error." But LFS is an educational resource after all, and missing a virtual filesystem in fstab seems like a realistic mistake for a new user to make. Why not have a clear error that is immediately understandable in that situation? Thanks, Dylan -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
