News for hackers. Stuff that matters.
Re:Portable systemd services by m3rc on Thursday November 17, 2016 @01:00AM (#12974769)
I used to spend time arguing with people on the internet about how systemd was an actually very useful tool but I never changed any minds and didn't help myself any. Now I just wait and watch for new helpful things it does to show up and I live a much happier life.
Re:Portable systemd services by badsock on Thursday November 17, 2016 @02:06AM (#12975076)
I almost think there should be a divorce. Call it systemdOS and be done with it. At that point every service it subsumes will be seen as a step closer to the obvious end-goal rather than a point of contention. And the other OS can be something like the Gnome2 fork MATE.

It's not a technical thing, it's cultural. The two sides are playing tug-of-war with the same OS, and systemd's winning, but maybe it would be better to have a positive culture around the changes they're making instead of always having people dragging on the rope. Some forks have been good in the past - EGCS/GCC for example.

Re:Portable systemd services by SwellJoe on Thursday November 17, 2016 @02:12AM (#12975111)
> Call it systemdOS and be done with it.

Every major Linux distro has chosen systemd as their future. I think that means whoever wants something different needs to change their name, rather than every major Linux distro changing theirs. Just as the Gnome 2 fans chose a new name for their future based on that lineage.

Re:Portable systemd services by yedpodtrzitko on Thursday November 17, 2016 @05:05AM (#12976063)
If you would tell me "this will just fix & improve init system" then that would a no-brainer. However I feel like the scope of the project has massively changed over time, so people (distros) who agreed with something a year or two ago could have a different opinion nowadays.
Re:Portable systemd services by SwellJoe on Thursday November 17, 2016 @03:58PM (#12981492)
> so people (distros) who agreed with something a year or two ago could have a different opinion nowadays.

Do you have an example of a distro that feels that way?

I only follow Fedora and RHEL/CentOS close enough to know, and they're still quite pro-systemd on all fronts, though there's still some hybrid stuff sticking around for backward compatibility and user comfort (so, a lot of stuff people were used to doing in the past still works the same on systemd-based systems).

Re:Portable systemd services by kasabali on Tuesday November 29, 2016 @03:58PM (#13066233)
> Do you have an example of a distro that feels that way?

Void Linux switched from systemd to runit.

Re:Portable systemd services by mfukar on Thursday November 17, 2016 @03:39AM (#12975576)
> as their future

..and here I was thinking they chose it as an init system.

Re:Portable systemd services by fapjacks on Thursday November 17, 2016 @03:38PM (#12981274)
Well, hopefully now you see that it never was just an init system. It is literally the future of Linux in the eyes of its proponents, as it gobbles up more and more crap. And people wonder why there is opposition to systemd!
Re:Portable systemd services by snaky on Thursday November 17, 2016 @04:35AM (#12975895)
> Every major Linux distro has chosen systemd as their future

Gentoo is a major Linux distro too.

Re:Portable systemd services by SwellJoe on Thursday November 17, 2016 @05:03AM (#12976054)
I don't really stay on top of popularity of distros, but I'd be surprised if Gentoo is in the top 10, in terms of usage. But, when I say "major Linux distros", I mean, specifically: RHEL/CentOS, Ubuntu and Debian, as those are clear market leaders on the server (I mostly pay attention to the server space). Fedora, Mint, and maybe Arch comes into the picture for desktop, I guess? SuSE seems to be on the rise again. All of those are systemd, I think.

I guess one can argue about what level of popularity makes something a "major Linux distro". I, personally, wouldn't put Gentoo into that category, unless I saw some evidence of dramatic increase in its usage.

Re:Portable systemd services by belorn on Thursday November 17, 2016 @05:00AM (#12976033)
Correct me if I am wrong here, but I thought Gentoo user had to make active choices when it came to make, compile and configure an installation, and that Gentoo as a distribution had a hands-off approach when it came to make decisions for the user. Is there a "default" init system, where if the user make no decision they end up with a specific one?
Re:Portable systemd services by pdkl95 on Thursday November 17, 2016 @05:30AM (#12976167)
https://wiki.gentoo.org/wiki/Comparison_of_init_systems

Gentoo officially uses OpenRC (and eudev), which is what you get if you follow the installation handbook. However, Gentoo also encourages choice and allows many options for init, daemon management, etc, which includes systemd. Other options ( are also available, too, at least unofficially.

> if the user makes no decision

While OpenRC is the official default, the "compile and setup everything yourself" nature of Gentoo makes this kind of statement somewhat irrelevant. One of the major reasons to use Gentoo is the ability to pick the components you want in your OS so it meets your specific needs. So yes, while there is a default, the concept of having a "default" is less important when you are installing everything manually.

Re:Portable systemd services by badsock on Thursday November 17, 2016 @02:25AM (#12975173)
Fair enough. It just seems like it might be useful to have a symbolic split of some kind, where people choose a camp instead of trying to pull in both directions. Naming can do that.
Re:Portable systemd services by SwellJoe on Thursday November 17, 2016 @02:39AM (#12975249)
Devuan is, apparently, a fork of Debian without systemd, so there are seemingly reasonable options for going that path. I, personally, won't miss initscripts, but one of our customers has been begging for a Devuan port of our products, so I guess some folks are excited about it.
Re:Portable systemd services by emmelaich on Thursday November 17, 2016 @02:53AM (#12975323)
Only systemd opponents think it is cultural.

Systemd is just fixing things that have been broken for a very long time.

Re:Portable systemd services by 2bluesc on Thursday November 17, 2016 @03:20AM (#12975486)
> Systemd is just fixing things that have been broken for a very long time.

This. I for one don't miss the mess of shell scripts for network management, init, bootloader, cron, etc. I personally think systemd already does 10x better at each of these tasks then the broken scripts have ever done.

Re:Portable systemd services by mfukar on Thursday November 17, 2016 @03:42AM (#12975589)
Changing the syntax of scripts managing devices and services is hardly an improvement by itself. Yes there are some ideas which have resulted in more useful tools for administrators (systemd-analyze and friends), along with more predictable behaviour which again helps administrators a lot, but apart from those systemd is just "fixing" things which were never an issue for the desktop user.
Re:Portable systemd services by SwellJoe on Thursday November 17, 2016 @04:38AM (#12975908)
"Changing the syntax of scripts managing devices and services is hardly an improvement by itself."

That's not what has been done.

systemd unit files are not "scripts". They are declarative configuration files, usually orders of magnitude smaller than the initscripts, network scripts, etc. that they replace. The Apache unit file on RHEL7 is ~17 lines long, and it replaced an initscript that was a couple hundred lines long.

It is a difference of both degree and kind.

Re:Portable systemd services by mfukar on Thursday November 17, 2016 @04:55AM (#12976013)
There's script & executable invocations inside systemd service files as well. They're simply handled differently. Some setups use dedicated units to just do `modprobe X`, and have "easy" dependency management. Some are replacing udev rulesets with systemd units, none of which are "orders of magnitude smaller".

Just saying, the de facto ways of using systemd are starting to diverge a lot from the intended behaviour. And of course, the de facto usage is what we'll judge each piece of software's merits on...eventually.

Re:Portable systemd services by untoreh on Thursday November 17, 2016 @12:05PM (#12979196)
I wouldn't call that diverting, but adapting already available scripts to systemd, and eventually they'll get rewritten
Re:Portable systemd services by mfukar on Thursday November 17, 2016 @02:44PM (#12980753)
Presenting the need to rewrite service scripts as an inevitability is not convincing anybody - and I hate shell scripts more than most.
Re:Portable systemd services by untoreh on Friday November 18, 2016 @04:50AM (#12985578)
I never said that they are going to be forcefully rewritten, I meant that whoever maintains initscripts might eventually rewrite them using systemd units more tightly because they are going be simpler and easier to maintain (in general, not because systemd is making anything any harder). You will still run something with systemd, this something can be the plain executable or an initscript, it is not like systemd checks and makes sure it likes whatever it is running...
Re:Portable systemd services by SwellJoe on Thursday November 17, 2016 @04:00PM (#12981504)
systemd has an initscript compatibility layer; it works with initscripts, and there is no expiration date on that functionality, to my knowledge. What more do you want?
Re:Portable systemd services by makomk on Thursday November 17, 2016 @05:02AM (#12976045)
Except that the more complex unit files still rely on shell scripts - they're just split off into separate files in another directory. systemd simplified init scripts by spraying their content over half a dozen or more different files and then only advertising the size of one them.
Re:Portable systemd services by jononor on Thursday November 17, 2016 @06:56AM (#12976617)
Got any examples?
Re:Portable systemd services by GFK_of_xmaspast on Thursday November 17, 2016 @07:58AM (#12977026)
If you're only a desktop user, where do you interact with systemd at all? I am, and I certainly don't.
Re:Portable systemd services by mfukar on Thursday November 17, 2016 @08:29AM (#12977216)
Precisely. No desktop user ever interacts with the init system.

On the other hand, Linux has a history of _forcing_ desktop users to mess with device management for the simplest of tasks, e.g. making their audio devices work.

Re:Portable systemd services by alphapapa on Thursday November 17, 2016 @03:10PM (#12981005)
> No desktop user ever interacts with the init system.

So you've never restarted a service on your desktop system?

Re:Portable systemd services by mfukar on Friday November 18, 2016 @03:06AM (#12985144)
On both Windows & macOS, I've created & managed services, and never had to restart them after they were deployed.

I don't use a Linux desktop (I often retry) because that is unattainable.

Re:Portable systemd services by beojan on Sunday November 20, 2016 @06:19PM (#13001843)
You've never changed the configuration of a service?
Re:Portable systemd services by yarrel on Thursday November 17, 2016 @03:27AM (#12975522)
The claim that systemd doesn't just fix init scripts packs two lies into a very small amount of space.
Re:Portable systemd services by wmf on Thursday November 17, 2016 @06:45PM (#12982936)
I don't know about that. I like systemd but I think it has a very different culture from classic Unix. (I never liked Unix culture.) It is probably possible to fix many of Linux's problems while keeping the old culture but no one can be bothered to do it.
Re:Portable systemd services by alphapapa on Thursday November 17, 2016 @03:08PM (#12980987)
The parallels between the systemd/anti-systemd "war" and the recent U.S. election are striking. I wonder if a "trumpid1" systemd competitor is in the future...haha...ha...
Re:Portable systemd services by upofadown on Thursday November 17, 2016 @03:27AM (#12975528)
> Call it systemdOS and be done with it.

I think of systemd as one component in an attempt to create a good desktop environment based on the Linux kernel. Sort of like how Android is an attempt to create a good phone environment based on the Linux kernel.

Based on that, I think it makes more sense to come up with a separate name for something like a Gnome/Wayland/Weston/systemd/Linux combination. While we are at it we could come up with a separate name for a Linux based system configured primarily by writing scripts. We should stop pretending that there is some sort of generic combination of things called "Linux".

Re:Portable systemd services by fnord123 on Thursday November 17, 2016 @04:58AM (#12976022)
>I think of systemd as one component in an attempt to create a good desktop environment based on the Linux kernel.

systemd works on systems as small as embedded systems up to huge hpc systems. It's not just a desktop thing.

Re:Portable systemd services by dozzie on Thursday November 17, 2016 @05:24AM (#12976129)
...for some value of "works".
Re:Portable systemd services by jononor on Thursday November 17, 2016 @07:07AM (#12976686)
...works better than sysvinit, and upstart.
Re:Portable systemd services by dozzie on Thursday November 17, 2016 @07:35AM (#12976868)
Except when it doesn't or when it's pain in the ass (embedded systems, or so I hear).
Re:Portable systemd services by mfukar on Thursday November 17, 2016 @08:57AM (#12977434)
You heard right.
Re:Portable systemd services by dasyatidprime on Thursday November 17, 2016 @03:56AM (#12975665)
I've been tentatively calling the former FDO/Linux or XDG/Linux, FWIW.
Re:Portable systemd services by mfukar on Thursday November 17, 2016 @03:40AM (#12975579)
Android is hardly a component. It's a fork. Systemd should also be a fork, that was the GP's opinion too, wasn't it?
Re:Portable systemd services by sandGorgon on Thursday November 17, 2016 @03:03AM (#12975383)
It's very interesting how the whole article (and Lennart) shies away from even uttering "package manager" and instead talks about containers.

This is fundamentally an implementation of Lennart's blog post - http://0pointer.net/blog/revisiting-how-we-put-together-linu.... That article used the words "We want an efficient way that allows vendors to package their software " ... which was followed by a storm of angry systemd-is-the-borg-it-needs-to-die tweets and articles.

Even on HN - the response to this article seems fairly muted... although it is a bigger political issue than even init systems. I wonder what the response would have been to "systemd introduces new portable packaging format"

Re:Portable systemd services by oblio on Thursday November 17, 2016 @04:21AM (#12975817)
If no one will say it, I will: it's stupid that we have multiple package managers and package formats.

There's no fundamental technical reason Linux couldn't have just 1 extensible package format and 1 extensible package manager. All the reasons for the split are social ("I like A"), political ("we want to be able to control A") or historical ("A came first, we built our house on A, we can't abandon A").

Re:Portable systemd services by majewsky on Thursday November 17, 2016 @07:54AM (#12977003)
The historical argument might be the biggest one, from my own experience with the steaming pile of shit that is RPM: https://blog.bethselamin.de/posts/argh-pm.html
Re:Portable systemd services by oblio on Thursday November 17, 2016 @10:16AM (#12978101)
I actually recently took a much shallower dive through RPM than yours (http://blog.oblio360.com/2016/08/23/rpm-install/). I knew that RPM was not that loved as a format, but what you've described there truly is "insane" (I know that you used that word many times in the article, but it fits the situation).
Re:Portable systemd services by digi_owl on Thursday November 17, 2016 @11:17AM (#12978724)
Really makes one wonder why RH is still allowed to set the direction of Linux as a whole. Oh wait, money...
Re:Portable systemd services by legulere on Thursday November 17, 2016 @06:24AM (#12976433)
Even with the same package managers, packages are still incompatible from different repositories because of differing assumptions about the underlying system and differing packages for the dependencies.

Converting between the differing package formats is actually relatively easy and tools like `alien` exist, that do that.

Re:Portable systemd services by oblio on Thursday November 17, 2016 @08:30AM (#12977223)
I know about that, I actually hate those "underlying system" differences even more. With a bit of forethought we could have covered all the use cases and not have silly things such as /etc/redhat-release vs /etc/debian_version.[1] There's no reason we couldn't have had a "/etc/distro-info" with a standardized format for writing down the distro name, the platform and the full distro version (branch/release, minor release, revision, build number, etc.). And there's thousands of these differences.

As I said: social/political/historical reasons bringing us down.

[1] I know about lsb_release, but that's an example of an afterthought, not a part of the initial design.

Re:Portable systemd services by vamega on Thursday November 17, 2016 @09:38AM (#12977771)
"/etc/os-release" is present in most newer releases. Sounds exactly what you want from "/etc/distro-info"
Re:Portable systemd services by oblio on Thursday November 17, 2016 @10:13AM (#12978068)
Whaddayaknow, I missed that file. Apparently it's a Freedesktop standard (https://www.freedesktop.org/software/systemd/man/os-release....).

My point still stands, something like this should have been included from the first releases of Linux distros, 20 years ago. And that was just a random example I came up with after 2 minutes of trying to prove a point. There's many, many more like it.

Also, just for kicks I took at look at the spec and...

1. ANSI_COLOR is funny:

> A suggested presentation color when showing the OS name on the console. This should be specified as string suitable for inclusion in the ESC [ m ANSI/ECMA-48 escape code for setting graphical rendition. This field is optional. Example: "ANSI_COLOR="0;31"" for red, or "ANSI_COLOR="1;34"" for light blue.

2. And some parts are scary:

> parameters may be set using os-release

Oh-oh! Everything is optional! That's really bad for a RFC.

Re:Portable systemd services by qznc on Thursday November 17, 2016 @04:27AM (#12975845)
Why do have so many programming languages? Because they fulfill different needs. C and Python are used for different things. Yet, there is overlap, which creates a constant tension. When do you rewrite your Python module into C for better performance?

Likewise, different packaging formats exist for different needs. Docker and Ubuntu Snap are for different needs, yet they overlap. Systemd did initially not care about packaging and containers. Yet, there is an overlap, like "How to do logging?". Docker and Systemd both grow and overlap more and more.

Re:Portable systemd services by oblio on Thursday November 17, 2016 @04:32AM (#12975870)
We're talking about different things here. deb/rpm serve the same role. yum/apt ditto.

We have gratuitous differences which could have been prevented with a better design. See for example even the mess in the rpm world where a SUSE rpm may or may not work on Red Hat.

Re:Portable systemd services by qznc on Thursday November 17, 2016 @04:22AM (#12975821)
I like the vision Lennart describes.

My hope for systemd is that it unifies the Linux Desktop universe. The Free Desktop movement has stopped doing that.

There is a time for exploding into lots of variants and a time for unifying. Remember the time, when git came up? There was an explosion of DVCSs (Monotone, Darcs, Bazaar, and more). For now, the world has mostly settled on git with Mercurial as a secondary.

Re:Portable systemd services by pmlnr on Thursday November 17, 2016 @07:06AM (#12976683)
Because unification kills diversity, which kinda kills progress and new ideas, which kills free. ( Free != free ).
Re:Portable systemd services by tech2 on Thursday November 17, 2016 @04:27AM (#12975843)
This (packaging/installation/management) seems to be a solved problem for those who've used Nix. Does it need solving again in a Lennart-specific way?
Re:Portable systemd services by chriswarbo on Thursday November 17, 2016 @07:49AM (#12976968)
I primarily think of Nix as being a build tool akin to Make rather than a package manager. It's almost as if the flakiness of Make made us think that building applications or libraries was somehow a different thing to building an OS, so we invented a separate thing called a package manager. Then Nix came along and showed that a single build tool can be used for something as simple as a preprocessor (Nix's string quasiquotation is very nice), through to compiling applications, bundling applications into a coherent OS, and even orchestrating clusters of real & virtual machines.

I wonder if this proposed system would be as amenable to handling such a wide variety of software (e.g. https://nixos.org/nixpkgs/manual/#chap-language-support ) on such a wide variety of platforms (e.g. https://github.com/NixOS/nixpkgs/tree/master/pkgs/os-specifi... ).

Re:Portable systemd services by digi_owl on Thursday November 17, 2016 @07:44AM (#12976922)
Poettering have a bad habit of not looking before coding (or blogging). That said, i think that blog predates Nix, but it sure as hell do not predate Gobolinux. And Gobolinux does its thing using mostly shell script (with the odd Python or binary for performance reasons).
Re:Portable systemd services by chriswarbo on Thursday November 17, 2016 @07:53AM (#12976998)
> i think that blog predates Nix, but it sure as hell do not predate Gobolinux

The blog post is dated September 2014. Nix had been around for at least a decade by then (e.g. see https://nixos.org/docs/papers.html ).

Wikipedia says Gobolinux is about the same age as Nix.

Re:Portable systemd services by wmf on Thursday November 17, 2016 @06:50PM (#12982973)
In Linux, the term "package manager" is loaded with baggage like twisty mazes of dependencies and kitchen-sink repositories. This proposal doesn't have those.
Re:Portable systemd services by dkarapetyan on Thursday November 17, 2016 @01:00AM (#12974768)
Isn't ubuntu snap already doing all this? The competing standards I don't think help in this regard. Now to make a "portable service" I will need to make sure whatever I do can be used as a snap and a systemd portable service.

Why is it so hard to settle on a standard when it comes to this stuff? The same confusion exists when it comes to rpm and deb packaging formats. At the end of the day both do the same thing and yet to deliver software to redhat and debian systems you have to double your packaging effort.

Re:Portable systemd services by derefr on Thursday November 17, 2016 @01:10AM (#12974811)
The RPM/Deb split, at this point, isn't so much about packaging formats, as it is about dependency graphs. Even if the two distro "families" of Redhat and Debian shared a common packaging format, a package would still have to be built—or at least specified—twice for them, because each family would still have its own set of deps that are factored out in incompatible ways to the deps of the other family. (For example, in Debian land, if your package wants to declare a dependency on OpenSSL, that might mean a package dependency on any of 'openssl', 'libssl1.0.0', 'libssl1.0.0-dbg', or 'libssl-dev'. RHEL et al do not have an isomorphic set of packages that these dependencies could be mapped to.)
Re:Portable systemd services by vbernat on Thursday November 17, 2016 @01:40AM (#12974960)
This is already the case for SuSE and Redhat. Package names are different, RPM macros are different. Doing a package that works for both is gruesome. Also, at the time of SysV, you had to use two different init scripts.
Re:Portable systemd services by niemeyer on Thursday November 17, 2016 @08:44AM (#12977321)
Such competing efforts are actually a form of non-voluntary collaboration. rpm and deb (and apt, yum, synaptic, ...) have significantly evolved together along the years, looking at each other. This happens all the time, and is happening again here.. the snap format and snapd evolve based on previous knowledge, and it's no surprise that the linked LWN article seems quite inspired by snaps (I'm biased as a snapd designer/developer).

Let it come.. we'll be watching and picking up the good ideas too. And working hard to make sure snaps continue to win on merit, rather than lack of competition.

Re:Portable systemd services by wmf on Thursday November 17, 2016 @01:39AM (#12974954)
Presumably portable services will work on Ubuntu so you could skip the snap.

There will never be agreement on standards that are used as strategic weapons in developer mindshare turf wars between companies using monopoly-or-die-trying business models.

Re:Portable systemd services by mateuszf on Thursday November 17, 2016 @01:09AM (#12974808)
Because systemd is more popular and cross distros.
Re:Portable systemd services by qwertyuiop924 on Thursday November 17, 2016 @09:47AM (#12977839)
I'm sorry, but I can't keep a straight face hearing the phrase "portable systemd."

I don't care what init system you run, but if you're writing userland software (GNOME, for one), than what init system I run is none of your damn business. For that matter, ideally you'd at least try to support the *BSDs.

As much as Systemd is the borg, I could at least live with that. I cannot live with the fact that systemd maintainers continue to say that having high-level userland software link to libsystemd is viable and acceptable. I cannot live with the fact that systemd continues to violate widely-accepted defaults for no reason (kill all processes on logout? really?). I cannot live with the fact that Lennart has widely stated that you should ignore POSIX and that all systems other than Linux don't matter.

Re:Portable systemd services by progman on Friday November 18, 2016 @03:04PM (#12989667)
> high-level userland software link to libsystemd is viable and acceptable

This is a direct violation of the KISS principle which made Unix and Linux so great. Not only do they want to intertwine user software with system software, now they even want an additional layer of abstraction on the _system_ level!

I think we need a counter strategy against the aggressive takeover of the Linux land before it is too late. I have nothing against people who love systemd. If they want it they should use it. But any Linux user should also have the option to get rid of systemd _completely_ if it turns out to be a failure.

Init systems and system services should be as replacable as desktop environments! Only if systemd is aiming to be "portable" like that than I can live in peace with it.

Re:Portable systemd services by qwertyuiop924 on Friday November 18, 2016 @05:21PM (#12990566)
>I think we need a counter strategy

The Gentoo folks, as well as many of us Arch users, are with you. Gentoo in particular has been aggressively forking and maintaining patch sets for any of the software that has succumbed to the cancer (the *kits, various desktop software, DBUS, GNOME, and most notably udev. Although if they weren't needed for some pieces of software I use, I'd gladly chuck 90% of that stuff). So yeah, if you want to help, that's where to contribute your effort.

Re:Portable systemd services by progman on Saturday November 19, 2016 @03:36AM (#12992600)
> So yeah, if you want to help, that's where to contribute your effort.

Gentoo and Arch are good options. However, in the long term classical Linux will likely only be able to run on retro systems and FREE HARDWARE! If Gentoo and Arch want to survive they should focus on free hardware pretty soon.

I think so because upcoming mainstream hardware will likely all be based on UEFI/SB. SB is yet optional but I expect it to be mandatory soon. Only Linux with certified kernels -- likely systemd Linux -- will be supported on those systems. I don't like that because I want to be able to install up-to-date kernels and software at any time without messing around with proprietary certificates.

The Monster 6502 [1] was an excellent starting point into a world of discrete SMD cpus. I hope there will also be a 16/32-bit cpu capable to run Linux (or its successor). At least 68katy [2] is capable.

The most promising project however is RISC-V which will hopefully be available with non SB-mainboards.

[1] http://monster6502.com

[2] http://www.bigmessowires.com/category/68katy/

[3] https://riscv.org

Re:Portable systemd services by qwertyuiop924 on Saturday November 19, 2016 @06:29AM (#12992988)
I'm dubious of that assertion, although it is good to know how the free hardware projects are going. We may well get a cert for UEFI SB, and if we don't, then someone will crack it sooner or later.

Honestly, the only thing that keeps me from migrating to the BSDs at this point is Steam.

Re:Portable systemd services by progman on Saturday November 19, 2016 @08:13AM (#12993332)
> We may well get a cert for UEFI SB,

As long as the vendors cooperate you will be fine. We will see how it works at Win 11+.

> and if we don't, then someone will crack it sooner or later.

Other people may be able to live with it but for me this is an unacceptable option. Either a system fully supports Linux or BSD, or I take another one.

Re:Portable systemd services by AceJohnny2 on Thursday November 17, 2016 @01:15AM (#12974831)
Tangentially, glad to see Jon finally put up a signup banner for non-subscribers :)

(see discussion 3 months ago: https://news.ycombinator.com/item?id=12224408)

Re:Portable systemd services by hardwaresofton on Thursday November 17, 2016 @04:25AM (#12975832)
Excited to see where this goes. After some recent issues with running docker on arch (vague devicemapper issues, inability to stop containers properly), and my newfound love for systemd using it from day to day on my personal computer (writing unit files is pretty darn easy), I've actually been seriously considering going back to writing applications that just get run as processes, and managed by something other than me.

If my understanding is right, the industry went:

CGI -> processes -> VMs -> containers

I'm thinking of going back to step 2.

Re:Portable systemd services by Karlozkiller on Thursday November 17, 2016 @02:06AM (#12975077)
This should surely stop the critics from saying systemd is doing too much and is bloatful.

No, but seriously I understand the reason why you'd want this, but what stops systemd from being divided into smaller modules? Like the Linux I'm used to.

Re:Portable systemd services by SwellJoe on Thursday November 17, 2016 @02:15AM (#12975128)
systemd is modular, and is divided into many components. There are several dozen binaries in a systemd package. Where do you believe the lines should be drawn differently?
Re:Portable systemd services by mfukar on Thursday November 17, 2016 @03:44AM (#12975599)
> There are several dozen binaries in a systemd package.

That's not what modular means. Can you use only parts of systemd if you wanted to? Can I e.g. use the very useful dependency-based service initialisation but keeping my log facilities and networking management intact?

Re:Portable systemd services by SwellJoe on Thursday November 17, 2016 @03:54AM (#12975654)
"Can you use only parts of systemd if you wanted to?"

Yes, though most distributions have chosen to use more than just the init functionality.

"Can I e.g. use the very useful dependency-based service initialisation but keeping my log facilities and networking management intact?"

No (logs) and yes (networking). Logging from systemd components, as far as I know, have to go through journald, but journald can send it as plain text to syslog, if you want it to. So, kinda yes on that one, too.

networkd didn't even exist yet when many people began using systemd for their init, and it is entirely possible to use other methods of managing your network services. RHEL still, AFAIK, has a hybrid model that keeps a lot of the old configuration files even though they have switched to systemd for a lot of stuff. Maybe it uses networkd on the backend; I haven't needed to find out, as the config files work the same way they always have.

I think the confusion comes from the fact that very few people want to only use one component of systemd. Even though you can, there is value in all of the pieces working well together and providing a consistent interface and API. Most distros that switch, choose to switch a lot of things over at the same time, because it's just nicer to do so, not because they had to. And, the people who hate systemd don't want any of it, so they never learn enough to know that they probably could get the bits from it they want without being tied to all of it.

Re:Portable systemd services by mfukar on Thursday November 17, 2016 @04:18AM (#12975800)
There is value in only some of the pieces working together, too. I'm sure having all the pieces together makes sense for some setups, but not all.
Re:Portable systemd services by Karlozkiller on Thursday November 17, 2016 @02:47AM (#12975294)
What I did mean was that at least from my understanding of it, you get systemd, and then you have all of systemd, unable to replace one part of systemd with some other package to handle that specific task.

One of the features I would like to see for example is less binary logging and this journalctl madness. Binary logging makes it harder for me to plug in other programs to parse the logs or whatever I want to do.

So what I would like to see is modularity in the sense where I can choose to run systemd as an init system, and something not-systemd for logging, or for scheduling or whatever.

Re:Portable systemd services by SwellJoe on Thursday November 17, 2016 @03:09AM (#12975417)
On the logging question, does the ForwardToSyslog option not do what you'd like?

Most components can be replaced (the journal isn't one of them, AFAIK, but most others can, and the journal can be configured to send things to a plain text log). Personally, I don't find the binary log to be that problematic. It is taking some getting used to, of course. 20+ years of muscle memory for grepping and awking and cutting text log files is hard to overcome, but the amount of help the system provides is nicer. It's better documented and better at guiding the user than the old way, IMHO.

Which brings to mind something I like about systemd becoming standard that rarely gets discussed, I think: It brings a level of consistency that some other UNIX systems have had for a long time; the BSDs, for instance, have the feeling of all of the pieces having been designed to work together. Linux has never had that feeling; but with systemd, a large amount of Linux real estate now feels that way. The documentation correctly references other components docs. The way various components work together is reasonably documented because they were built at roughly the same time by roughly the same people (or at least people who interacted during the design), so the interfaces are clearly delineated. That's cool, I think.

So, sure, I'm having to learn new stuff every time I interact with systemd, and that's frustrating. I know Linux like the back of my hand, so when I find myself having to read the docs for even simple stuff, I get grumpy. But, I get over it. It's gonna be fine, and we'll all get through this learning curve.

Re:Portable systemd services by dozzie on Thursday November 17, 2016 @05:27AM (#12976148)
> On the logging question, does the ForwardToSyslog option not do what you'd like?

Of course not. Now you have two logging services. Hardly a replacement.

Re:Portable systemd services by SwellJoe on Thursday November 17, 2016 @03:23PM (#12981130)
So, to be clear, it is systemd itself that expects to be able to spit its logs to journald. Other services (most of the rest of a system) can log to whatever target it wants, including plain text files or a running syslog.

The idea is that systemd wanted to not implement a bunch of different logging APIs within systemd itself. They wanted one logging API across all of the systemd components; and, then, if the end user needs logs to some other target, they use one utility (journald) to spit it out to that other target.

I believe the thinking that went into this decision was sound. The alternative would be for every component in systemd to know about multiple logging targets, which would be exactly what people are accusing systemd of being (but isn't, in this case): bloated. systemd and all of its components log one way, allowing for a very simple logging code path. journald allows you to use those logs in many ways.

So, either, systemd would need to expand to include support for a bunch of different logging mechanisms, or it would support one simple logging API and provide a way to export those logs to other targets.

Are you here arguing that systemd should be made larger and more complicated, in order to support other kinds of logging (like syslog and plain text files) without the help of journald?

To me, this looks like modularization and componentization at a reasonable level of abstraction. It simplifies the logging code for every component, while also providing a means for end users to consume the logs in the ways they prefer, including plain text.

Re:Portable systemd services by dozzie on Thursday November 17, 2016 @04:12PM (#12981621)
Your reasoning is invalid. It would be just enough if systemd supported syslog, with a mechanism for buffering logs initially until the syslog starts, which systemd already needs and has anyway. It was not a choice between new, custom service and making things complicated by supporting every possible log service.

It's not modularization. It's scope creep in pure form.

Re:Portable systemd services by SwellJoe on Thursday November 17, 2016 @05:23PM (#12982291)
There's an argument to be made for picking an existing standard. I probably would have, were I developing something like systemd, because I'm lazy. But, the path they've chosen is more flexible than that, and has some other benefits. syslog is a very old standard, at this point, and has many limitations and issues, particularly in a world where a deployment might involve hundreds of instances of a service.

Lennart wrote a pretty good summary of why journald exists, and I think it holds up to scrutiny pretty well:

https://docs.google.com/document/pub?id=1IC9yOXj7j6cdLLxWEBA...

One could argue about what the right "one log" target is, but I doubt one would come up with syslog. syslog-ng and rsyslog were incremental improvements, and solve some of the issues, but they're 18 and 12 years old, respectively, and both pre-date containers, widespread cloud computing (AWS came in 2006), service-based architectures, etc. When they were new, we still had servers that did one thing.

One can also argue about whether journald is the right implementation, even if we acknowledge that a new standard is needed, we don't have to agree that journald is the right one. But, I wasn't writing the code, and what they came up with is pretty good. I don't have any major complaints about it, except that I have to learn some new stuff.

So, I respect the argument that they should have chosen an existing standard for logging, but I also see the reasons why they chose to build something new. I think if I'd been involved in the decision, I probably would have come down on the side of journald, in the end (but would have needed some convincing).

Re:Portable systemd services by dozzie on Thursday November 17, 2016 @05:38PM (#12982414)
> Lennart wrote a pretty good summary of why journald exists [...]

Of the reasons he wrote it, half of them is not met by journald, and the other half could be implemented without much trouble on top of syslog. Hard to call it "holding up to scrutiny pretty well".

And I fail to see how journald is better than syslog in the age of containers.

Re:Portable systemd services by SwellJoe on Thursday November 17, 2016 @06:47PM (#12982955)
I think we'll just have to agree to disagree, then. You don't like systemd or journald, and that's fine. To me, it looks like systemd and journald solve the problems they set out to solve in a reasonable way; I don't like everything about it, but I didn't like a lot of things about initscripts and syslog, either, and think we've moved up in the world by switching.

Hopefully, you'll be able to direct your energies into maintaining one of the distros that has chosen to stick with the old way of doing things (Devuan seems to be the most promising one coming up, but I guess there are several others). I'm not opposed to folks having choices, as long as I don't have to maintain them.

Re:Portable systemd services by dozzie on Thursday November 17, 2016 @06:56PM (#12983022)
To detach from discussion at this point is fine, I guess. But please entertain my question about containers. I'm yet to try those out, be it Docker or some other packaging solution[#], so I'd like to know beforehand what is different with them in logging than what I usually expect from regular log centralization.

[#] LXC/libvirt type containers I see as merely cheap VMs, though I like them very much.

Re:Portable systemd services by SwellJoe on Thursday November 17, 2016 @10:05PM (#12983980)
I think me backing off is the only useful thing for me to do. We both seem pretty convinced about what the right solution to these problems is, and neither seems to be budging. I don't really think either is right or wrong; I have a preference and so do you.

As for Docker, you can continue to use the logging tools you're used to, or you can have it output to the journal. Docker supports many logging drivers: https://docs.docker.com/engine/admin/logging/overview/

Re:Portable systemd services by brainfire on Thursday November 17, 2016 @03:28PM (#12981183)
If you draw the line there you're probably running a dozen "logging services" on any given system.