astrogeek |
09-18-2015 02:55 PM |
Habitual's link is new to me as well - looks like a great resource - use it!
I would point out to the OP that what they really need to learn is not a system of abbreviations, but the basic access mode properties of the Unix filesystem. Those "abbreviations" (it is more useful to think of them as the bit flags they actually are) are a representation of the access properties of a file or directory. As such, they really only make sense if you know what those properties are.
As noted, these are Unix access properties or Unix file permissions, and are a core idea inherited by Linux - a very important part of Linux' Unix heritage. You should DuckDuckGo all those terms for a more complete understanding of the concept.
A useful representation of the bit (flag) pattern worth reproducing with a few modifications here ( see full article here):
Code:
|------file mode------|
| |
|
| |----full-----|
|
|-type| | |--basic--|
| | | | |
oo0 000 000 000 000 000
- rwx rwx rwx
- 421 421 421 (Bit value for octal sums)*
... ... ... ... ... ...
| | | | |
| | | | |---- rwx for other
| | | |
| | | |-------- rwx for group
| | |
| | |------------ rwx for user
| |
| |---------------- set uid, set gid, sticky bit
|
|---------------------- file type: regular (-)
directory (d)
character special (c)
block special (b)
fifo (p)
symbolic link (l)
socket (s)
* Flag -> Octal
=============
rwx 7 (4+2+1)
rw- 6 (4+2)
r-x 5 (4+1)
r-- 4
--- 0
Learn the equivalence between octal representation (0-7) and flags (r,w,x) and how they appear in different contexts. It is easy and intuitive once you think about it a little! And it is all important to using a Unix like OS!
Here is another easy to read and complete article on Unix file permissions that expands on these ideas, hope it helps!
And I agree with smallpond - just ask your questions here and you will have a thousand mentors!
|