This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/19108] New: Stop using /etc/mtab (_PATH_MOUNTED) in Linux
- From: "martin.pitt at ubuntu dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Fri, 09 Oct 2015 14:50:21 +0000
- Subject: [Bug libc/19108] New: Stop using /etc/mtab (_PATH_MOUNTED) in Linux
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=19108
Bug ID: 19108
Summary: Stop using /etc/mtab (_PATH_MOUNTED) in Linux
Product: glibc
Version: unspecified
Status: NEW
Severity: minor
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: martin.pitt at ubuntu dot com
CC: drepper.fsp at gmail dot com
Target Milestone: ---
An /etc/mtab file has been a broken concept right from the start (putting info
about mounted file systems on a mounted file system), and at least in Linux
(util-linux, systemd, etc.) it has been dead for many years. Every distro,
systemd, etc. configure /etc/mtab as a symlink to /proc/mounts, but every now
and then it still happens that /etc/mtab is a file: you might keep `/etc/` in
revision control, under backup, trying to edit it, etc.
This then causes e. g. libmount's mount monitor to break, systemd 227 will not
even boot (which is way too strict, I'm currently arguing about that in
https://github.com/systemd/systemd/issues/1495), and it's generally a pointless
exercise these days -- there is just one valid value for that file (be a
symlink to /proc/mounts).
util-linux has deprecated it a while ago (offering
--enable-libmount-force-mountinfo), and 2.27.1 will cease to pay attention to
it completely (https://github.com/karelzak/util-linux/commit/02501746). glibc's
_PATH_MOUNTED seems to be pretty much the only place left that actually still
needs /etc/mtab.
So, my plea: can we pretty please get rid of this altogether, use /proc/mounts
consistently, and stop creating/using/paying attention to /etc/mtab altogether?
(At least for Linux, not sure about BSD and others).
Thank you for considering!
--
You are receiving this mail because:
You are on the CC list for the bug.