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) by tangomargarine on Tuesday April 18 2017, @05:38AM (2 children)

    by tangomargarine (667) on Tuesday April 18 2017, @05:38AM (#495695)

    Literally the first three top-level comments were about the lack of a link. WTF are you talking about

    --
    "Is that really true?" "I just spent the last hour telling you to think for yourself! Didn't you hear anything I said?"
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 2) by PiMuNu on Tuesday April 18 2017, @12:11PM

    by PiMuNu (3823) on Tuesday April 18 2017, @12:11PM (#495798)

    > WTF are you talking about

    Its like watching drunk people in a bar. Once they are done fighting about nothing, they will be onto philosophy in no time.

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

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

    The lack of a link is just a sign this is a shit story.
    The actual content of the story is the real problem.
    Its an exaggeration nearly to the point of being a conspiracy theory.

    To recap:

    (1) Not an rm unix command, its a systemd internal function call
    (2) Not censored, comments limited to collaborators
    (3) Limit only made after 3 drive-by flame posts that literally added no new technical information, 10 days after last informative post

    It's also interesting to note that the story was submitted here just 4 hours after the discussion was limited to collaborators.
    Makes me suspicious that the submitter was one of the flamers and is butthurt that his anti-social behavior was rejected.
    What are the chances that some random person 'discovers' this horrible case of censorship so quickly?