On Thursday 07 April 2016, Karel Zak wrote: > libmount supports three scenarios: > > 1) regular classic /etc/mtab > > 2) /etc/mtab symlink to /proc/self/mount -- in this case libmount > uses /proc/self/mountinfo and /run/mount/utab > > The current default is to detect symlink and on-the-fly switch > between 1) and 2). > > 3) --enable-libmount-force-mountinfo -- don't care about the symlink > and always use /proc/self/mountinfo. This is robust solution required > for example by systemd, because unfortunately sometimes people use > broken stuff (init scripts, tools, etc.) which removes the symlink. > > > I'd like to make 3) default, the question is what with mtab code: > > a) #ifdef all mtab code (and add --enable-support-mtab) > > b) remove mtab support at all (because it's evil and horrible > code) > > Comments? Even if b) is the final goal I would first do a) and mark the new option --enable-support-mtab as deprecated from the beginning. Could be interesting to see who would ever use this option and because of which reasons. About changing the default: We could add a warning somewhere to a non-critical tool when printing human-readable output, like lsblk: "warning: deprecated /etc/mtab file ingnored" ... just to remind people to fix their system/scripts. cu, Rudi -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html