| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
/etc/os-release existence is only enforced in --boot mode,
therefore the term "starting" (which also applies to chroot-like mode)
is substituted with "booting" in this context.
|
|
|
|
|
|
| |
The recommendation to use machinectl login/shell instead of
trying to combine two distinct container instances seemed a
litte bit out of context and is now combined via "rather".
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The existing sd_hwdb_new function always initializes the hwdb from the
first successful hwdb.bin it finds from hwdb_bin_paths. This means there
is currently no way to initialize a hwdb from an explicit path, which
would be useful for systemd-hwdb query.
Add sd_hwdb_new_from_path to allow a sd_hwdb to be initialized from a
custom path outside of hwdb_bin_paths.
|
|\
| |
| | |
Some docs
|
| |
| |
| |
| |
| | |
Fixes #22966. Since there are competing conventions, let's not
change our code, but make the docs match what is implemented.
|
| |
| |
| |
| | |
Fixes #22816.
|
| |
| |
| |
| | |
Fixes #23401
|
| |
| |
| |
| | |
Fixes #21832.
|
| | |
|
| |
| |
| |
| |
| | |
"additional" implies that the unit itself is a symlink, which it is not.
Also "link to the mount unit", not "link to the mount".
|
| | |
|
|/
|
|
|
|
|
| |
This makes the interface more flexible, by allowing the same filtering
for show and status as is done for list-units.
Fixes #23207.
|
| |
|
|\
| |
| | |
systemd-analyze compare-versions
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The interface, output, and exit status convention are all taken directly from
rpmdev-vercmp and dpkg --compare-versions. The implementation is different
though. See test-string-util for a list of known cases where we compare
strings incompatibly.
The idea is that this string comparison function will be declared as "the"
method to use for boot entry ordering in the specification and similar
uses. Thus it's nice to allow users to compare strings.
|
|\ \
| | |
| | | |
boot: EFI mixed mode support
|
| |/ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
All wiki pages that contain a deprecation banner
pointing to systemd.io or manpages are updated to
point to their replacements directly.
Helpful command for identification of available links:
git grep freedesktop.org/wiki | \
sed "s#.*\(https://www.freedesktop.org/wiki[^ $<'\\\")]*\)\(.*\)#\\1#" | \
sort | uniq
|
|/
|
|
|
|
|
|
| |
* Avoid traling slash as most links are defined without.
* Always use https:// protocol and www. subdomain
Allows for easier tree-wide linkvalidation
for our migration to systemd.io.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The methods published by the example have a reply in the signature, but
the code was not sending any, so the client gets stuck waiting for a
response that doesn't arrive. Echo back the input string.
Update the object path to follow what would be the canonical format.
Request a service name on the bus, so that the code can be dropped in a
service and it can be dbus-activatable. It also makes it easier to see
on busctl list.
|
| |
|
| |
|
|
|
|
|
| |
So we're able to tell from the introspection data that the method
doesn't reply.
|
| |
|
|\
| |
| | |
network: clarify relationship between RA flags and DHCPv6 modes
|
| |
| |
| |
| |
| | |
Just setting DHCP=ipv6 is not enough to get DHCPv6 working without RA.
The WithoutRA option must also be changed from its default of "no".
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the documentation, using the term "managed" for both the RA flag and
the DHCPv6 mode is confusing because the mode is referred to as
"solicit" both in the official DHCPv6 documentation (see RFC 8415) and
in the WithoutRA option.
Furthermore, calling the other RA flag "other information" or "other
address configuration" is confusing because its official name is simply
"other configuration" (see RFC 4861 and RFC 5175) and it isn't used to
assign IP addresses.
Rewrite the documentation for DHCPv6Client and WithoutRA to make it
clear that getting the "managed" RA flag triggers the same kind of DHCP
request as WithoutRA=solicit, whereas getting the "other configuration"
RA flag triggers the same kind of DHCP request as
WithoutRA=information-request.
|
|\ \
| |/
|/| |
Logind man and rules
|
| | |
|
| |
| |
| |
| | |
gdbus is an external program, so it makes sense to recommend busctl.
|
| | |
|
| |
| |
| |
| |
| | |
It's useful for installation scripts and suchlike.
Raised in https://bugzilla.redhat.com/show_bug.cgi?id=2079784#c9.
|
| | |
|
|/
|
|
|
|
| |
This makes it easier to only test a subset of tests without having
to specify them all on the command line:
meson test -C build --suite headers
|
|
|
|
| |
Closes #23262.
|
|
|
|
|
|
|
|
|
| |
roothash=/usrhash= on the kernel cmdline
It doesn't really care about the hash value passed (which is processed
by systemd-veritysetup-generator), but it does care about the fact that
it is set (and mounts the DM nodes /dev/mapper/usr + /dev/mapper/root in
that case).
|
|
|
|
|
|
|
|
|
| |
I don't know why this didn't occur to me earlier, but of course, it
*has* to be this data.
(This replaces some German prose about Berlin, that i guess only very
few people will get. With the new blob I think we have a much broader
chance of delivering smiles.)
|
|
|
|
|
|
| |
Let's merge the footnote with the overall explanation of where systemd
parses its options from and reword the section a bit to hopefully make
things a bit more clear.
|
|\
| |
| | |
import system credentials from sd-stub + qemu fw_cfg + kernel cmdline explicitly in PID 1
|
| | |
|
| | |
|
|\ \
| |/
|/| |
More cross-references in bootctl/systemctl man pages
|
| | |
|
|\|
| |
| | |
Extend the documentation for oomd a bit
|
| |
| |
| |
| | |
OOMPolicy remains valid, but let's push users for the userspace solution.
|