From owner-freebsd-rc@FreeBSD.ORG Sun Jan 1 00:40:32 2012 Return-Path: Delivered-To: freebsd-rc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC1DF106566C; Sun, 1 Jan 2012 00:40:31 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id A0CCE8FC15; Sun, 1 Jan 2012 00:40:31 +0000 (UTC) Received: from pps.filterd (ltcfislmsgpa03 [127.0.0.1]) by ltcfislmsgpa03.fnfis.com (8.14.4/8.14.4) with SMTP id q010W59W017537; Sat, 31 Dec 2011 18:40:30 -0600 Received: from smtp.fisglobal.com ([10.132.206.17]) by ltcfislmsgpa03.fnfis.com with ESMTP id 122a3urc0b-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 31 Dec 2011 18:40:30 -0600 Received: from [10.0.0.103] (10.14.152.30) by smtp.fisglobal.com (10.132.206.17) with Microsoft SMTP Server (TLS) id 14.1.323.3; Sat, 31 Dec 2011 18:40:29 -0600 MIME-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset="us-ascii" From: Devin Teske In-Reply-To: <4EFF9911.5020603@FreeBSD.org> Date: Sat, 31 Dec 2011 16:40:27 -0800 Content-Transfer-Encoding: quoted-printable Message-ID: References: <201112310758.pBV7webJ074390@freefall.freebsd.org> <8F16E728-1A94-4ECD-9D83-4A854AD7A702@fisglobal.com> <4EFF9911.5020603@FreeBSD.org> To: Doug Barton X-Mailer: Apple Mail (2.1084) X-Originating-IP: [10.14.152.30] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.5.7110, 1.0.211, 0.0.0000 definitions=2011-12-31_06:2011-12-30, 2011-12-31, 1970-01-01 signatures=0 Cc: Devin, FreeBSD RC Subject: Re: The mountlate rc.d boot script cannot be disabled X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2012 00:40:32 -0000 First, let me prefix my inline responses with stating that: Due to the addition of the "failok" mount(8) option, it is highly likely th= at this may solve our problems. However, since the "failok" addition is currently not available in any -REL= EASE, we cannot test it for production deployment (maybe in 6-months). With that being said, we look forward to when FreeBSD 8.3-RELEASE will be m= ade available (as I've confirmed that "failok" is tagged for RELENG_8, the = source for what should be 8.3 when created). On Dec 31, 2011, at 3:21 PM, Doug Barton wrote: > On 12/31/2011 8:34 AM, Chris Rees wrote: >> Doug, is there a reason that the patch is harmful? >=20 > 1. An unlimited number of knobs is not a virtue, it just leads to more > user confusion. >=20 > 2. The harm caused by a user accidentally flipping this is much greater > than any possible benefit that it could provide. I've been thinking about it and the patch does have the following two negat= ives: 1. disabling mountlate means the administrator needs to memorize that whils= t looking at fstab(5) that "late" filesystems could be neutered (good or ba= d, requires modification of man-pages, re-training to learn new axioms, etc= .) 2. mountlate is metaphorically the "enforcer" of mountcritremote. Disabling= mountlate means mountcritremote doesn't really make remote mounts critical. So, up until this point, we'd not been aware of the new "failok" option (wh= y would we? it's not really available yet) and now that we know about it, w= e look forward to checking it out in a future release. But at this time, ne= ither 8.1 nor 8.2 support it. Until we can upgrade, we'll have to resort to= modifying the system in some way. > I think Jilles had a good point, it's likely that the best actual change > to be made here is better documentation of the failok knob for fstab. >=20 Gcooper raised docs/163742 to address the lacking documentation. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.