From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] news item: OpenRC 0.18 changes to localmount and netmount
Date: Thu, 1 Oct 2015 08:41:55 -0500 [thread overview]
Message-ID: <20151001134155.GA5192@linux1> (raw)
In-Reply-To: <560AAA85.7000709@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2379 bytes --]
On Tue, Sep 29, 2015 at 11:13:09AM -0400, Ian Stakenvicius wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 29/09/15 11:10 AM, Ian Stakenvicius wrote:
> > On 29/09/15 10:52 AM, Alan McKinnon wrote:
> >> On 29/09/2015 16:29, Ian Stakenvicius wrote:
> >>> On 28/09/15 06:58 PM, William Hubbs wrote:
> >>>> Also, we are dropping the use of the -O switch for
> >>>> mount/umount -a. This is being dropped because it is
> >>>> util-linux specific and not compatible with busybox.
> >>>
> >>> Does this have any actual end-user impact? AFAIK, using the
> >>> -O switch was 'just added' by us originally (i think to
> >>> reduce the explicit listing of the different fs types or
> >>> otherwise simplify the init script code) right? I'm just
> >>> wondering if this paragraph is actually necessary or not..
> >
> >> As a user, that para in the news makes me ask "how does this
> >> affect me?". I have to go read man pages and init scripts to
> >> find out.
> >
> >> Perhaps this:
> >
> >> Also, we are dropping the use of the -O switch for
> >> mount/umount -a, because it is util-linux specific and not
> >> compatible with busybox. This only affects mounts with
> >> "_netdev" listed under options in /etc/fstab. Such systems
> >> should use "noauto" and/or "nofail" as described above.
> >
> >
> > Exactly my thoughts. We used -O _netdev within the 'netmount'
> > script to identify which fstab entries are network mounts. But
> > we did it a different way prior to using -O _netdev. And since
> > this isn't actually related in any way to something end-users can
> > set in fstab (it has to do with the filesystem type itself) I
> > don't see the point in worrying end-users about it.
> >
> > I suppose it's worthwhile to note to busybox users that they no
> > longer have to use alternate means of netmounting, as 'netmount'
> > will now work on busybox...?
> >
> > Perhaps: " Also, we are dropping the use of the -O switch for
> > mount/umount -a, to ensure the localmount and netmount scripts
> > are compatible with busybox mount. If your system uses busybox
> > mount please migrate any custom workarounds you may have to the
> > openrc localmount/netmount services. "
> >
>
> PS - i still think we should just cut it.
What is it that you think we should cut?
Thanks,
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2015-10-01 13:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 22:58 [gentoo-dev] news item: OpenRC 0.18 changes to localmount and netmount William Hubbs
2015-09-29 0:05 ` [gentoo-dev] " Duncan
2015-09-29 14:29 ` [gentoo-dev] " Ian Stakenvicius
2015-09-29 14:52 ` Alan McKinnon
2015-09-29 15:10 ` Ian Stakenvicius
2015-09-29 15:13 ` Ian Stakenvicius
2015-10-01 13:41 ` William Hubbs [this message]
2015-10-01 14:15 ` Ian Stakenvicius
2015-10-01 15:46 ` Ian Stakenvicius
2015-10-01 15:49 ` Mike Gilbert
2015-10-01 16:05 ` J. Roeleveld
2015-10-01 18:17 ` J. Roeleveld
2015-10-01 18:42 ` [gentoo-dev] OpenRC 0.18 changes -O _netdev Ian Stakenvicius
2015-10-01 20:16 ` William Hubbs
2015-10-01 20:45 ` Mike Gilbert
2015-10-01 20:50 ` Kristian Fiskerstrand
2015-10-01 20:56 ` Ian Stakenvicius
2015-10-01 21:04 ` William Hubbs
2015-10-01 21:07 ` Kristian Fiskerstrand
2015-10-01 21:34 ` William Hubbs
2015-09-30 7:57 ` [gentoo-dev] news item: OpenRC 0.18 changes to localmount and netmount J. Roeleveld
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=20151001134155.GA5192@linux1 \
--to=williamh@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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