> why do you want to create new directories at the root level?
Why not? It's his system, he should be able to do whatever he likes. On most Linux I can rm -rf / all day long and nobody cares. What's the problem with creating root level directories?
Why not? It's his system, he should be able to do whatever he likes. On most Linux I can rm -rf / all day long and nobody cares. What's the problem with creating root level directories?
> On most Linux I can rm -rf / all day long and nobody cares.
So let me turn this around: Why do you think a system that doesn't make it difficult to completely destroy it with one command is a bad idea? "It's my system, I should be able to do whatever I like" is an answer, to be sure.
(N.B.: in fact, "rm -rf /" won't work without "--no-preserve-root" in most Linux distributions, AFAIK, and I presume sudo.)
This does not seem very charitable.
It is fine if the system warns you about doing potentially dangerous operations (which --no-preserve-root amounts to) but it must not prevent you from ignoring that warning.
The decision on which bits of the system I can destroy should be mine, not theirs. That's the issue. At the moment, I am getting pushed out of my machine, bit by bit. Every binary I run is getting report to Apple etc.
It is also possible to destroy the system by dropping your MacBook from a very great height. Should it be padded to cope with this eventuality?