3
Contributors
3
Replies
19
Views
4 Years
Discussion Span
Last Post by chriswelborn
1

All well and good, being able to specify Linux/Unix file permissions with octal encodings, but these days there are much better options, such as the symbolic permissions supported by chmod, such as "chmod ugo+rw file/dirname", etc. Why force users to know octal permission encodings when they can use much simpler, and more easily understood, dialects? FWIW, I have been working with Unix since the early 1980's, and Linux since the 90's. I almost NEVER use octal encodings any longer for file/directory permissions any longer.

0

hi rubberman, agree with you setting up permissions for file. The best way to go is to use symbolic permissions. But setting up some configuration still does require the knowledge of the octal encodings (in my own opinion) like setting up Vstfpd, apache settings and etc.. But i'm not sure whether the new apache settings and vsftpd can also use symbolic permissions on their configuration.

0

wow, i never knew how that worked. I always use the symbolic method (chmod +rw). So it's just a binary chart basically.

 R | W | X = 4 | 2 | 1
-----------------------
 x`| x |   = 4 + 2      = 6

that's awesome, and good to know.

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.