| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
core: follow-ups for objective serialization
|
| |
| |
| |
| | |
Addresses https://github.com/systemd/systemd/pull/32320#discussion_r1569192295
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Follow-up for 8c15bf36e117054cf54b4f0cca59615b7531a545
I just realized that we should not serialize the number
of internal enum, as that's subject to changes and such
changes would be hard to notice. Let's serialize strings
properly instead.
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
systemctl: show invocation ID in unit status output
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I think we should put more emphasis on the invocation ID as a handle for
a specific runtime cycle of a unit. Let's start with actually showing it
to users.
See: #16035
|
|\ \ \
| |_|/
|/| | |
mkosi: undefine FORTIFY_SOURCE instead of setting it zero
|
| | |
| | |
| | |
| | |
| | | |
Newer gcc complains if FORTIFY_SOURCE=0 is set so just undefine it
instead.
|
|/ / |
|
|\ \
| | |
| | | |
mkosi: Various improvements
|
| | |
| | |
| | |
| | |
| | |
| | | |
When we're building debuginfo packages, the original binaries and
libraries are stripped so make sure we install the debuginfo
packages to make sure debugging in the container/VM still works.
|
| | |
| | |
| | |
| | |
| | |
| | | |
This doesn't actually work because the opensuse spec doesn't allow
adding extra build flags, but I'm working on fixing that, so let's
already set things up for later.
|
| | |
| | |
| | |
| | | |
Otherwise we get warnings from gcc.
|
| | |
| | |
| | |
| | |
| | | |
Let's install everything we can to get more coverage and make sure
all build outputs are available in mkosi containers or VMs.
|
| | |
| | |
| | |
| | | |
This is just a Provides for systemd-udev.
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
man: pam_system_loadkey additions and fixes
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is required because pam_sm_open_session [1] only looks at
gkr_system_authtok, which is copied from the kernel keyring in
pam_sm_authenticate.
[1] https://gitlab.gnome.org/GNOME/gnome-keyring/-/blob/46.1/pam/gkr-pam-module.c?ref_type=tags
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
As a follow-up in the style of:
873be895ed ("udev: add USB revision in ID_PATH")
this patch adds a second symlink for media controllers, this time
including the USB revision.
This means that in addition to persistent symlinks like:
pci-0000:04:00.3-usb-0:1:1.0-media-controller -> ../../media0
We now also get:
pci-0000:04:00.3-usbv2-0:1:1.0-media-controller -> ../../media0
...which helps distinguish media devices plugged into different USB root
hubs provided by the same PCI card, at least as long as they are for
different USB revisions.
Fixes: 04f19d6735 ("udev: Add /dev/media/by-path symlinks for media controllers")
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Sponsored work on homed
|
|\ \ \ \
| | | | |
| | | | | |
docs: use absolute links for our pages
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Since 56b2970 has proven to be a no-go for us, as it breaks existing
links, let's embrace the trailing slash and use absolute links
everywhere for our pages. This way we'll get around browser cleverly
appending the relative link to the current location (since it ends with
a slash), and given our docs/ layout is flat it's not much of a hassle
either.
Converted using this beauty:
$ sed -ri 's/(\[.+\]\()([A-Z_]+\))/\1\/\2/g' *.md
Resolves: #32088 (again) and #32310
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This breaks existing links with a trailing slash, so it's a no-go.
This reverts commit d1a7e030c5daa4a09ee93b8af6b28ecaac5d34d0.
|
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Let's create the .ssh dir with the right perms first.
Suggested by @gcb.
Fixes: #28172
|
| |_|/
|/| | |
|
| | |
| | |
| | |
| | | |
Follow-ups for 089bef66316e5bdc91b9984148e5a6455449c1da.
|
| | |
| | |
| | |
| | | |
Follow-up for 33ff155957327f51dde740a7a75f19122bff1ebc.
|
|\ \ \
| | | |
| | | | |
blockdev-util: fix detection of partscan
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The 'capability' sysattr was deprecated by
https://github.com/torvalds/linux/commit/e81cd5a983bb35dabd38ee472cf3fea1c63e0f23 (v6.3).
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | | |
vmspawn: generate predicatable TAP device names and MAC addresses
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
shared/netif-util
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | | |
Fixes #31920.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Clarify that `-p, --priority=` always treats its option as a priority range, even when given
a single log level per the full man page description.
Co-authored-by: Mike Yuan <me@yhndnzj.com>
|
|\ \ \ \
| | | | |
| | | | | |
sd-ndisc: disable one more timer event source
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Otherwise, even if we have already received RA, timeout callback will be
called. Currently, networkd mostly does nothing on timeout, hence should
not change any effective behavior.
Follow-up for e7cb80474d4e580f7cc7c8645e1412e4a59f7588.
|
|\ \ \ \ \
| |_|_|_|/
|/| | | | |
journal-gatewayd: use skip_leading_chars
|
| | | | |
| | | | |
| | | | |
| | | | | |
Prompted by c5d675472588815dedf67af8c36da0fac398fb3e
|
| | | | | |
|