summaryrefslogtreecommitdiffstats
path: root/mkosi.postinst (unfollow)
Commit message (Collapse)AuthorFilesLines
2022-08-12hwdb: Apply existing accel orientation quirk to all ChromebooksAlper Nebi Yasak1-18/+4
The cros-ec-accel and cros-ec-accel-legacy kernel modules internally correct for the board-specific accelerometer mounting orientations. Their sensor outputs are in a standard reference frame consistent across different boards, so the orientation matrix already added for a number of devices should apply to every device using cros-ec accelerometers. The different matrix for the 'Nocturne' board seems to be an error. Replace the existing hwdb rules for select Chromebooks with generic rules that apply to all Chromebooks.
2022-08-12network: replace usage of sd_bus_call_method_async() to ↵williamsumendap4-8/+12
bus_call_method_async() (#24290)
2022-08-12tpm2-util: rename tpmKey → primaryLennart Poettering1-4/+4
Let's use the nomenclature from the spec. "tpmKey" is just too genric.
2022-08-12tpm2-util: lower indentation level a tiny bitLennart Poettering1-19/+15
2022-08-12cryptenroll: fix memory leakLennart Poettering1-0/+1
2022-08-12update TODOLennart Poettering1-0/+6
2022-08-12udev: use sd_device_new_from_path() and _new_child()Yu Watanabe1-5/+9
Follow-up for 65c2ad985a8debdf6d7d11fee5b466f280260f4b.
2022-08-12test: add more tests for sd_device_new_from_path()Yu Watanabe1-0/+49
2022-08-12sd-device: allow to create sd-device object through a symlink outside of /sysYu Watanabe1-8/+18
For example, /proc/device-tree is a symlink to /sys/firmware/devicetree/base, and the kernel documentation says the symlink should be used by userspace app. See, https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw. Hence, it is useful to make `sd_device_new_from_path()` support such symlink.
2022-08-12udev: set description for device monitorYu Watanabe1-0/+4
2022-08-12test: use sd_device_monitor_set_description()Yu Watanabe1-14/+14
2022-08-12sd-device-monitor: logs description for device monitorYu Watanabe1-43/+52
2022-08-12sd-device-monitor: introduce sd_device_monitor_{set,get}_description()Yu Watanabe3-1/+30
2022-08-12sd-device-enumerator: drop noisy log messagesYu Watanabe1-4/+0
These are not for failed tasks, and provide almost no information.
2022-08-12repart: add test for drop-in filesRichard Phibel1-0/+50
2022-08-12repart: Add support for drop-in overridesRichard Phibel1-16/+45
2022-08-12config-parser: Add list of drop-in files as return argument of config_parse_manyRichard Phibel8-7/+21
This will be used to save the list of drop-in files for each partition
2022-08-12udev: net_id: Use devicetree aliases when availableSean Anderson4-2/+134
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
2022-08-11sd-device-monitor: actually refuse to send invalid devicesYu Watanabe1-2/+2
Fixes an issue introduced by 9e79123884a36ce095b98d1c0fe247dddf02dbec.
2022-08-11sd-device-monitor: fix inversed conditionYu Watanabe1-1/+1
Fixes an issue introduced by b3d06b9226db96fddb6bb45a4708e2e8d413d91d.
2022-08-11test: do not fill up receiver bufferYu Watanabe1-10/+16
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
2022-08-11test: add fake action and seqnumYu Watanabe1-0/+12
Otherwise, the receiver refuses the devices. See device_verify().
2022-08-11core/cgroup: CPUWeight/CPUShares support idle inputwineway14-17/+99
Signed-off-by: wineway <wangyuweihx@gmail.com>
2022-08-11semaphore: run autopkgtest with sudoFrantisek Sumsal1-4/+4
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 ```
2022-08-11docs: mention qemu fw_cfg size limitationLudwig Nussel1-1/+2
2022-08-11creds: refactor reading user passwordLudwig Nussel4-37/+44
Share code between firstboot and sysusers
2022-08-11tests: systemd-cryptenroll: unlock volume with keyfileJan B1-0/+3
2022-08-11docs: adding "--unlock-key-file" to systemd-cryptenrollJan B1-0/+9
2022-08-11semaphore: drop the --keyserver= parameter for the download templateFrantisek Sumsal1-8/+1
since it's no longer supported/necessary. See: https://github.com/lxc/lxc/commit/58520263041b6864cadad96278848f9b8ce78ee9
2022-08-11ci: lint the Coverity scriptFrantisek Sumsal1-2/+1
as we now use our own custom script for it.
2022-08-11ci: simplify the Coverity script a bitFrantisek Sumsal3-263/+44
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.
2022-08-11resolvctl: only remove protocol after last dot when mangling ifname for ↵exploide1-1/+1
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.
2022-08-11oomd: notify via dbus what have been killedOleg Solovyov3-3/+57
2022-08-11core/scope: Add oom-kill status for scope units (#24269)gtwang012-0/+30
Closes #23557.
2022-08-10cryptenroll: adding the option to use a keyfile to unlock the deviceJan B1-0/+43
2022-08-10oom: drop invalid %m in the log messageYu Watanabe1-1/+1
Fixes https://github.com/systemd/systemd/issues/23785#issuecomment-1210030100.
2022-08-10tree-wide: fix typoYu Watanabe5-5/+5
2022-08-10meson: Test correct efi linker for supported argsJan Janssen1-5/+13
Fixes: #24241
2022-08-09po: Translated using Weblate (Hungarian)Balázs Meskó1-225/+139
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
2022-08-09meson: use 'not in'Yu Watanabe1-1/+1
Follow-ups for 60f97fee2d2f948c8e8963ea8ff767008cb93cae and 32963344736004e01ff4dd9dca079faabaf58cf2.
2022-08-09mkosi: Don't use InstallDirectory by defaultDaan De Meyer1-1/+0
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.
2022-08-09mkosi: Use mkosi.output/ as output directory by defaultDaan De Meyer1-0/+1
Better than creating a mess of output files in the root directory.
2022-08-09sleep: support multiple battery instead of only BAT0Sonali Srivastava3-116/+363
2022-08-09hwdb: Add Greaseweazle "drives" to the list of analyzersBastien Nocera1-0/+7
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
2022-08-09hwdb: Allow users access to USB serial for analysersBastien Nocera1-0/+1
Allow users at the console access to the USB serial interface for USB analysers. See 9e2dbfef479060ed850ccdd9cd82d3f0cda2b5c0
2022-08-09hwdb: analyzers: Clarify the type of devices we want listedBastien Nocera1-2/+3
2022-08-09NEWS: add entries for v252Zbigniew Jędrzejewski-Szmek1-1/+148
2022-08-09test-network: split out qdisc and wait-online tests from NetworkdNetworkTestsYu Watanabe1-0/+16
2022-08-09test-network: split test_qdisc() and test_qdisc2()Yu Watanabe16-294/+391
And check module availability in each tests. This also sorts qdisc tests.
2022-08-09test-network: check qdisc feature by module existenceYu Watanabe1-50/+5