From owner-freebsd-bugs Mon Feb 11 1:51:55 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8D44337B416; Mon, 11 Feb 2002 01:51:53 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1B9h4A60876; Mon, 11 Feb 2002 01:43:04 -0800 (PST) (envelope-from sheldonh) Date: Mon, 11 Feb 2002 01:43:04 -0800 (PST) From: Message-Id: <200202110943.g1B9h4A60876@freefall.freebsd.org> To: troyc@tacsoft.com, sheldonh@FreeBSD.org, sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: misc/34247: auto mount smbfs in /etc/fstab AFTER network startup (a la NFS) Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: auto mount smbfs in /etc/fstab AFTER network startup (a la NFS) State-Changed-From-To: analyzed->feedback State-Changed-By: sheldonh State-Changed-When: Mon Feb 11 01:40:50 PST 2002 State-Changed-Why: Merging the change onto the RELENG_4 branch is made tricky by the different handling of diskless booting on that branch. I can't test diskless booting, nor the impact of this change on it, so what's required now is feedback from diskless users on how the delayed network fs mounting support should be implemented. Responsible-Changed-From-To: sheldonh->freebsd-bugs Responsible-Changed-By: sheldonh Responsible-Changed-When: Mon Feb 11 01:40:50 PST 2002 Responsible-Changed-Why: Since I can't test this for RELENG_4, there's no sense in me hogging feedback. Thrown open to the floor. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message