News for hackers. Stuff that matters.
Re:Linux 4.5-rc5: efivarfs fixed to avoid “rm -rf /” brickin... by Etzos on Monday February 22, 2016 @05:01PM (#11154627)
What I was saying was that "rm -rf ." just won't work. You cannot delete the directory you are in directly ("." and ".." are not valid options).

If however you delete a directory that is higher up the directory tree (e.g. the parent directory), it will be deleted.

As far as I can tell this does not violate the POSIX standard[1], as that situation is left as undefined (since in theory the directory you are deleting will chain to the directory you are currently in which is open in the tty).

Edit: The rest of my previous comment was trying to say that the utility of being able to self destruct the current directory is arguable. Why should it be prevented (especially when it could just be hidden behind a flag to prevent accidental destruction)?

Edit2: D'oh. Forgot the reference:

[1] http://pubs.opengroup.org/onlinepubs/9699919799/functions/rm...

Re:Linux 4.5-rc5: efivarfs fixed to avoid “rm -rf /” brickin... by protomyth on Monday February 22, 2016 @05:40PM (#11154917)
"If the current working directory of the process is being removed, that should be an allowed error."

Ok, I read that wrong a long while back, but "allowed error" is really odd. I guess I still side on an error is an error and it should not be allowed.