Stories
Slash Boxes
Comments

SoylentNews is people

posted by cmn32480 on Monday April 17 2017, @08:34PM   Printer-friendly
from the people-that-live-in-a-bubble dept.

Edit: The link.

There were lots of good titles for this submission, as in "Breaking news: Poettering clueless?" to finally disprove Betteridge's law, or "systemd surprisingly not as good as advertised" or "Breaking new: systemd broken" or "Poettering censors critics after epic fail".

Systemd implementation of "rm -rf .*" will follow ".." to upper directory and erase /

How to reproduce:
        # mkdir -p /foo/dir{1,2}

        # touch /foo/.bar{1,2}

        # cat /etc/tmpfiles.d/test.conf

        R! /foo/.* - - - - -

        Reboot.

After the issue was fixed, finally Poettering added this gem of wisdom:

I am not sure I'd consider this much of a problem. Yeah, it's a UNIX pitfall, but "rm -rf /foo/.*" will work the exact same way, no?

The answer to this question, as many clarified for him, obviously is a loud "NO!". After being told a couple of times in no uncertain terms, the thread was closed for non-developers

poettering locked and limited conversation to collaborators 4 hours ago

for which I proposed the "freedom-of-speech" department (although I admit it is a weak proposal).


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2, Informative) by Anonymous Coward on Monday April 17 2017, @09:57PM (3 children)

    by Anonymous Coward on Monday April 17 2017, @09:57PM (#495543)

    poettering locked and limited conversation to collaborators 4 hours ago

    Guys, this is a non-story.
    He didn't stop all conversation. He stopped drive-bys who were throwing shade nearly two weeks after it had been asked an answered.
    Like thelounge-zz [github.com] who's made two contributions in 3 years and neither were systemd related, but felt it necessary to write two posts suggesting poettering is an idiot but otherwise adding no new information to the discussion.
    Project collaborators weren't locked out.

    This submission should never have made it past the editors.

    Starting Score:    0  points
    Moderation   +2  
       Flamebait=1, Troll=2, Informative=5, Disagree=1, Total=9
    Extra 'Informative' Modifier   0  

    Total Score:   2  
  • (Score: 0) by Anonymous Coward on Monday April 17 2017, @11:20PM (1 child)

    by Anonymous Coward on Monday April 17 2017, @11:20PM (#495595)

    Ive made thousands of commits to private repos and maybe 2 to github. Does that mean I too am unqualified to state he is a NIH narcissistic idiot?

    • (Score: 0) by Anonymous Coward on Tuesday April 18 2017, @01:17AM

      by Anonymous Coward on Tuesday April 18 2017, @01:17AM (#495631)

      Yes, actually it does mean you are unqualified because posting an irrelevant comment like that to a bug report would be a far greater narccisism.

  • (Score: 0) by Anonymous Coward on Tuesday April 18 2017, @02:40PM

    by Anonymous Coward on Tuesday April 18 2017, @02:40PM (#495865)

    Well Poettering presented himself as an idiot by making the comment. Because it shows that the creator and maintainer of systemd do not know how a present day rm behaves. And if he is that disconnected from daily operations of _nix, why is he developing a project that is re-implementing large swaths of _nix core code?!