From owner-freebsd-rc@FreeBSD.ORG Sat Dec 3 01:05:48 2011 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 430E91065670; Sat, 3 Dec 2011 01:05:48 +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 048888FC08; Sat, 3 Dec 2011 01:05:47 +0000 (UTC) Received: from pps.filterd (ltcfislmsgpa03 [127.0.0.1]) by ltcfislmsgpa03.fnfis.com (8.14.4/8.14.4) with SMTP id pB30PeSV001457; Fri, 2 Dec 2011 19:05:46 -0600 Received: from smtp.fisglobal.com ([10.132.206.31]) by ltcfislmsgpa03.fnfis.com with ESMTP id 11f93s82px-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 02 Dec 2011 19:05:46 -0600 Received: from dtwin (10.14.152.48) by smtp.fisglobal.com (10.132.206.31) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 2 Dec 2011 19:05:46 -0600 From: Devin Teske To: "'Doug Barton'" References: <039201ccb0ab$b3db9470$1b92bd50$@fisglobal.com> <4ED862D6.9090807@FreeBSD.org> <039f01ccb0da$67b50f20$371f2d60$@fisglobal.com> <4ED952AF.3060404@FreeBSD.org> <044c01ccb14c$55b99bc0$012cd340$@fisglobal.com> <4ED96570.4070302@FreeBSD.org> In-Reply-To: <4ED96570.4070302@FreeBSD.org> Date: Fri, 2 Dec 2011 17:05:58 -0800 Message-ID: <045101ccb157$b85dd510$29197f30$@fisglobal.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQIhmfk7Ve6JVGWlRGJXhdLF64R2wQHbinWoAbGk/9gCbCVefQH9N6nSAhXIaViUzxeeYA== Content-Language: en-us X-Originating-IP: [10.14.152.48] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.5.7110, 1.0.211, 0.0.0000 definitions=2011-12-02_06:2011-12-02, 2011-12-02, 1970-01-01 signatures=0 Cc: freebsd-rc@freebsd.org, 'Ken Smith' , 'Parker-Smith' , phk@freebsd.org, 'Julian Elischer' , "'Robison, Dave'" Subject: RE: mount(8) bug? rc.d/mountlate bug? bug in both? 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: Sat, 03 Dec 2011 01:05:48 -0000 > -----Original Message----- > From: Doug Barton [mailto:dougb@FreeBSD.org] > Sent: Friday, December 02, 2011 3:55 PM > To: Devin Teske > Cc: freebsd-rc@freebsd.org; 'Ken Smith'; 'Parker-Smith'; phk@freebsd.org; > 'Julian Elischer'; Robison, Dave > Subject: Re: mount(8) bug? rc.d/mountlate bug? bug in both? > > On 12/02/2011 15:44, Devin Teske wrote: > > >>>> Short answer, tag the mount(s) noauto in fstab, and mount them in > >>> /etc/rc.local. > >>>> > >>> > >>> That may be the simplest approach. > >>> > >>> However, we're looking more for a solution that involves keeping the > >>> NFS mounts in fstab(5). > >> > >> Why said anything about moving the NFS mounts out of fstab? > > > > s/mounts in fstab(5)/mounting logic entirely contained within > > fstab(5)/ > > /etc/fstab is just a configuration file. The actual mounting of stuff happens > elsewhere. My suggestion is to move the actual mounting of stuff from one rc file > to another, a solution which will completely meet your needs without changing > anything in the base. The fact that you're rejecting the simple solution indicates > to me pretty clearly that I don't want to be involved further. > > >> Not to mention, you specifically asked for a solution that involved > >> no code changes. Now you're proposing code changes. > > > > You expect everybody that asks questions to wait indefinitely for an > > answer and do nothing in the mean time? What a sad world. > > Indefinitely? I answered your initial post less than an hour after you posted it. > Tea in china? Whatever dude. -- Devin _____________ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.