From owner-freebsd-bugs Tue Oct 22 05:40:06 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA26299 for bugs-outgoing; Tue, 22 Oct 1996 05:40:06 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA26268; Tue, 22 Oct 1996 05:40:04 -0700 (PDT) Date: Tue, 22 Oct 1996 05:40:04 -0700 (PDT) Message-Id: <199610221240.FAA26268@freefall.freebsd.org> To: freebsd-bugs Cc: From: Peter Wemm Subject: Re: bin/926 Reply-To: Peter Wemm Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR bin/926; it has been noted by GNATS. From: Peter Wemm To: Robert Eckardt Cc: scrappy@freefall.freebsd.org (Marc G. Fournier), hsu@clinet.fi, freebsd-gnats-submit@freefall.freebsd.org Subject: Re: bin/926 Date: Tue, 22 Oct 1996 20:37:47 +0800 Robert Eckardt wrote: > > Synopsis: Mounting nfs disks before starting mountd: Chicken or Egg problem > > Problem Still Exists > > From: Heikki Suonsivu > > > > This is still valid problem; mountd is started in /etc/rc later than mount > > -a -t nfs is run (checked current from two days ago). > > This is no conflict. mountd is needed for the NFS-Server. > Mounting NFS-FSs is done by the NFS-Client, which needs only nfsiod. > > Robert And not even that.. You can mount nfs partitions as a client even without the nfsiod's running, you just get slower transfers until they are going. Although I could see there would be a problem if the machine was mounting some of it's own disks, but I suspect that might be tempting fate with ``interesting'' coherency problems.. Cheers, -Peter