Thanks Mark The reason my exports file has "/installroot/", the trailing slash, is that when I go into Yast and select NFS Server, and then browse the directory I need, it seems to put the trailing slash in. I went along with that as, it seems, that without a trailing slash, you are specifying a file, with a trailing slash, you are specifying a directory.
I'll try specifying /home/Suse9/installroot. Never thought of trying it as the manual says to specify "installroot". Seemed to me to be a relative directory (and my question really was, relative to what?). Anyway, I will know within the hour. Thanks Tom Duerbusch THD Consulting --- "Post, Mark K" <[EMAIL PROTECTED]> wrote: > Tom, > > You should specify the install directory as an > absolute path name: > /installroot > > In your /etc/exports file, you have > /installroot/ *(ro,root_squash,sync) > > You don't need that trailing slash. > /installroot *(ro,root_squash,sync) > would work just as well. > > You don't have to bind mount the directory. You > could just export > /home/Suse9/installroot and tell YaST to use that: > /home/Suse9/installroot *(ro,root_squash,sync) > > > Mark Post > > -----Original Message----- > From: Linux on 390 Port > [mailto:[EMAIL PROTECTED] On Behalf Of Tom > Duerbusch > Sent: Sunday, January 16, 2005 10:10 PM > To: [email protected] > Subject: Installing Suse 9.0 with NFS > > > Where most of my time, I've tried installing Suse > 9.0 with SMB (to no > avail), I'm trying a NFS install this weekend (with > NFS on my Suse 9.0 > laptop). > > I got the following > > > 1 nfs > > 192.168.99.210 > > installroot > > > > warning: can't open /etc/fstab: No such file or > directory > > lockd: failed to open /var/lib/nfs/state: err=-2 > > CD not mounted. Please check parameters. > > Please specify the installation Source: > > When I exit the install, do a "mkdir temp" and > issue: "mount -t nfs > 192.168.99.210:/installroot temp", that seems to > work. Well, I can do a LS > on temp and see the files back on my laptop. > > My guess, is the NFS server hasn't setup or > authorized directories properly. > > I created the /installroot directory on the root > drive with suse9 and core9 > next....etc. > > Per the RELEASE NOTES, during the install, I just > need to specify the > directory "installroot". Since this seems to be > relative directory, I'm not > sure NFS would know where the subdirectory resides. > > The /etc/exports on the NFS server has: > > /installroot/ *(ro,root_squash,sync) > > That would seem to jive with what I see when I try a > manual mount, but I'm > not sure that this is what the Suse 9.0 install > needs. > > The Suse 9.0 installation really doesn't talk much > about the NFS server, > just part of the directory structure that it needs. > > Now, it may be that my root directory /installroot > may have to be a real > structure. The actual install files are on > /home/Suse9/installroot/sles9.... and accessed as: > > mount --bind /home/Sues9/installroot /installroot > > Any ideas on a proper NFS setup. > > Thanks > > Tom Duerbusch > THD Consulting > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access > instructions, send email > to [EMAIL PROTECTED] with the message: INFO > LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access > instructions, > send email to [EMAIL PROTECTED] with the > message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
