mount nfs failed without explicitly specify the address

[jady3356]

It was failed and prompt "mount: '192.168.1.22:/nfs'->'nfs': Invalid argument". Steps as follow(it works with Busybox):

mkdir nfs
mount -t nfs -o nolock 192.168.22:/nfs nfs

It works if specify the address:

mount -t nfs -o nolock,addr=192.168.1.22 192.168.22:/nfs nfs

Is it possiable to optimize the redundancy address check and just have same behavior with Busybox?

[landley]

I have a todo item to add "nfsmount" and "smbmount" commands that can prompt for password without showing it to other ps users on the command line, and stuff like that. (No, passing -o as an environment variable doesn't help, /proc/self/environ exists...)

Would that cover it?

Rob