Date: Sun, 02 Jul 2000 12:48:16 -0400 From: steinyv <steinyv@skyweb.net> To: freebsd-hardware@freebsd.org Subject: Re: NFS Message-ID: <4.2.0.58.20000702120746.009d4ee0@> In-Reply-To: <20000702000413.I1820@dialin-client.earthlink.net> References: <4.2.0.58.20000702021130.009ce120@> <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
>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? Well on the server side I was able to mount the cdrom on /mnt and was able to browse around, so everything's is cool there. I unmounted from /mnt, and went to the 2nd machine and tried to install via NFS using 192.168.0.1:/cdrom, and this time I was looking for the dreaded message but lo and behold the cdrom started humming and the 2nd machine is installing as I write. Dont know where the problem was, but Ill look over the config files to engrave it in my brain. Thank You very much. Another obstacle broken........ _________________________________________ Steiny's Studio Pachyderm Productions http://steiny.hypermart.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.2.0.58.20000702120746.009d4ee0>