Date: Mon, 22 Mar 2004 23:31:33 -0600 From: Sean Welch <Sean_Welch@alum.wofford.org> To: James Sarrett <James.Sarrett@asu.edu> Cc: freebsd-ppc@freebsd.org Subject: Re: Netbooting PPC FreeBSD and file locking Message-ID: <20040323053133.GA9026@NitroPhys.welchsmnet.net> In-Reply-To: <BF515510-7C8A-11D8-9329-003065FB9A8C@asu.edu> References: <20040323052448.GA8975@NitroPhys.welchsmnet.net> <BF515510-7C8A-11D8-9329-003065FB9A8C@asu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
inittab? There doesn't seem to be any such animal in the FreeBSD world... Sean On Mon, Mar 22, 2004 at 10:27:16PM -0700, James Sarrett wrote: > hmm... maybe check inittab? i dont' have an fBSD machine up at the > moment to check > > -James > On Monday, March 22, 2004, at 10:24 PM, Sean Welch wrote: > > >Well, I just copied the entries I have on the server (which > >seem to set things up just fine). Is there any way to guarantee > >it starts first other than order in rc.conf? It is listed > >first, but the system sure acts as though rpcbind isn't starting > >first... > > > >Sean > > > >On Mon, Mar 22, 2004 at 10:16:39PM -0700, James Sarrett wrote: > >>really quick, doublecheck to make sure rpcbind starts first > >> > >>-James > >>On Monday, March 22, 2004, at 10:10 PM, Sean Welch wrote: > >> > >>>Well, I just figured it out -- sort of. > >>> > >>>Looks like not only do I have to run rpcbind, rpc.statd, > >>>and rpc.lockd on the server I must run all three on the > >>>client as well. > >>> > >>>Suddenly passwd and adduser work just fine! :-) > >>> > >>>Now for the "sort of" statement. > >>> > >>>I added the necessary entries into the rc.conf of the > >>>exported filesystem but it failed to start up the > >>>services. I didn't see any mention of rpcbind in the > >>>boot messages but I did see this: > >>> > >>>rpc.statd: svc_tp_create: Could not register prog 100024 vers 1 on > >>>udp6 > >>>rpc.statd: svc_tp_create: Could not register prog 100024 vers 1 on > >>>udp > >>>rpc.statd: cannot create udp service > >>>Starting lockd. > >>>rpc.locd: unable to register (NLM_PROG, NLM_SM, udp) > >>> > >>>Also, I noticed that when the system is mounting > >>>filesystems it complains that the filesystem is read > >>>only and so creates a memory disk for /var !! No > >>>wonder I don't get the systems messages showing up in > >>>/var/log ! > >>> > >>>Progress! Now if I can just figure these things out... > >>> > >>>;-) > >>> > >>>Sean > >>> > >>>_______________________________________________ > >>>freebsd-ppc@freebsd.org mailing list > >>>http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > >>>To unsubscribe, send any mail to > >>>"freebsd-ppc-unsubscribe@freebsd.org" > >>> > >> > >>-------------------------------------------- > >>"Never trust a man who can count to 1024 on his fingers" > >>-------------------------------------------- > >> > >> > > -------------------------------------------- > "Never trust a man who can count to 1024 on his fingers" > -------------------------------------------- >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040323053133.GA9026>