mount permission denied though server side already authenticated therequest
Strong Qu
strong.qu at amd.com
Tue Apr 10 20:53:52 UTC 2007
Thanks Jan for your help. There is no portmapper running on the platform
and portmap was not built on the platform. But I have another similar
platform that running Busybox 1.00 and does not have portmapper running
either. According my search from internet, portmapper is not needed if
use mount with -o nolock option.
Regards,
Strong
> -----Original Message-----
> From: Jan Evert van Grootheest
> Sent: Thursday, April 05, 2007 1:04 AM
> To: Strong Qu; busybox at busybox.net
> Subject: RE: mount permission denied though server side
> already authenticated therequest
>
>
> >-----Oorspronkelijk bericht-----
> >Van: busybox-bounces at busybox.net [mailto:busybox-bounces at busybox.net]
> Namens Strong Qu
> >Verzonden: woensdag 4 april 2007 16:08
> >Aan: busybox at busybox.net
> >Onderwerp: mount permission denied though server side already
> authenticated therequest
> >
> >
> >I'm new of using busybox. Detail as follow:
> >ARM V6 platform Linux 2.6.10, Busybox 1.01, ash shell, server side is
> Ubuntu 6.10, nfs exports *(rw, all_squash)
> >On target platform run:
> ># mount -o nolock 192.168.1.2:/home/user_1/share
> /mnt/shannon Root has
> >read/write/exec right in /mnt/pool. 192.168.1.2 is IP of
> shannon, the nfs server.
> >I got error as:
> >mount: permission denied. (are you root?) On the server side I run:
> ># tail -f /var/log/syslog
> >It shows:
> >Mar 30 11:01:13 shannon mounted[4330]: authenticated mount from
> 192.168.1.3 for /home/user_1/share (/home/user_1/share)
> >And on other x86/linux I can mount the nfs without any trouble.
> >I did not find nfsmount on the target board. Is it a must for nfs
> mount?
> >Thanks.
> >-Strong
>
> You do have a portmap running?
> I had this once too (the permission denied) because I forgot
> to start the portmapper.
>
> -- Jan Evert
>
> The information contained in this communication is
> confidential and may be legally privileged. It is intended
> solely for the use of the individual or entity to whom it is
> addressed and others authorised to receive it. If you are not
> the intended recipient you are hereby notified that any
> disclosure, copying, distribution or taking any action in
> reliance on the contents of this information is strictly
> prohibited and may be unlawful. Vialis is neither liable for
> the proper and complete transmission of the information
> contained in this communication nor for any delay in its receipt.
>
>
>
>
More information about the busybox
mailing list