systemd is a system and session manager for Linux, compatible with SysV and LSB init scripts. systemd provides aggressive parallelization capabilities, uses socket and D-Bus activation for starting services, offers on-demand starting of daemons, keeps track of processes using Linux cgroups, supports snapshotting and restoring of the system state, maintains mount and automount points and implements an elaborate transactional dependency-based service control logic. It can work as a drop-in replacement for sysvinit.
Embed a build result badge whereever you need it. Select from
the options below and copy the result over to your README or on
your website, and enjoy it refresh automatically whenever the
build result changes.
Split systemctl and tmpfiles into a separate package
The backstory is that %{?systemd_requires} in all kinds of .spec files
pulls in systemd, which is not always desirable. Upstream has come up
with some solution where they make use of a rpm tag (available in
4.10+) that is only about ordering - cf
https://github.com/systemd/systemd/commit/2424b6bd716f0c1c3bf3406b1fd1a16ba1b6a556
. The commit explicitly states though, that "installing systemd
afterwards [...], does not result in the same outcome."
With this proposed change to our systemd.spec, we could have the cake
and eat it too:
* symlinks in /etc/systemd can be created at install time, permitting
the administrator to install/use systemd as init system in a container
at a later date (enabling "same outcome")
* mandatory tmp directories will be created at install time already,
so the administrator does not have to run `tmpfiles --root=/mycontainer`
before launching the (systemd-less) container.
* the only protruding dependency of systemctl.rpm is libgcrypt20,
i.e. comparatively light.
* the OrderWithRequires feature can be done independently
Sounds like a plan? @mpluskal too #boo980389
I never managed to log in to the suse bugzilla (and just verified that I still can't get there). The account setup for suse infrastructure is a huge mess, usually I just fix issues or do my own workaround just so I don't have to deal with that. In this case preparing a proper fix would've been too much effort for me, so next best thing was leaving a comment and hoping someone notices, latest when other people start complaining that something is broken...
Systemd homed and oomd have been in use in other distros for quite some time. Either together in one package or separated like with OpenMandriva. I'd argue that they would be stable enough for everyone using openSUSE Tumbleweed. Perhaps they can soon be included in the base package. Or as separate packages for when people choose to install them.
I don't know if its considered stable yet for tumbleweed. this is just a suggestion.
Comments 6
This comment has been deleted
Fix submitted. Thanks for the report, but please next time use BZ for this instead.
I never managed to log in to the suse bugzilla (and just verified that I still can't get there). The account setup for suse infrastructure is a huge mess, usually I just fix issues or do my own workaround just so I don't have to deal with that. In this case preparing a proper fix would've been too much effort for me, so next best thing was leaving a comment and hoping someone notices, latest when other people start complaining that something is broken...
Thanks, I just caught this bug too today. Well at least it was updated NOT remotely, otherwise the server would be down.
On Leap 15.1/SLE15SP1, suse-module-tools and systemd(-mini) are inconsistent, conflicting sg.conf.
Can someone either - enable build of systemd(-mini) on Leap 15.1/SLE15SP1 or - disable build of suse-module-tools and purge the binaries from the repo
Systemd homed and oomd have been in use in other distros for quite some time. Either together in one package or separated like with OpenMandriva. I'd argue that they would be stable enough for everyone using openSUSE Tumbleweed. Perhaps they can soon be included in the base package. Or as separate packages for when people choose to install them.
I don't know if its considered stable yet for tumbleweed. this is just a suggestion.