| Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
These are not for failed tasks, and provide almost no information.
|
|
|
|
|
|
This will be used to save the list of drop-in files for each partition
|
|
Devicetree firmware contains an "aliases" node, containing various
aliases for devices described by the firmware. For ethernet devices,
these are named "ethernet0", "ethernet1", etc. They provide a convenient
means of numbering ethernet devices, especially on systems with no other
stable number other than the address. In particular, U-Boot already uses
these aliases to name its ethernet devices.
Previously, there have been attempts (such as [1]) to add support for
these aliases to Linux. However, these patches have been rejected
because it is the maintainers' view that naming policy be left to
userspace. Well, systemd is userspace, so here we are.
In terms of implementation, apparently there can be multiple device
trees at once. I have decided to dodge this problem for now, and just
use /proc/device-tree. If it is desired to support multiple device trees
later, then the scheme can be modified to include the device tree's
index. For example, /sys/firmware/devicetree/base2/aliases/ethernet3
might be named enb2d3.
For the moment we only support "ethernetX" aliases. Future patches might
want to also handle "canX" and "wifiX".
It is common on boards with only one ethernet device to use an alias of
just "ethernet". In this case, the index is an implicit 0. In case the
author of the firmware made a mistake, we check to ensure that aliases
of "ethernet" and "ethernet0" do not both exist.
[1] https://patchwork.kernel.org/project/linux-arm-kernel/patch/1399390594-1409-1-git-send-email-boris.brezillon@free-electrons.com/
Closes: #17625
|
|
Fixes an issue introduced by 9e79123884a36ce095b98d1c0fe247dddf02dbec.
|
|
Fixes an issue introduced by b3d06b9226db96fddb6bb45a4708e2e8d413d91d.
|
|
If a system has many devices, then the receiver buffer may be filled up.
Hopefully fixes https://bugzilla.redhat.com/show_bug.cgi?id=2095750
|
|
Otherwise, the receiver refuses the devices. See device_verify().
|
|
Signed-off-by: wineway <wangyuweihx@gmail.com>
|
|
Otherwise it can't access the newly create LXC container:
```
autopkgtest-virt-lxc: DBG: wait_booted: detecting init system failed, retrying...
autopkgtest-virt-lxc: DBG: stderr: lxc-attach: autopkgtest-lxc-trjmpu: tools/lxc_attach.c: main: 302 You lack access to /home/semaphore/.local/share/lxc
```
|
|
|
|
Share code between firstboot and sysusers
|
|
since it's no longer supported/necessary.
See: https://github.com/lxc/lxc/commit/58520263041b6864cadad96278848f9b8ce78ee9
|
|
as we now use our own custom script for it.
|
|
Also, address https://github.com/systemd/systemd/pull/24252#issuecomment-1208747320
by using a pre-defined e-mail address stored in the GH Action secrets.
|
|
resolvconf
ifname_resolvconf_mangle is supposed to remove protocol suffixes like .dhcp
from interface names. But this removed also valid parts of the ifname like
VLAN IDs, e.g. enp2s0u4.72.dhcp -> enp2s0u4 instead of enp2s0u4.72
After this change, everything behind the last dot is removed instead of the first.
|
|
|
|
Closes #23557.
|
|
Fixes https://github.com/systemd/systemd/issues/23785#issuecomment-1210030100.
|
|
|
|
Fixes: #24241
|
|
Currently translated at 100.0% (189 of 189 strings)
Co-authored-by: Balázs Meskó <meskobalazs@mailbox.org>
Translate-URL: https://translate.fedoraproject.org/projects/systemd/master/hu/
Translation: systemd/main
|
|
Follow-ups for 60f97fee2d2f948c8e8963ea8ff767008cb93cae and
32963344736004e01ff4dd9dca079faabaf58cf2.
|
|
While this provides some marginal speedup, the disadvantage is
that files are never removed when doing cached builds, which can
sometimes lead to hard to debug issues. So let's not do this by
default.
|
|
Better than creating a mess of output files in the root directory.
|
|
|
|
They're floppy disk flux readers and writers used in digital
preservation and can be broadly considered to be "analyzers" of magnetic
fluxes.
This will have the intended side-effect of giving access to the device
to users at the console, obsoleting:
https://github.com/keirf/greaseweazle/blob/master/scripts/49-greaseweazle.rules
|
|
Allow users at the console access to the USB serial interface for USB
analysers.
See 9e2dbfef479060ed850ccdd9cd82d3f0cda2b5c0
|
|
|
|
|
|
|
|
And check module availability in each tests.
This also sorts qdisc tests.
|
|
|
|
The names seem to be used in AWS.
This also merges test_tun() and test_tap().
|
|
|
|
|
|
|
|
|
|
|
|
Preparation for next commit.
|
|
|
|
This modifies some sd_bus calls to equivalent bus calls.
|
|
This tweaks user creation logic to properly take into consideration
an explicitly requested GID.
It fixes a bug where the creation flow would mistakenly fall back
to use the username instead, resulting in wrong lookups in case of
users and groups using the same name.
|
|
This relaxes the availability check when creating a group, if an
explicit GID has been requested.
It avoids mixing up users and groups entries with valid and unique
UIDs/GIDs, but each having the same ID number.
|
|
|
|
|
|
Hence, when sd_device_enumerator_add_match_property() called with NULL
for value, then the filter always unmatches with the device.
|
|
Previously, if sd_device_enumerator_add_match_sysattr() is called for
the same sysattr with different values, then no device passed the filter.
Now, the accepted values (or patterns) are stored in strv, and if the
sysattr value of a device matches with the strv, then the device passes
the filter.
|
