From: Ruediger Meier <sweet_f_a@gmx.de>
To: Robby Workman <rworkman@slackware.com>
Cc: Karel Zak <kzak@redhat.com>, util-linux@vger.kernel.org
Subject: Re: v2.29 plan: kill mtab
Date: Wed, 13 Apr 2016 13:03:15 +0200 [thread overview]
Message-ID: <201604131303.16574.sweet_f_a@gmx.de> (raw)
In-Reply-To: <alpine.LNX.2.02.1604121931070.16273@connie.slackware.com>
On Wednesday 13 April 2016, Robby Workman wrote:
> On Mon, 11 Apr 2016, Karel Zak wrote:
> > On Sun, Apr 10, 2016 at 09:35:41PM -0700, Robby Workman wrote:
> >> 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-libmount-support-mtab)
> >>>
> >>> b) remove mtab support at all (because it's evil and horrible
> >>> code)
> >>>
> >>> Comments?
> >>
> >> We still use SysV init because it suits our needs just fine, and
> >> we have no plans to migrate to systemd in the foreseeable future,
> >> so we don't have any other compelling reason to use anything other
> >> than classic /etc/mtab. As such, we'd certainly appreciate, at the
> >> very least, leaving the mtab support in util-linux.
> >
> > This discussion is really not about init, but about mtab that is
> > broken by design.
>
> Okay, then how about this? Our current use of /etc/mtab works well
> for us, and as far as I'm aware, we've experienced absolutely
> none of this "[breakage] by design"
AFAIR we've had a lot of /etc/mtab related bugs in past, for sure also
reproducable on Slackware. For util-linux upstream it's annyoing to fix
these bugs by adding ugly code ... although there is a rock-solid
replacement available since many years.
> - as such, we'd be grealy
> appreciative if the option remains to continue using it.
There are many advantages by using /proc and unfixable issues
with /etc/mtab file. IMHO in this case you should have a real reason
why you don't want to go forward.
> -RW
> --
> To unsubscribe from this list: send the line "unsubscribe util-linux"
> in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-04-13 11:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 4:35 v2.29 plan: kill mtab Robby Workman
2016-04-11 20:59 ` Karel Zak
2016-04-13 2:33 ` Robby Workman
2016-04-13 10:28 ` Karel Zak
2016-04-13 11:03 ` Ruediger Meier [this message]
2016-04-12 1:07 ` Isaac Dunham
-- strict thread matches above, loose matches on Subject: below --
2016-04-07 10:54 Karel Zak
2016-04-07 11:22 ` Ruediger Meier
2016-04-13 20:58 ` Ruediger Meier
2016-04-14 12:43 ` Karel Zak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201604131303.16574.sweet_f_a@gmx.de \
--to=sweet_f_a@gmx.de \
--cc=kzak@redhat.com \
--cc=rworkman@slackware.com \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox