| Commit message (Collapse) | Author | Files | Lines |
|---|
|
Let's make this test independent on what's in the environment.
|
|
For debugging failing tests in combination with mkosi's --debug-shell.
|
|
A fixed kernel finally landed on mirrors, so let's revert the C8S kernel
pin.
This reverts commit a64398b2ca1cdaee291550face0d1ce5f8ea52f6.
|
|
Addresses https://github.com/systemd/systemd/pull/30321#discussion_r1429716344.
|
|
Users can currently pick specific versions of NIC naming, but that
does not guarantee that NIC names won't change after the kernel adds
a new sysfs attribute.
This patch allows for an allow/deny list of sysfs attributes
that could be used when composing the name.
These lists can be supplied as an hwdb entry in the form of
/etc/udev/hwdb.d/50-net-naming-allowlist.hwdb
net:naming:drvirtio_net
ID_NET_NAME_ALLOW=0
ID_NET_NAME_ALLOW_ACPI_INDEX=1
ID_NET_NAME_ALLOW_ADDR_ASSIGN_TYPE=1
ID_NET_NAME_ALLOW_ADDRESS=1
ID_NET_NAME_ALLOW_ARI_ENABLED=1
ID_NET_NAME_ALLOW_DEV_PORT=1
ID_NET_NAME_ALLOW_FUNCTION_ID=1
ID_NET_NAME_ALLOW_IFLINK=1
ID_NET_NAME_ALLOW_INDEX=1
ID_NET_NAME_ALLOW_LABEL=1
ID_NET_NAME_ALLOW_PHYS_PORT_NAME=1
ID_NET_NAME_ALLOW_TYPE=1
|
|
Let's be systematic here, and always hash LE values. It doesn't matter
in our current codebase, but it might one day.
|
|
|
|
Without them only the last expression's return value is honored, causing
unexpected CI fails:
[ 26.006721] testsuite-04.sh[1191]: + for _ in {0..9}
[ 26.007672] testsuite-04.sh[1191]: + setterm --term linux --dump --file /tmp/console.dump
[ 26.008871] testsuite-04.sh[1233]: + SYSTEMD_COLORS=256
[ 26.009606] testsuite-04.sh[1233]: + /usr/lib/systemd/systemd-bsod
[ 26.063296] systemd[1]: session-1.scope: Deactivated successfully.
[ 26.124789] testsuite-04.sh[1191]: + grep -aq 'Press any key to exit' /tmp/console.dump
[ 26.131509] testsuite-04.sh[1191]: + grep -aq 'Root emergency message' /tmp/console.dump
[ 26.137882] testsuite-04.sh[1191]: + grep -aq 'The current boot has failed' /tmp/console.dump
[ 26.141650] testsuite-04.sh[1191]: + return 0
[ 26.144816] testsuite-04.sh[1191]: + grep -aq 'Scan the QR code' /tmp/console.dump
[ 26.153591] testsuite-04.sh[1191]: + at_exit
[ 26.154744] testsuite-04.sh[1191]: + local EC=1
[ 26.155697] testsuite-04.sh[1191]: + [[ 1 -ne 0 ]]
[ 26.156787] testsuite-04.sh[1191]: + [[ -e /tmp/console.dump ]]
[ 26.157799] testsuite-04.sh[1191]: + cat /tmp/console.dump
[ 26.158858] testsuite-04.sh[1244]: The current boot has failed!
[ 26.159858] testsuite-04.sh[1244]: Root emergency message
I'm genuinely impressed that this worked at all.
|
|
|
|
|
|
|
|
Resolves: #30014
|
|
We already refuse the other two cursor-related options (--cursor= and
--after-cursor=) with --since=, so let's do the same with
--cursor-file=.
Closes: #20523
|
|
|
|
|
|
gracefully
Regardless of whether a vc path is passed, the behavior of
systemd-vconsole-setup wasn't ideal when either the passed vc or /dev/tty1 was
in graphics mode.
When a vc in graphics mode was passed, no message was emitted despite the fact
that the font settings couldn't be applied. The previous code might have
assumed that setfont(8) would throw a warning but that's not case.
When no argument was passed, systemd-vconsole-setup was supposed to
automatically select a valid tty, init it and copy the font setting to the
remaining ttys. However if the selected virtual console was in KD_GRAPHICS mode
the initialization of the font failed not only for the selected source vc but
for all of them.
|
|
|
|
This patch enables IFNAME_VALID_ALTERNATIVE for checks guarding the
parsing of RestrictNetworkInterfaces=.
The underlying implementation for this option already supports
altnames.
|
|
|
|
There's a race condition where the EXIT_STATUS= message we send
just before shutting down the VM doesn't arrive on the host,
presumably because the VM is shut down before the kernel has had a
chance to forward the message to the host.
Since there's no obvious way to wait until the message has been
flushed to the host, let's send the message before we execute the
final sync() instead of after executing the final sync(). In my
testing, this seems to either guarantee the message is sent or
introduces sufficient delay that the kernel always has time to flush
its socket buffers to the host.
|
|
|
|
Now that creds are processed even if systemd.firstboot=no is set, we can
use it to disable the root pw prompt *and* the new homectl prompt at the
same time, without breaking the creds stuff.
|
|
This extends what systemd-firstboot does and runs on first boots only
and either processes user records passed in via credentials to create,
or asks the user interactively to create one (only if no regular user
exists yet).
|
|
So far by setting systemd.firstboot=no simply short-cut the whole tool
and made it exit early. This is against what the docs say though: they
just claim the user isn't asked for questions anymore. Let's change
behaviour so that the code actually matches the docs, or more
specifically: if credentials are passed into firstboot, then honour
them, regardless of the kernel cmdline option.
After all, if we get explicit data passed in we should operate on it,
and then leave systemd.firstboot=no just affect the interactivity.
I think this was actually mostly a bug introduced because the credential
stuff was added after the kernel cmdline option, hence this just catches
up with the new addition.
|
|
want rather than complain about them
This makes it easier to take a user record from one host and create an
identical user on another.
|
|
|
|
|
|
This is just paranoia. In all these cases we don't really care about the
trailing NUL byte. But if there's space for it dns_label_unescape() is
going to insert it, and that's a good safety strategy.
This is a follow-up to c29c3adefa8cd859f8cb87d9ad62f3d77b7cd102 which
fixed an actual bug, unlike this commit, which is just paranoia.
|
|
This reverts commit e4a80de119c5ce022396b436690f6321f4bb626b.
|
|
NFT sets must be installed before starting networkd, otherwise some sets may be
installed too late.
Closes #30427
|
|
|
|
In case the host has a 63-byte hostname, we must have enough space for a
NUL terminator as well.
|
|
|
|
|
|
No longer necessary, as the test checks if systemd ran in the initrd.
This reverts commit 0d290cbcd62c5021b485c6f2bf0cef633e77a2b1.
|
|
This test requires systemd in the initrd, which is not the case in
mkinitrd-based initrds (Ubuntu/Debian).
Resolves: #30481
|
|
Follow-up for fe6e0cfa19dd1de4ac599ae207182fd556adcfa7.
|
|
|
|
|
|
With <para><filename>…</filename></para>, we get a separate "paragraph" for
each line, i.e. entries separated by empty lines. This uses up a lot of space
and was only done because docbook makes it hard to insert a newline. In some
other places, <literallayout> was used, but then we cannot indent the source
text (because the whitespace would end up in the final page). We can get the
desired result with <simplelist>.
With <simplelist> the items are indented in roff output, but not in html
output. In some places this looks better then no indentation, and in others it
would probably be better to have no indent. But this is a minor issue and we
cannot control that.
(I didn't convert all spots. There's a bunch of other man pages which have two
lines, e.g. an executable and service file, and it doesn't matter there so
much.)
|
|
|
|
Also, there's no need to set use errno_or_else(), since fscanf() is
documented to set errno on error.
|
|
|
|
|
|
Since [0] delv no longer does that automagically, so we have to that
explicitly with each delv invocation.
Resolves: #30477
[0] https://github.com/isc-projects/bind9/commit/c144fd2871206d209ccdb916f5959a3ceab1d44c
|
|
|
|
Resolves: #30478
|
|
Follow-up to 9fb2a61830.
|
|
Since we nuke the journal multiple times during that, which makes
potential fails undebugable.
|
|
The integration tests use /etc/rc.d/init.d if it exists
or falls back to /etc/init.d,
while the mkosi.build.chroot script dereferenced /etc/init.d.
This produces inconsistent results, as sometimes an image can be made
that has systemd built to expect /etc/init.d but /etc/rc.d/init.d
also exists.
|
