4 ms·
> pleasedontdelete flag For some programs (rm isn't one of them), removing the write permission is sufficient to get an interactive prompt when you try to over
by derefr 11y ago
> pleasedontdelete flag
For some programs (rm isn't one of them), removing the write permission is sufficient to get an interactive prompt when you try to overwrite/truncate/delete the file.
I really like OSX's current metaphor, where files that haven't been touched in a while get "locked", and must then be "unlocked" to modify them further. Phrasing it in terms of stability rather than permission makes a lot of sense to me. It's too bad the metaphor isn't echoed in the CLI.
- alcari 11y ago`rm` is definitely one of them, it's just suppressed by the `-f` flag. (examples from Ubuntu) $ touch foo $ chmod -w foo $ rm foo rm: remove write-protected regular empty file ‘foo’? There's also the immutable attribute many modern filesystems support, which prevents the file from being modified unless the attribute is removed. $ sudo chattr +i foo $ rm foo rm: remove write-protected regular empty file ‘foo’? y rm: cannot remove ‘foo’: Operation not permitted
- ethbro 11y agoThat's a surprisingly good idea for UAC too. People would hate that it's non-deterministic (from "how will my program run on a user's system" perspective), but makes more sense than other approaches. If I'm tapping a file that's been sitting there since the OS was installed and hasn't been touched since... Probably fair to ask me to confirm!