Quote:
Originally Posted by Corona688
Not quite sure what you're saying -- that if a file's owner doesn't have read access, but world has access, the owner can't read it? That sort of thing?
Quote:
Originally Posted by scheerchrs
Are you referring to the set UID or Guid bit?
No. I just want to say that if I have a file which has permissions set to 007 then it will be impossible to write, read or execute this file by any user - all owner, group and others will have access denied to that file. If you want to make access to read, write and execute that file to others then it has to have permissions 777. So you can set some permissions for others and don't give that permissions to owner/group but simply it won't work. Similarly if you set some permissions for group but don't give that permission to owner.
But again - what I have said above is based on my observation and I haven't found it guaranteed in any standard, so I don't know if really I can rely on that feature. But such solution seems to be desirable - I can't see any logic in permission like 007, 050 or 077.
Quote:
Originally Posted by scheerchrs
Again, remember that directories are just another sort of file. Not a true "directory"; just a parent-child pointer for organization.
Of course directories still are files, but they are treated by the system in something special way. For example it isn't possible to view and edit directory with vi or emacs. So it is responsibility of a system for make it possible to list a contents of directory, not yours. It is explicitly stated that directory includes i-numbers and again a system is in charge of knowing how to dealt with it, not you. And execute permission is treated in other way for directories than for normal files.