Live data from Hacker News

Systemd: tmpfiles: R /dir/.* destroys root

github.com

1–10 of 21 posts

Re: Systemd: tmpfiles: R /dir/.* destroys root

#5
This almost seems like a generational clash. Anybody who's been around for a while knows that you never ever type rm -rf .* because it can blow up in your face. Lennart's response is tone-deaf because he can't understand how anybody could make that mistake. He's never noticed that rm has started refusing to let you shoot yourself in the foot because he would never think of typing rm -rf .* in the first place. Newer users have never had the opportunity to shoot themselves in the foot with rm and are now tripping over systemd. For all the criticism of systemd not being unixy, this bug reproduces classic unix behavior!

edit: unintentional italics

Re: Systemd: tmpfiles: R /dir/.* destroys root

#7
That bug is like the quintessence of why systemd is bad. Breaking the system when getting user input that previously worked, not even knowing that the existing tools they replaced had safe-guards against this problem, and when confronted with the issue having a first reaction of "that's not a problem".

The one good thing about this is that they did not close it as 'won't fix'.

Re: Systemd: tmpfiles: R /dir/.* destroys root

#9
post #5

This almost seems like a generational clash. Anybody who's been around for a while knows that you never ever type rm -rf .* because it can blow up in your face. Lennart's response is tone-deaf because he can't understand how anybody could make that mistake. He's never noticed that rm has started refusing to let you shoot yourself in the foot because he would never think of typing rm -rf .* in the first place. Newer u…

I don't think Lennart is from a generation that would have experienced this.

http://pubs.opengroup.org/onlinepubs/007904975/utilities/rm....

"The rm utility is forbidden to remove the names dot and dot-dot in order to avoid the consequences of inadvertently doing ..."

Re: Systemd: tmpfiles: R /dir/.* destroys root

#10
post #5

This almost seems like a generational clash. Anybody who's been around for a while knows that you never ever type rm -rf .* because it can blow up in your face. Lennart's response is tone-deaf because he can't understand how anybody could make that mistake. He's never noticed that rm has started refusing to let you shoot yourself in the foot because he would never think of typing rm -rf .* in the first place. Newer u…

Nah, it is more a clash in that not only do the systemd devs feel the need to make their own rm equivalent. But they fail to look into the evolution of defaults for said command before going "its unix, deal with it".

Yeah it is unix, it is the kind of unix that you only find running on some old DEC somewhere. Not on a modern x86 cluster.

This while presenting systemd as being about making Linux something more than a unix clone.

And when people complain about systemd not being unix, it is about how everything is blobbed together via interfaces that keep changing at the whim of the developers.

This in contrast to how someone can pipe the output of a GNU command to the input of a BSD command and get sane results, because the interfaces are known and fixed.

People would be much more accommodating of systemd if the logind part could be used independently of the init part etc.

Post reply on HN