Stories
Slash Boxes
Comments

SoylentNews is people

posted by mrpg on Wednesday May 30 2018, @12:10AM   Printer-friendly
from the one-process-to-rule-them-all dept.

Systemd Introduces "Portable Services" Functionality, Similar To Containers

Lennart is at it again, making complicated things that nobody asked for.

The past several months Lennart Poettering has been working on a "portable services" concept and that big ticket new feature has now landed in Systemd. Portable services are akin to containers but different.

[...] A portable service is ultimately just an OS tree, either inside of a directory tree, or inside a raw disk image containing a Linux file system. This tree is called the "image". It can be "attached" or "detached" from the system. When "attached" specific systemd units from the image are made available on the host system, then behaving pretty much exactly like locally installed system services. When "detached" these units are removed again from the host, leaving no artifacts around (except maybe messages they might have logged).

[...] The primary focus use-case of "portable services" is to extend the host system with encapsulated extensions, but provide almost full integration with the rest of the system, though possibly restricted by effective security knobs. This focus includes system extensions otherwise sometimes called "super-privileged containers".


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 DarkMorph on Wednesday May 30 2018, @10:53PM (1 child)

    by DarkMorph (674) on Wednesday May 30 2018, @10:53PM (#686528)
    Visiting the without-systemd website is the quickest way to discover a long list of operating systems (Linux, BSD, and others) that do not use systemd. Of course systemd is irrelevant outside of Linux, but it is good to have a more thorough list. Some of the more significant Linux distros that come to mind are Gentoo, Devuan, Slackware, Alpine, and Void. I am curious what "not that much positive about it recently" is about regarding Gentoo, whose Portage is perhaps the most powerful package manager in the Linux landscape. The only gripe I have right now is the lack of staff to work on the Portage tree. (It's noticeable on GitHub how many PRs age a bit before they're finally merged in. Official reviewers and devs so short-handed that simply spoon-feeding patches and contributions are backlogged! Fortunately this seems to only be true for extraneous packages not relevant to the core system. There is plenty of attention for the heart of the package tree.) If you want to balance between the leverage Gentoo offers you and offloading some of the necessity to compile things, Calculate Linux might be for you, as it ships default binary packages in the tree that helps you cut down on compiling.

    Personally, given how powerful personal computers' CPUs have become, I can say the number of packages I actually have a problem with spontaneously compiling on a whim due to their compile times, I can count on one hand.

    And I think it's worth noting that the distros that do not supply systemd by default (or at all) often supply the choice of init system. Which is how it should be, by all distros. It would be far more acceptable, I'm sure, had distros such as Debian simply maintained the option of switching the init system rather than forcing just the one.
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 0) by Anonymous Coward on Thursday May 31 2018, @06:21PM

    by Anonymous Coward on Thursday May 31 2018, @06:21PM (#686859)

    > It would be far more acceptable, I'm sure, had distros such as Debian simply maintained the option of switching the init system rather than forcing just the one.

    One can just install sysvinit in Debian if wanted.