| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
| |
We need to do better here, but for now let's at least not trick
users into nuking their graphical environment. Inspired by #16548.
|
| |\
| |
| | |
Fix coredumpctl operation with zstd-compressed journals
|
| | |
| |
| |
| |
| |
| |
| | |
The docs for XZ don't seem to answer this at first blush, or maybe
I'm looking in the wrong place... This might make XZ less terribly slow,
but on the other hand, almost nobody uses it, so it doesn't matter that
much.
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
Add --image= switch to firstboot, similar to --root= but with support for operating on disk image
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| |\
| |
| | |
repart: add new CopyBlocks= setting
|
| | | |
|
| |\ \
| | |
| | | |
pid1: add support for allowing to pass in random seed via kernel cmdline
|
| | |/ |
|
| | | |
|
| | |
| |
| |
| | |
Most of them were reported by Fossies.org
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
Make busctl stdout/stderr split consistent
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We would print the error sometimes to stdout and sometimes to stderr. It *is*
useful to get the message if one of the names is not found on the bus to
stdout, so that this shows out in the pager. So let's do verification of args
early to catch invalid arguments, and then if we receive an error over the bus
(most likely that the name is not activatable), let's print to stdout so it
gets paged. E.g. 'busctl tree org.freedesktop.systemd1 org.freedesktop.systemd2'
gives a nicely usable output.
|
| |\ \
| | |
| | | |
networkd link serialization fix
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We'd start writing an entry line, then another one, then another one,
and then output the rest of the first one, and then some other random
stuff, and the rest of some other lines... Results were ...eh... random.
Let's define a helper to avoid some of the copy&paste madness, and separate
blocks that output a single line with /**********************************/.
This rework doesn't change what data is written, it only tries to fix the
format of the output. The fact that some entries only write data from
link->network, and some from either link->network or link, some stuff only
for dhpc4 leases while some for both dhpc4 and dhcp6, etc, looks rather
suspicious too, but I didn't touch this.
|
| |/ |
|
| |
|
|
| |
Another batch of codespell fixes as reported by Fossies.org
|
| | |
|
| |\
| |
| | |
A few tweaks to docs
|
| | |
| |
| |
| | |
Those are either implemented or obsolete.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
DUID/IAID — #2818, #2890, #3156,
Scope – #6449,
bond options — #10542,
option 119: sd_network_get_domains/sd_network_get_search_domains,
/proc/cmdline parsing – 426c1d385212e11cb,
wait states — #14536.
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Debian Policy encourages to preserve timestamps whenever possible in the
tarballs, thus stable release updates of systemd usually do not bump NEWS file
timestamp. And thus time-epoch remains the same for the lifetime of a release.
It would be better, if each new stable release rebuild of systemd would bump
the time epoch a bit. But at the same time remain
reproducible. SOURCE_DATE_EPOCH is an environmnet variable defined for this
purpose. Thus if available, prefer that, instead of the NEWS file modification
time.
For example, on Debian/Ubuntu under the reproducible builds the
SOURCE_DATE_EPOCH is set to the timestamp from the packaging metadata, thus it
is incremented on every new stable release update, whilst preserving
reproducible builds capability.
Reference: https://reproducible-builds.org/docs/timestamps/
|
| | |
|
| | |
|
| | |
|
| | |
|
