| Commit message (Collapse) | Author | Files | Lines |
|
That's just a follow-up to https://github.com/systemd/systemd/pull/22179
|
|
Fixes #22178.
|
|
Otherwise, the generated xml files are not reproducible.
|
|
This should make sure the stub elf binary is reproducible.
Fixes: #22157
|
|
Suggested by shell check SC2129.
|
|
|
|
On failure, the function previously sometimes logs in debug level, but
sometimes does not. Let's always log the error cause.
|
|
Prompted by https://github.com/systemd/systemd/pull/22093#issuecomment-1016254914.
|
|
Fixes the second issue in #21819.
|
|
Jan 17 12:34:59 myguest1 (sd-sysext)[486]: Device '/var/lib/extensions/myext.raw' is loopback block device with partition scanning turned off, please turn it on.
Fixes https://github.com/systemd/systemd/issues/22146
|
|
|
|
|
|
|
|
|
|
configuring it
|
|
This adds SR-IOVVirtualFunctions= setting in [Link] section.
|
|
The same section is already supported by .network files. But such
low-level inteerface setting should be done by udevd, instead of
networkd. Let's also support the same semantics by .link files.
Prompted by https://github.com/systemd/systemd/issues/20474#issuecomment-901901360.
|
|
|
|
And move it and relevant functions to conf-parser.[ch].
|
|
|
|
|
|
|
|
have ID in os-release
We can't match an extension if we don't at least have an ID,
so refuse to continue
|
|
os-release
A rolling distro won't set VERSION_ID or SYSEXT_LEVEL in os-release,
which means we skip validation of ExtensionImages.
Validate even with just an ID, the lower level helper already
recognizes and accepts this use case.
Fixes https://github.com/systemd/systemd/issues/22146
|
|
|
|
Remove the parameter 'only_auto' from the function
boot_entries_augment_from_loader() because each caller set it always to
true.
Signed-off-by: Goffredo Baroncelli <kreijack@inwind.it>
|
|
When bootctl lists the boot entries, considers also the ones
returned by systemd-boot (via the efi LoaderEntries variable),
created at boot time.
Unfortunately this list may became incorrect if (e.g.) the user remove a
kernel package.
This patch changes this behaviour, so bootctl ignores some the
boot entries returned by systemd-boot.
In any case, bootctl still considers the 'auto-xxx' boot entries
listed below:
Boot entrie name Title
----------------------------- ------------------------------
auto-osx macOS boot loader
auto-windows Windows Boot Manager
auto-efi-shell EFI Shell
auto-efi-default EFI Default Loader
auto-reboot-to-firmware-setup Reboot Into Firmware Interface
The other entries that systemd-boot synthetizes (e.g. the ones loaded from
/efi/loader/entries/<uuid>) can be synthetized by bootctl too, so no
information is lost.
Signed-off-by: Goffredo Baroncelli <kreijack@inwind.it>
|
|
|
|
The device path should not contain multiple hard drive nodes in it,
so looking at them all should not be needed.
If some crazy firmware/driver were to make nested GPT drives
available like that, we should be only looking at the last partition
and its containing GPT drive anyway.
|
|
Some firmware creates partition device paths without a messaging
device path node, making the search for the xboot loader partition
fail.
Fixes: #17756
|
|
Looks like https://github.com/mesonbuild/meson/issues/957 was
reintroduced in meson-0.57.0 (and looking and https://mesonbuild.com/Release-notes-for-0-57-0.html
I'm not sure whether it was intentional or not) so run_command can no
longer be used to get around
https://github.com/mesonbuild/meson/issues/3589. Let's just force
ctags to always use absolute paths to fix it once and for all.
|
|
The function is called in recursion, and cgroup.procs in some subcgroups
may not be read.
Fixes #22089.
|
|
https://github.com/systemd/mkosi/pull/886
|
|
|
|
Follow-up for 12727c2bc2859995cbd561ffc3d9a4d571202254.
Addresses https://github.com/systemd/systemd/pull/22125#discussion_r786358474.
Fixes CID#1469023.
|
|
Link in systemd.io and systemd-sysext
Fixes #22146
|
|
Previously, the holes we punched earlier would get removed when
copying the file. Let's enable the new COPY_HOLES flag to make
sure this doesn't happen.
In my test, this drops a 800MB btrfs journal (without compression)
to 720 MB.
Fixes #22087
|
|
Fixes RHBZ#2016630.
|
|
The whole point of systemd-stdio-bridge is to be executed on "foreign" systems
where the path might be different, so we use $PATH to find the binary everywhere.
|
|
|
|
|
|
I hope that this fixes the comment
https://github.com/systemd/systemd/pull/22141#issuecomment-1013960371
> As someone who doesn't know what this prog does
The listing in the man page is sorted according to logical
use: all the options setting the address are now together.
|
|
|
|
Bumps [github/codeql-action](https://github.com/github/codeql-action) from 1.0.26 to 1.0.27.
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](https://github.com/github/codeql-action/compare/5f532563584d71fdef14ee64d17bafb34f751ce5...cd783c8a29bdcf5a5c79c5137889e24651fa626c)
---
updated-dependencies:
- dependency-name: github/codeql-action
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
|
|
|
|
Lintian is opinionated about this and we get nagged
|
|
By analogy with https://github.com/systemd/systemd/pull/22138, to get
the static analyzers to analyze that part of code that package should
be installed there as well.
|
|
Follow-up for 0bc488c99ab2ed3464237607e381f4d72cd321d5.
Also sort dependency properties to make them match the definition of
`enum UnitDependency` in basic/unit-def.h.
Fixes #22133.
|
|
Fixes CID#1469009.
|