> you imagine what things like these are doing to your backup
> concepts in a multi-user environment? Somebody touched a file
> with an editor, did not change anything but the cursor position
> in a ressource fork and the whole file goes to amanda the next
> night...
>
> Or what if I delete a user from my system. Imagine the system
> administrator scanning the whole filesystem for ressource forks
> where this particular user has stored now unneeded configuration
> data and stripping all these forks from the respective files -
> making changes to these files and forcing everything that user
> *ever* touched on backup the next night (which is exactly the
> opposite of the right thing to do, because I don't want to
NO NO NO.
The forks would have the same permissions as the file.
Random J luser on your system couldn't add fork data to /bin/bash.
Forks should be stored as directories, and initally created with the same
permissions as the files.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html