Hi Roger, On Sun, Jun 21, 2009 at 02:26:51PM +0100, Roger Leigh wrote: > This information should be recorded in /proc/mounts now that this > information can be passed to mount(2). really? > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494001 I see in the bug report: > With linux >= 2.6.26, /proc/mounts contains all of the information in > /etc/mtab, plus more. The mount system call can now pass all of the > mount options to the kernel, so no information is missing in /proc/mounts. that's strange. I'd like to see kernel patch which implements support for userspace specific mount options. > Yes. For all the reasons given in the report. Additionally, > it fixes a *lot* of bugs in mount which bugs? I don't remember any bug report. > The only other issue I saw was loop devices not being automatically > freed (discussed in the link above), but this appears to be working > with the current util-linux-ng. Yeah, kernel >= v2.6.25 and util-linux-ng >= v2.14 support auto-destruction of loop devices. > Are there any other known bugs in > mount exposed when /etc/mtab is a symlink? Currently, we have two userspace mount options, user= and uhelper=. The uhelper= is used by HAL/DeviceKit (see umount man page). The /proc/mounts file does not properly store information about bind mounts -- this is reason why we have /proc/self/mountinfo. My plan is to support systems without /etc/mtab and use /proc/self/mountinfo in util-linux-ng 2.{17,18} (September/October 2009 or so...). Karel -- Karel Zak <kzak@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
