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: 5, Insightful) by Anonymous Coward on Monday April 17 2017, @09:04PM (4 children)

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

    The best part is the dipshit actually wonders why people are resistant to running his code on their computers. IT'S BLUNDERS LIKE THIS, MORON!

    This is some serious amateur hour bullshit. The dumbass doesn't even have a complete grasp of how a *nix system works, yet he's in charge of maintaining CRITICAL. SYSTEM. CODE. What's next, letting him infect the mainline kernel with his crap?

    Systemd is malware, and any distro that relies on it is defective. Thanks a lot asshole, you've broken 90% of the Linux world.

    Starting Score:    0  points
    Moderation   +5  
       Insightful=4, Informative=1, Total=5
    Extra 'Insightful' Modifier   0  

    Total Score:   5  
  • (Score: 1, Insightful) by Anonymous Coward on Monday April 17 2017, @09:26PM (2 children)

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

    Not sure if Poettering has ever submitted code to the kernel, but his compatriot Sievers have.

    Code that Torvalds was less than happy about, on more than one occasion.

    Sadly Sievers seems to be on good terms with GregKH, a highly active kernel developer and maintainer of the "stable" branches of each kernel release.

    Thus one may wonder what will happen to the Linux kernel quality once Torvalds decides he is too old to herd bobcats, as GregKH is the most likely candidate to take over that job...

    • (Score: -1, Redundant) by Anonymous Coward on Monday April 17 2017, @09:58PM (1 child)

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

      That is all.

      • (Score: 0) by Anonymous Coward on Wednesday April 19 2017, @08:39AM

        by Anonymous Coward on Wednesday April 19 2017, @08:39AM (#496197)

        Would Torvalds mind if the fork was called "Torvix"?

  • (Score: 2) by FatPhil on Tuesday April 18 2017, @07:48AM

    by FatPhil (863) <{pc-soylent} {at} {asdf.fi}> on Tuesday April 18 2017, @07:48AM (#495740) Homepage
    He had Kay Sievers do that kernel dirty work. Had. http://www.theregister.co.uk/2014/04/05/torvalds_sievers_dust_up/
    --
    Great minds discuss ideas; average minds discuss events; small minds discuss people; the smallest discuss themselves