Timeline for File permissions mechanism on OS level
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 18, 2019 at 10:17 | comment | added | Steffen Ullrich | @PhilipCouling: you are technically correct if you see "move" as rename or link within the same file system and not as copy to new system and delete from old one. I've changed the answer to talk only about "transfer" then to make more clear that the contents of the file gets actually moved to some other place. | |
| Feb 18, 2019 at 10:15 | history | edited | Steffen Ullrich | CC BY-SA 4.0 |
added 7 characters in body
|
| Feb 18, 2019 at 10:14 | comment | added | Philip Couling | This isn't technically correct either. A file can only truly be "moved" on the same file system. That does not require special effort to preserve permissions. If a program wishes to move a file outside of the file system, it has to copy and delete the origional. | |
| Feb 18, 2019 at 10:10 | history | answered | Steffen Ullrich | CC BY-SA 4.0 |