Stories
Slash Boxes
Comments

SoylentNews is people

posted by LaminatorX on Monday September 01 2014, @09:04PM   Printer-friendly
from the puttering-about dept.

Phoronix has an article up about some interesting ideas of Lennart Poettering about what could be a possible future for Linux:

Lennart Poettering of systemd and PulseAudio fame has published a lengthy blog post that shares his vision for how he wishes to change how Linux software systems are put together to address a wide variety of issues. The Btrfs file-system and systemd play big roles with his new vision. Long story short, Lennart is trying to tackle how Linux distributions and software systems themselves are assembled to improve security, deal with the challenges of upstream software vendors integrating into many different distributions, and "the classic Linux distribution scheme is frequently not what end users want."

 
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: 0) by Anonymous Coward on Tuesday September 02 2014, @01:11AM

    by Anonymous Coward on Tuesday September 02 2014, @01:11AM (#88303)

    What is with all this sudo rubbish :P I only ever use that on OSX.

    IIRC there was a proposal a couple of years back for fat binaries and OSX style .app folders on linux. It didn't get very far although I was supportive. If LP is involved in realising something like this, I remove any and all support. Furthermore, the only 'sand-boxing' I want to see is around systemd and it's access to anything that is not a part of the fucking init system.

  • (Score: 2) by tangomargarine on Tuesday September 02 2014, @03:04PM

    by tangomargarine (667) on Tuesday September 02 2014, @03:04PM (#88525)

    You think installing software shouldn't require rights elevation? WTF? And Windows does it, too, only they call it UAC, so it's on all 3 of Windows, Mac, and Linux.

    IIRC there was a proposal a couple of years back for fat binaries and OSX style .app folders on linux.

    Oh, you mean all installed programs should be "portable"?

    It didn't get very far

    Hence why we're continuing to do it the sane way (sudo).

    --
    "Is that really true?" "I just spent the last hour telling you to think for yourself! Didn't you hear anything I said?"
    • (Score: 3, Informative) by cykros on Tuesday September 02 2014, @07:54PM

      by cykros (989) on Tuesday September 02 2014, @07:54PM (#88619)

      Installing software DOESN'T require privilege escalation. Nothing stops you from installing into your own ~/bin, ~/lib, etc.

      Installing it system-wide, of course, does, and should, as system-critical files and directories require elevated privileges to write to them for a good reason.

      • (Score: 2) by tangomargarine on Tuesday September 02 2014, @08:24PM

        by tangomargarine (667) on Tuesday September 02 2014, @08:24PM (#88628)

        Ah, yes, good point. I'm dimly aware there's some debate about where to install stuff to that I'm not privy to.

        --
        "Is that really true?" "I just spent the last hour telling you to think for yourself! Didn't you hear anything I said?"
        • (Score: 2) by cykros on Monday September 15 2014, @09:01PM

          by cykros (989) on Monday September 15 2014, @09:01PM (#93639)

          It's less a matter of debate and more just something to consider when installing software. By installing system wide, you're generally aiming to make it available to more than one user on the system, whereas by installing in a home directory you're putting software in that is only to be used by that user (with normal permissions set up anyway). This makes it more suitable if you are using a multi-user system, such as a public shell server or shared work server. Furthermore, the decision can be impacted on your partitioning (or extra drives) scheme. In many cases, installing software into your /home partition means you'll retain it even if you choose reinstall your root system.