Very Computer

I've just succeeded in setting up and coniguring wireless networking from my
laptop to my desktop machine.  But I'm getting an error when trying to
remote NFS mount the root file system from my laptop on my desktop and vice
versa.

On my desktop, with the mount point /mars, when I type as root:

mount /mars

I get the error: "mount: RPC: Program not registered"

(I get the same error trying to mount the root file system of my desktop
on my laptop.)

Following the instructions in the PCMCIA howto, I have an entry for
/mars in my desktop machine's /etc/fstab and in
/etc/pcmcia/network.opts have set MOUNTS to "/mars".  But it appears
there is something else I need to do related to remote procedure call
configuration.

I am using Suse Linux and did a search for this problem on their web site
and found some discussion on this error; they were in German, so I couldn't
read them, but this implies that others have come across this problem and
found a solution.  (I'm using Suse 6.3.)

I don't think the problem has to do with the wireless card or driver,
but just in case - I'm using the Aviator2.4 pcmcia cards with Corey
Thomas's driver.

Can someone give me a hint or pointer to an appropriate document or URL?

Thanks!
--
Jim Cochrane

It sounds like you don't have the NFS server
running.  Look for something like
/etc/rc.d/init.d/nfs which starts NFS services.

If the NFS server programs aren't there or if no
filesystems are being exported then the services
won't start at boot time.

hth
tony

Quote:>I get the error: "mount: RPC: Program not registered"

You need to start mountd.

Quote:>I don't think the problem has to do with the wireless card or driver,

It doesn't.  I don't have SUSE, but on Caldera you have to enable nfs on
boot through their config tool or by editing /etc/sysconfig/daemons/nfs.

You can start mountd manually with /etc/rc.d/init.d/nfs start

--
 -| Bob Hauck
 -| To Whom You Are Speaking
 -| http://www.bobh.org/

Take with a grain (or six) of salt as I
only got this working within the past 24
hours myself ...  I had everything set up
to where the r commands worked, &c &c,
portmapper mountd nfsd  daemons were all
running on both sides (all machines will
serve NFS to each other) and every attempt
to mount ran into the error you're seeing.
Finally I thrashed around to something
that seemed to fix it (well, it DID fix it,
but I don't understand why, so YMMV) ...

Try using explicit IP addresses in the
_server_ /etc/exports and /etc/hosts.allow.
Names seem to OK on the client side in
/etc/fstab.

E.g., to allow "client" at 192.168.101.11
to NFS mount /opt read-only from server
at 192.168.101.10

   server's /etc/exports

        /opt    192.168.101.11(ro)

   server's /etc/hosts.allow

        ALL:    192.168.101.11

   clients /etc/hosts

      192.169.101.10  server

   client's  /etc/fstab

        server:/opt  /mnt/nfs/srv-opt  nfs  user,exec,rw,soft  0 0

//  Mike Kent

Contrary to other replies to your post, you don't need to start all NFS
services to get rid of this message (unless you want to export
NFS volumes from your laptop).  All you need to do is run the
portmapper, which starts the mount and lock daemons as
required.  Try

/etc/rc.d/init.d/portmapper start

before attempting to mount the volume.

I found the NFS documentation to be somewhat confusing on this issue.
--

University of Cambridge, Zoology Department, Downing Street, CAMBRIDGE CB2 3EJ

Thanks for your help and to that of the others that responded to my query.

It turns out that the fix for the problem in my case was to download an nfs
patch for Suse 6.3 on their web site and install it.  This fixed the
problem; not sure exactly what the fix did, but I think it replaced the nfs
and mount daemons.

If anyone else using Suse 6.3 has this problem, you need to download and
install nfsserv.rpm.

--
Jim Cochrane