Date: Sun, 2 Jul 2000 00:04:14 -0700 From: "Crist J. Clark" <cristjc@earthlink.net> To: steinyv <steinyv@skyweb.net> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: NFS Message-ID: <20000702000413.I1820@dialin-client.earthlink.net> In-Reply-To: <4.2.0.58.20000702021130.009ce120@>; from steinyv@skyweb.net on Sun, Jul 02, 2000 at 02:17:15AM -0400 References: <20000701211659.C1820@dialin-client.earthlink.net> <4.2.0.58.20000701215228.00a0bdb0@> <4.2.0.58.20000701215228.00a0bdb0@> <4.2.0.58.20000702012559.009b2e80@> <4.2.0.58.20000702021130.009ce120@>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jul 02, 2000 at 02:17:15AM -0400, steinyv wrote: > At 01:46 AM 7/2/00 , you wrote: > >At 12:16 AM 7/2/00 , you wrote: > >>On Sat, Jul 01, 2000 at 09:52:34PM -0400, steinyv wrote: > >> > Ok, newbie here. I installed successfully on one machine (Im a pro at > >> that > >> > now). Since my machines are not connected to the internet (yet), its only > >> > for practise, I gave the first machine the fake hostname of > >> > "gw.example.net" (sound familiar) with a fake ip address. The output of > >> > ifconfig -a shows my nic interface (ed0) witht the ip address and the > >> > loopback device. I entered the info as described for an nfs server from > >> > the handbook. > >> > >>OK, so take us through the steps. You made an exports(5) file. You > >>made sure portmap(8) was running. If mountd(8) was running, you gave > >>it a SIGHUP. If it was not, you started it. Right? Were there error > >>messages at any point? Any messages in /var/log/messages? > >>-- > >>Crist J. Clark cjclark@alum.mit.edu > > > >I made the exports file "/cdrom -ro 192.168.0.2" > >portmap was running as a daemon > >mountd was running, but I passed over the SIGHUP part > >Everything seems ok on the server side..... > >I tried again with different ip address (just to make me feel > >comfortable), and this time on the client during the setup I used the ip > >address instead because of lack of name server, so I used "192.168.0.1:/cdrom" > >and this time it returned "Unable to transfer the bin file. Do you want > >to try again." > >Ill try that SIGHUP thing and report back. > Well I tried the SIGHUP thing and I got the same results. This step is required. You have to tell mountd(8) to re-read the exports(5) file whenever changes are made. > I started the install again and these were the errors==> > "Unable to transfer the bin distribution from 192.168.0.1:/cdrom. > Do you want to try to retrieve it again?" > On the second console where all the messages are there was ==> > "mount_nfs: can't update /var/db/mounttab for 192.168.0.1:/cdrom" > Dont know what that 2nd message is about, anyone.......someone, help me??? IIRC, without looking at the source, that is a non-fatal message. Let's determine if the problem is at the server or client. Can the server mount its own exported filesystem? # cat /etc/exports /cdrom -ro -network 192.168.0.0 -mask 255.255.255.0 # kill -HUP `cat /var/run/mountd.pid` # mount 192.168.0.1:/cdrom /mnt And see what happens. Have you been checking /var/log/messages on the server to see what it might be reporting? -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000702000413.I1820>