Re: bad nfs mounting

[Bernd Bleßmann <bibi@online.de>]

Hi Felix,

to start the status monitor statd just try:
# /sbin/rpc.statd

BTW: you mount command looks wrong to me, but this might be a typo. 
There should be the name of the exported directory after the ip address, 
separated by a colon (e.g. 192.168.1.2:/nfsexp).

Hope it helps.

Greetings
  Bernd


Felix Miata schrieb:
> # uname -a
> Linux Knoppix 2.6.24.4 #2 SMP PREEMPT... (aka 5.3.1)
>
> # portmap
> #
>
> # mount -t nfs 192.168.1.2 /nfsmnt
> mount.nfs: rpc.statd is not running but is required for remote locking
>     Either use '-o nolocks' to keep locks local, or start statd.
> #
>
> # mount -t nfs -o nolocks 192.168.1.2 /nfsmnt
> mount.nfs: Unsupported nfs mount option: nolocks
> #
>
> # ls -l /etc/init.d | grep rpc
> #
>
> # ls -l /etc/init.d | grep stat
> # pppstatus
> #
>
> I looked for clues in /etc/init.d/nfs-common and /etc/init.d/mountnfs.sh 
> for clues how rpc.statd is supposed to get started, but couldn't 
> recognize any. Why does mount.nfs tell me to try an option that it 
> cannot recognize? It used to be that all I had to remember to mount nfs 
> running Knoppix was to start portmap. What's the current 5.3.1 secret to 
> accessing nfs? Is it the same in all versions 5.3.1 or newer?
>
> BTW, I tried 6.4.1 or so first, but only get a black screen shortly 
> after init (3) starts. Intel 945G. I tried several cmdline options that 
> failed to help before giving that up in favor of 5.3.1.