From owner-cvs-all Sat Jul 21 11: 4:12 2001 Delivered-To: cvs-all@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id E662437B406; Sat, 21 Jul 2001 11:04:06 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 21 Jul 2001 19:04:05 +0100 (BST) To: mjacob@feral.com Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sbin/mount_nfs mount_nfs.8 mount_nfs.c In-Reply-To: Your message of "Sat, 21 Jul 2001 09:51:13 PDT." Date: Sat, 21 Jul 2001 19:04:04 +0100 From: Ian Dowse Message-ID: <200107211904.aa72582@salmon.maths.tcd.ie> Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , Matthew Jacob writes : >MFC? Of course. I'll do it shortly; it is the previous revision that is the important bugfix because right now there is no way in -stable to tell mount_nfs to wait forever on foreground mounts. But I will of course commit the two together. BTW, thanks for chasing me up on this issue. When I first saw the change in foreground mount behaviour introduced in r1.40 I did think that it was bad, but the explanation I was given at the time somehow convinced me that it wouldn't cause any problems. The change in default behaviour isn't such a big issue as the fact that the change broke support for critical NFS filesystems, and even with that bit fixed, many sites would require changes to /etc/fstab. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message