Timeline for Understanding UNIX permissions and file types
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 12, 2017 at 23:04 | comment | added | rugk | Picture source? | |
| Feb 13, 2015 at 14:10 | history | bounty awarded | Peter | ||
| Feb 11, 2015 at 3:42 | comment | added | Nick T |
Python Master Race solved this backwards problem by banning all "numbers" that start with 0, forcing the user to be explicit if they want anything other than decimal, e.g. hex: 0x1FF, binary: 0b111111111 or octal: 0o777. PYTHON POWER
|
|
| Feb 10, 2015 at 17:46 | comment | added | peterph | ... which in the case of the syscall (or its wrapper) and the binary bearing the same name can be a bit confusing. | |
| Feb 10, 2015 at 17:44 | history | edited | peterph | CC BY-SA 3.0 |
added 39 characters in body
|
| Feb 10, 2015 at 17:39 | comment | added | peterph |
@orion Occasionally it actually is true, e.g. in a C-like code chmod(777) would actually be the equivalent of running chmod 1411 (i.e. the chmod command with argument 1411).
|
|
| Feb 10, 2015 at 14:01 | comment | added | orion | You are wrong about the 777 vs 0777. Both are octal (decimal makes no sense anyway in this case), but in four-character form, the first digit sets the special bits (sticky & setuid). | |
| Feb 10, 2015 at 12:46 | history | edited | ValeriRangelov | CC BY-SA 3.0 |
added 187 characters in body
|
| Feb 10, 2015 at 12:32 | history | edited | ValeriRangelov | CC BY-SA 3.0 |
added 130 characters in body
|
| Feb 10, 2015 at 12:18 | history | answered | ValeriRangelov | CC BY-SA 3.0 |