Zhang Weiwu wrote: > On Tue, 2007-06-05 at 13:47 +0100, Dave Howorth wrote: >> Is no_secure a valid option? > > I don't know but without this option if my SuSE 10.2 is nfs server and > Ubuntu is nfs client, the client cannot mount. So I just use this option > to avoid SuSE client not being able to mount ubuntu nfs server
It was just that the man page on my system says 'insecure' rather than 'no_secure'. But then I'm not on 10.2. >>> The client (SuSE 10.2) can mount as rw correctly but cannot write: >>> >>> joe:/home/yuliansu # mount -v eula:/home/zhangweiwu/Movies Movies/ >>> eula:/home/zhangweiwu/Movies on /home/yuliansu/Movies type nfs >>> (rw,addr=124.72.54.254) >>> joe:/home/yuliansu/Movies # rm Movies/* >>> rm: cannot remove `Breakfast.At.Tiffanys.CD1.avi': Read-only file system >>> >>> I have checked the files in Movies folder belong to user 1000, group >>> 1000, permission 666, so permission should be okay. >> (this is a red herring but in the interest of accuracy...) It's the >> permissions of the directory that count. What are they? > > the permission of the directory 755, owned by uid=1000 gid=100 So the group is irrelevant since it doesn't have write permission. A red herring as promised :) >> Also you say it is exported as gid 100 but the user is gid 1000 ??? > > Yes that's the strange! On Ubuntu every file I have in my home directory > is of uid:1000 and gid:1000, on SuSE it's uid:1000 gid:100 > > I don't know why Ubuntu created a user group 'zhangweiwu' when I created > my own account 'zhangweiwu' with all default options. If this is more or > less a Ubuntu issue I'll forward to Ubuntu forum. I am only not sure. There are two factors. The numbers are different because Suse and Ubuntu/Debian just happen to use different default numbers for groups. You can change that in YaST if you wish; I don't know how to do it on Ubuntu. The second issue is the per-user groups. Suse follows the traditional Unix way where everybody belongs to the same group unless you explicitly set up some team structures. The implicit assumption is that they're all working together and need to share things. Ubuntu follows a different line of thought which is that users are individuals and their right to privacy is most important for the default settings. So everybody gets their own groups, default umask is different, and you need to explicitly set up sharing between team members. Just different defaults. >>> I simply begin to have no clue to go on, what else should I look for >>> finding out why I am told "Read-only file system" (it is NOT)? >> What does /etc/mtab say? > > [EMAIL PROTECTED]:~> grep Movies /etc/mtab > eula:/home/zhangweiwu/Movies /home/yuliansu/Movies nfs > rw,addr=124.72.54.254 0 0 That looks OK. Sorry, I'm not sure what the problem is. Here are some random questions I'd You can list the directory. Can you read the files? Can you create a new file? Can you write to an existing file? What versions of NFS are in use on client and server? Actually, given that you have to turn security off to make it work, I'd double check all the NFS configuration options on both systems. Does it work if you remove the all_squash and/or anonuid and/or anongid options? Cheers, Dave -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
