@Steve Langasek: The options CANNOT be specified. *PLEASE* => read my comments early on. Quote:
"... As per these instructions by SUN, when you issue this command: /opt/tta_tem/bin/tem startcdm ... to trigger the "client drive mapping" functionality then this script "/opt/tta_tem/bin/tem" is executed which ultimately triggers the mount command I give above (I checked via "strace"): "mount -t nfs -o rw,udp,mountvers=2,port=4242 localhost:/smb /smb" So this explains why I need above command to work, no matter how strange and pointless it may look. ... " > My assertion is that, contrary to the SGD documentation, 'mountvers' > should normally not need to be specified explicitly. My assertion is that this option should not have been touched, damn it!! This boneheaded changing of options because "nobody should be using this" is making Debian and Ubuntu *impossible* to use in a professional environment. One day the option is there ... you upgrade a few packages and ... *POOOOFFF!* ... option is gone all of a sudden and your Enterprise Remote Access solution partially stops to work. Nice one. Seriously. :-( > I would expect the same problem to affect recent versions of RHEL, for > instance. I can test that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/251923 Title: /sbin/mount.nfs doesn't understand mount option mountvers=n To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/251923/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
