a59eb7d78f
$ sudo dnf remove --installroot=/var/tmp/img1 systemd-networkd ... Running scriptlet: systemd-networkd-248~rc4-4.fc32.x86_64 1/1 Removed /etc/systemd/system/multi-user.target.wants/systemd-networkd.service. Removed /etc/systemd/system/sockets.target.wants/systemd-networkd.socket. Removed /etc/systemd/system/dbus-org.freedesktop.network1.service. Removed /etc/systemd/system/network-online.target.wants/systemd-networkd-wait-online.service. System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down (Another option would be make --now do nothing if systemd is not running. But I think that's not too good. 'disable --now' doing nothing would be OK, since if systemd is not running, the service is not running either, so we are in the desired state. But that argument doesn't work for 'enable --now'. And accepting 'disable --now' but not 'enable --now' seems overly complex. So I think it is better to make the scriptlet handle this case explicitly.) Also, let's reindent the file to 4 spaces. Very deeply nested scriptlets are harder to read, and the triggers file is indented to 4 spaces already. |
||
---|---|---|
.github | ||
.lgtm/cpp-queries | ||
.mkosi | ||
.semaphore | ||
catalog | ||
coccinelle | ||
docs | ||
factory/etc | ||
hwdb.d | ||
man | ||
mkosi.default.d | ||
modprobe.d | ||
network | ||
po | ||
presets | ||
rules.d | ||
shell-completion | ||
src | ||
sysctl.d | ||
sysusers.d | ||
test | ||
tmpfiles.d | ||
tools | ||
units | ||
xorg | ||
.clang-format | ||
.ctags | ||
.dir-locals.el | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.lgtm.yml | ||
.mailmap | ||
.packit.yml | ||
.vimrc | ||
.ycm_extra_conf.py | ||
configure | ||
LICENSE.GPL2 | ||
LICENSE.LGPL2.1 | ||
Makefile | ||
meson_options.txt | ||
meson.build | ||
mkosi.build | ||
NEWS | ||
README | ||
README.md | ||
TODO |
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.