[BusyBox] NFS: mount program didn't pass remote address!

Remco van Strien rvs_82 at hotmail.com
Fri Apr 1 12:03:29 UTC 2005


To compile the package portmap with my toolchain I had to enable full RPC 
support in uClibc. After doing this and following the instructions below 
everything worked and I could mount the NFS share.

Many thanks,
Remco van Strien.

>From: John Williams <jwilliams at itee.uq.edu.au>
>Reply-To: jwilliams at itee.uq.edu.au
>To: Remco van Strien <rvs_82 at hotmail.com>, busybox at mail.codepoet.org
>Subject: Re: [BusyBox] NFS: mount program didn't pass remote address!
>Date: Fri, 01 Apr 2005 08:37:07 +1000
>
>Remco van Strien wrote:
>>Hi,
>>
>>I'm using linux kernel 2.6.11.3 with buildroot with BusyBox v1.00 for my 
>>target. I'm trying to connect to the host share at 192.168.1.1:/tmp. This 
>>directory is shared succesfully, i can connect there locally with the 
>>host. However when i try to connect with my client I get the following:
>>
>># mount -t nfs -o nolock,ro,nfsvers=2 192.168.1.1/tmp /mnt
>>nfs warning: mount version newer then kernel
>>NFS: mount program didn't pass remote address!
>>mount: Mounting 192.168.1.1/tmp on /mnt failed: Invalid argument.
>>
>>
>>I also tried:
>># mount 192.168.1.1:/tmp /mnt
>>nsf warning: mount version older than kernel
>>portmap: server localhost not responding, timed out
>>RPC: failed to contact portmap (errno -5).
>>portmap: server localhost not responding, timed out
>>RPC: failed to contact portmap (errno -5).
>>lockd_up: makesock failed, error=-5
>>portmap: server localhost not responding, timed out
>>RPC: failed to contact portmap (errno -5).
>>
>>Any suggestions??
>
>Have you run portmap?
>
>$ portmap &
>
>$ mount -t nfs .....
>
>Regards,
>
>John

_________________________________________________________________
Direct antwoord op je vragen: gebruik MSN Messenger http://messenger.msn.nl/




More information about the busybox mailing list