On 11/04/2021 18:45, paka wrote:
> and the action is quite expected
> read-only files may be copied but not removed or executed.
> that is the reason for "read-only"
What? read-only means: You are allowed to read the file, but not to
write to it. Whether you can "move" or "remove" it (i.e. unlink() it,
i.e. remove an entry from the directory), is determined by the
permissions on the directory, not the file. This is how it was desinged
by the gods (Thompson, Ritchie).
By the way: Actually, you cannot "delete" or "remove" a file in Unix,
it's impossible from user land. The only thing you can do is unlink it,
i.e. remove entries from a directory, and once the link count is zero
(which may or may not be the case after one "rm"), the OS will delete
the file for you.
(MS-DOS, and it's newer versions under the name of Windows "work"
differently, for loose definitions of "work". And it's inconsistent, as
we see...).
> why are you giving read-only permissions to the files?
Maybe because every second post on this list tells you to NOT touch the
raw files?
Best regards,
Michael
--
Michael Staats
[email protected]
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]
