According to Chris Fischer: While burning my CPU.
>
> Richard,
>
> Sorry for taking so long to get back to you...it's been a busy couple weeks. The
> problem was simple to fix. I'm running RedHat 5.0. I don't know if other
> distributions have this utility, but there's a utility called tksysv. It's a gui
> utility that allow you to edit what's loaded at the different runlevels. As it
> turns out 'nfsfs' wasn't set to run for initlevel 3. I just added 'nfsfs' to the
> list of items to run at boot time and now my nfs partition mounts like it should
> automatically.
>
> Thanks for all your help!
Thanks for letting me know, sorry it took me so long to reply also, i have
been away in Spain on my holidays.
It would seem however i should have made myself clearer i stated "make sure
nfs is started after the eth0 interface is up" i should have said "nfsfs",
sorry for the confustion.
>
> Regards,
>
> Chris Fischer
>
> Richard Adams wrote:
>
> > According to Chris Fischer: While burning my CPU.
> > >
> > > Richard,
> > >
> > > Richard Adams wrote:
> > >
> > > > You need to enter the name of the directory on the remote machine which is
> > > > to be mounted on your machine;
> > > >
> > > > 192.168.0.1:/files /files nfs defaults 0 0
> > > >
> > > > The /files directory could possably be called something else on the remote
> > > > machine.
> > >
> > > I'm trying to mount the entire root partition, but it's still not mounting.
> > >
> > > In fstab, I put:
> > >
> > > 192.168.0.1:/ /files /nfs defaults 0 0
> > >
> > > but it still doesn't mount....any other suggestions?
> > >
> > > However, I am able to mount at the shell prompt with:
> > >
> > > mount -t nfs 192.168.0.1:/ /files
> > >
> >
> > Well normaly speaking it "should work", what is possably happening is that
> > you are not booting your machine in the proper manner.
> > By this i mean your system is possably trying to mount the nfs partition
> > "before" the ethernet interface is attached.
> >
> > How do you attach your interface, is is done in a normal manner or is i
> > activated by you in a seperate script somewhere.???
> >
> > Firstly, what system do you have redhat slackware.??
> > Secondly how is your system setup to boot, in the normal "installation" way,
> > by this i mean default settings done by some configuration program,?.
> >
> > Does the system seem to halt for a couple of minutes while it trys to
> > contact the remote host at boottime, (this would indicate the lack of an
> > entry in your /etc/hosts for 192.168.0.1)??
> >
> > At bootime you need to make sure that;
> >
> > 1) nfs is started after the eth0 interface is up, (networking has been
> > activated)
> > 2) There is a valid route for 192.168.0.1
> > 3) A valid entry in /etc/hosts for 192.168.0.1
> > 4) If used, a valid DNS server, and a valid route to it.
> >
> > If all else fails and you cant seem to find out what is happening, meaning
> > it just wont work how you want it to, you can do;
> >
> > edit /etc/fstab to;
> > 192.168.0.1:/ /files /nfs noauto 0 0
> > Now save and exit.
> >
> > edit /etc/rc.d/rc.local
> > add a line at the bottom of the file like;
> > /bin/mount 192.168.0.1:/
> >
> > There is no need to edit any other files, as the "noauto" entry in fstab
> > will result in no action being taken to mount the nfs partition at bootime.
> >
> > Doing it this way is just about the same as typing it in at the prompt, this
> > considering the fact that the "whole" system is up and running before you
> > issue the command in rc.local, as rc.local is the last file to be executed
> > at boottime.
> >
> > Now i would appricate an answer from you as and when you get things going as
> > you want them, just to let me know just what the problem was if found...
> >
>
--
Regards Richard.
[EMAIL PROTECTED]
