Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!news.hawaii.edu!ames!olivea!uunet!mcsun!sun4nl!eur.nl!pk From: pk@cs.few.eur.nl (Paul Kranenburg) Newsgroups: comp.unix.bsd Subject: Re: NFS mount of /usr Message-ID: <1992Jul30.114552.15049@cs.few.eur.nl> Date: 30 Jul 92 11:45:52 GMT References: <sxjcb-290792093009@sxjcb.uacn.alaska.edu> Sender: news@cs.few.eur.nl Reply-To: pk@cs.few.eur.nl Organization: Erasmus University Rotterdam Lines: 28 In <sxjcb-290792093009@sxjcb.uacn.alaska.edu> sxjcb@orca.alaska.edu (Jay C. Beavers) writes: >I've been playing around with NFS and such and it's working just fine, so >I've >tried to take NFS to it's next logical step on my 39 MB system -- NFS >mounting >/usr. However, 386BSD seems to think that this is just a horrible idea and >I've had no end of trouble. >If I leave the rc file intact, I get a system hang after 'starting system >logger'. >If I edit the rc file to hardcode my old usr directory (/oldusr) to every >file located in /usr I get a hang after the rc file ends. I have used a NFS mounted /usr from day 1 (never had a /usr partition on the local HD). You need to set the correct parameters to enable your network device to handle the traffic generated by the server. I am currently using a WD8003 card which has an 8K buffer, so the default NFS read/write packet size of 8K will most likely generate to many back-to-back ethernet packets when mounting from a fast server. I use this entry in /etc/fstab: bridei:/export/exec/i386 /usr nfs rw,rsize=4096,wsize=4096 0 0 Reading from the NFS mounted filesystem is actually faster than from the local hard disk (not much, but it was above expectations). -pk