3 ms·
Well, move on ext4 (and most other Linux filesystems) has very specific semantics - keep the file intact in every possible way (including permissions, modificat
by beagle3 7y ago
Well, move on ext4 (and most other Linux filesystems) has very specific semantics - keep the file intact in every possible way (including permissions, modification time, ownership etc) but make it visible through another name.
Please be aware that that the common semantics are that permissions are associated with a file, not with its name (and a file may have a lot of names through hard links, or no name at all - open a file, delete it, and it is only accessible if you have an fd, or with little more work through the inode number)
- Iolaum 7y agoI am indeed on ext4 (and MATE DE). Thank you for the information, although I am not sure what's the next step to have the OS enforce a certain group (and 775 permissions optimally) on all files created/copied/moved (moved is the part that's the biggest pain) within a certain directory.
- beagle3 7y agoYou can write a script that does "inotify_wait" on your directory and changes the permission on anything that's there and doesn't have them.
- em-bee 7y agoa share command that does the necessary permission changes (and optionally the move) would be nice. effectively you want to be able to say: share this file with joe, or share -rw joe john ... file ... destination/; something along those lines that will change the acl as needed.