From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id BE4641383E0 for ; Thu, 1 Oct 2015 13:42:05 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A8D1921C036; Thu, 1 Oct 2015 13:41:58 +0000 (UTC) Received: from mail-oi0-f49.google.com (mail-oi0-f49.google.com [209.85.218.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id BF88121C017 for ; Thu, 1 Oct 2015 13:41:57 +0000 (UTC) Received: by oiww128 with SMTP id w128so40743160oiw.2 for ; Thu, 01 Oct 2015 06:41:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=pAG/CUI3K8VbzPX4pM9lKaDFWRXIHeNvkZ4ibmTVPr8=; b=S8EcxG3MxDqvX3kli6Q3uB/t1EARdnP42Rbfk+KjHggDcX94ppd27ktIrzXWE1RYX8 J2k9Kb8HZroVuluu262+PsDya/eO9kmwr1kiHQud3CNCC/FeqYw1PCCd+l8OBv3epsHw pWfqWAtH8Re/QX7Hrd3dy7wy54noPg5sl9BQUBnmzZm/vv9VESwwDBjsZbv1EEewVz6Z aU5/WNPh71JZllA1MAAKdHioADh5PyazNBNYEBRnKDMmQItiVkN9ov6O79jvrRc0IoRo 3G0/LhO+TmDq4N3RCYv+kLW2szkJo+Um3TYRalNS2TinFs7CnYjotZrOifdNUuVsAAsu IiOw== X-Received: by 10.202.75.145 with SMTP id y139mr5789542oia.64.1443706916807; Thu, 01 Oct 2015 06:41:56 -0700 (PDT) Received: from linux1 (cpe-66-68-34-247.austin.res.rr.com. [66.68.34.247]) by smtp.gmail.com with ESMTPSA id ta5sm2713611obc.13.2015.10.01.06.41.55 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Oct 2015 06:41:56 -0700 (PDT) Sender: William Hubbs Received: (nullmailer pid 5236 invoked by uid 1000); Thu, 01 Oct 2015 13:41:55 -0000 Date: Thu, 1 Oct 2015 08:41:55 -0500 From: William Hubbs To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] news item: OpenRC 0.18 changes to localmount and netmount Message-ID: <20151001134155.GA5192@linux1> Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <5609c60d.2337420a.eba7.ffff912e@mx.google.com> <560AA05B.2020000@gentoo.org> <560AA5C3.8070607@gmail.com> <560AA9ED.8000603@gentoo.org> <560AAA85.7000709@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="huq684BweRXVnRxX" Content-Disposition: inline In-Reply-To: <560AAA85.7000709@gentoo.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-Archives-Salt: b20be51b-e1d0-4d33-8eac-9a5b3e492b50 X-Archives-Hash: 629ce4a231c400451924f37fda1f8eab --huq684BweRXVnRxX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 29, 2015 at 11:13:09AM -0400, Ian Stakenvicius wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 >=20 > 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=20 > >>>> mount/umount -a. This is being dropped because it is=20 > >>>> util-linux specific and not compatible with busybox. > >>>=20 > >>> Does this have any actual end-user impact? AFAIK, using the=20 > >>> -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.. > >=20 > >> As a user, that para in the news makes me ask "how does this=20 > >> affect me?". I have to go read man pages and init scripts to > >> find out. > >=20 > >> Perhaps this: > >=20 > >> 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. > >=20 > >=20 > > Exactly my thoughts. We used -O _netdev within the 'netmount'=20 > > 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. > >=20 > > I suppose it's worthwhile to note to busybox users that they no=20 > > longer have to use alternate means of netmounting, as 'netmount'=20 > > will now work on busybox...? > >=20 > > 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. " > >=20 >=20 > PS - i still think we should just cut it. What is it that you think we should cut? Thanks, William --huq684BweRXVnRxX Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlYNOCMACgkQblQW9DDEZTim3wCfYU7SZbwyvXBWGJfZXGXf58eC Ak0AoLMFKdOT000Cu2K+k8ST1CI7fWYk =fK0c -----END PGP SIGNATURE----- --huq684BweRXVnRxX--