Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!jplopto!earle
From: earle@jplopto.uucp (Greg Earle)
Newsgroups: comp.dcom.lans,comp.protocols.tcp-ip
Subject: Re: SUN 3.4 problems
Message-ID: <4355@elroy.Jpl.Nasa.Gov>
Date: Thu, 27-Aug-87 14:49:22 EDT
Article-I.D.: elroy.4355
Posted: Thu Aug 27 14:49:22 1987
Date-Received: Sun, 30-Aug-87 06:14:58 EDT
References: <1615@briar.Philips.Com>
Sender: news@elroy.Jpl.Nasa.Gov
Reply-To: earle@jplopto.JPL.NASA.GOV (Greg Earle)
Followup-To: poster
Organization: Jet Propulsion Laboratory, Pasadena, CA
Lines: 23
Keywords: /etc/servers  YP
Summary: Another possibility
Xref: mnetor comp.dcom.lans:785 comp.protocols.tcp-ip:1002

Joanne,
	Are you running YP?  Your boots are dying when it tries to do NFS
mounts; in order to do this there has to be an entry for the rpc.mountd
daemon in /etc/servers, so the program can be registered.  Trouble is,
when you install diskless clients, either /etc/servers or /etc/services
(or both) *do not get installed* on diskless clients.  If it is /etc/servers
and (I think) you do not run Yellow Pages, then the portmapper will not
be able to get the entry for the server, and it will emit the messages
you describe.
	I suggest you halt all your diskless clients, retry the 3.4 kernel on
`condor', then successively mount /dev/ndl[0-9?] onto /mnt, and do a
cp /etc/servers /mnt/etc/servers (and do /etc/services just to make sure).
Then unmount /mnt.  After you're all done, reboot the server with the 3.4
kernel, then try the client reboots again.  See what happens.

Just a thought,

	- Greg

	Greg Earle		earle@jplopto.JPL.NASA.GOV
	Sun Consulting		earle%jplopto@jpl-elroy.ARPA	[aka:]
	(Freelance -		earle%jplopto@elroy.JPL.NASA.GOV
	    write me)		...!cit-vax!elroy!smeagol!jplopto!earle