Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!sun-barr!newstop!sun!amdcad!brahms!indra
From: indra@brahms.amd.com (Indra Singhal)
Newsgroups: comp.protocols.nfs
Subject: Re: PC-NFS 3.0.1 net umask question.
Message-ID: <1990Oct14.072403.24521@amd.com>
Date: 14 Oct 90 07:24:03 GMT
References: <1990Oct12.003227.8315@amd.com> <2878@jaytee.East.Sun.COM>
Sender: usenet@amd.com (NNTP Posting)
Organization: Advanced Micro Devices, Inc.
Lines: 28

geoff@bodleian.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) writes:

>Quoth indra@ashirvad.amd.com (Indra Singhal) (in <1990Oct12.003227.8315@amd.com>):
>#In PC-NFS if you do a: net umask 022, even files are created with 755
>#permissions which is not good. 

>Why do you regard it is "not good"? What problems does it cause?

>Just curious.
Well, for one, all files created from the PC show up with their execute
bit set and when doing an ls -F in UNIX, show up with the trailing '*'.
All those executables which aren't really... 

And just that any file that shows up with executable bits in UNIX should
really be executable!

Nothing major... more aesthetic than functional, in my view atleast.

>#And if you try using 'net umask 133' any
>#directories you make are unusable.

>Fixed in the next release.
Thank you!! 

--
iNDRA | indra@amd.com or {ames apple uunet}!amd!indra
      | (Indra Singhal) (408) 749-5445; Advanced Micro Devices
      | MS 167; Box 3453; 901, Thompson Pl., Sunnyvale, CA 94088