[systemd-devel] systemd prerelease 258-rc4

A new systemd ☠️ pre-release ☠️ has just been tagged. Please download the tarball here: https://github.com/systemd/systemd/archive/v258-rc4.tar.gz NOTE: This is ☠️ pre-release ☠️ software. Do not run this on production systems, but please test this and report any issues you find to GitHu

Re: [systemd-devel] systemd-logind fails to start if /etc is read-only

On Mi, 20.08.25 14:50, Demi Marie Obenour (demioben...@gmail.com) wrote: > >> On a system where /etc is read-only, systemd-logind fails to start. > >> I have tried making / a writable overlayfs without any success so > >> far. The code is at https://github.com/DemiMarie/spectrum (branch > >> b4/s

Re: [systemd-devel] systemd-logind fails to start if /etc is read-only

On 8/18/25 05:02, Lennart Poettering wrote: > On Sa, 16.08.25 22:47, Demi Marie Obenour (demioben...@gmail.com) wrote: > >> On a system where /etc is read-only, systemd-logind fails to start. >> I have tried making / a writable overlayfs without any success so >> far. The code is at https://githu

[systemd-devel] systemd prerelease 258-rc3

A new systemd ☠️ pre-release ☠️ has just been tagged. Please download the tarball here: https://github.com/systemd/systemd/archive/v258-rc3.tar.gz NOTE: This is ☠️ pre-release ☠️ software. Do not run this on production systems, but please test this and report any issues you find to GitHu

Re: [systemd-devel] systemd-logind fails to start if /etc is read-only

On Sa, 16.08.25 22:47, Demi Marie Obenour (demioben...@gmail.com) wrote: > On a system where /etc is read-only, systemd-logind fails to start. > I have tried making / a writable overlayfs without any success so > far. The code is at https://github.com/DemiMarie/spectrum (branch > b4/systemd) and

[systemd-devel] systemd-logind fails to start if /etc is read-only

On a system where /etc is read-only, systemd-logind fails to start. I have tried making / a writable overlayfs without any success so far. The code is at https://github.com/DemiMarie/spectrum (branch b4/systemd) and the problem can be reproduced by running nix-shell --pure --run 'make run' in host

[systemd-devel] systemd prerelease 258-rc2

A new systemd ☠️ pre-release ☠️ has just been tagged. Please download the tarball here: https://github.com/systemd/systemd/archive/v258-rc2.tar.gz NOTE: This is ☠️ pre-release ☠️ software. Do not run this on production systems, but please test this and report any issues you find to GitHu

[systemd-devel] systemd prerelease 258-rc1

A new systemd ☠️ pre-release ☠️ has just been tagged. Please download the tarball here: https://github.com/systemd/systemd/archive/v258-rc1.tar.gz NOTE: This is ☠️ pre-release ☠️ software. Do not run this on production systems, but please test this and report any issues you find to GitHu

Re: [systemd-devel] systemd-tty-ask-password-agent, new warning

> Does it also move "systemd-ask-password" to -extra? Yes, systemd-ask-password is/was also part of systemd-extra-utils, along with several other files. > For a distro that targets embedded devices (i.e. where services aren't going > to use > systemd's ask-password facility because nobody will

Re: [systemd-devel] systemd-tty-ask-password-agent, new warning

Does it also move "systemd-ask-password" to -extra? For a distro that targets embedded devices (i.e. where services aren't going to use systemd's ask-password facility because nobody will ever be around to manually respond to such prompts for services *anyway*), I think it would be fine to leave o

Re: [systemd-devel] systemd-tty-ask-password-agent, new warning

>> Any comment on my other question: is systemd-tty-ask-password an optional >> component? > > It is optional. You can skip it with --no-ask-password. If you did not, > it is assumed you wanted password agent and the warning is correct. It > is just a message, systemctl does not fail if it could

Re: [systemd-devel] systemd-tty-ask-password-agent, new warning

08.07.2025 22:38, James Muir (jamesmui) wrote: Is systemd-tty-ask-password still an optional component? Is this new behaviour (where systemd-tty-ask-password is repeatedly executed) intentional? It is not new behavior. systemctl did it for as long as I remember. Okay. But the display of th

Re: [systemd-devel] systemd-tty-ask-password-agent, new warning

> Is systemd-tty-ask-password real or a typo? Sorry, I meant systemd-tty-ask-password-agent. I dropped “-agent” by mistake (at least I had it right in the subject). > Also if you're already in a root session, why is it asking for more > authentication? I suspect some services need to query for

Re: [systemd-devel] systemd-tty-ask-password-agent, new warning

On Tue, 8 Jul 2025 18:02:56 + "James Muir (jamesmui)" wrote: > >> Is systemd-tty-ask-password still an optional component? > >> > >> Is this new behaviour (where systemd-tty-ask-password is > >> repeatedly executed) intentional? > > > > It is not new behavior. systemctl did it for as long as

Re: [systemd-devel] systemd-tty-ask-password-agent, new warning

>>> Is systemd-tty-ask-password still an optional component? >>> >>> Is this new behaviour (where systemd-tty-ask-password is repeatedly >>> executed) intentional? >> >> It is not new behavior. systemctl did it for as long as I remember. > > Okay. But the display of the warning is new behaviour.

Re: [systemd-devel] systemd-tty-ask-password-agent, new warning

>> Is systemd-tty-ask-password still an optional component? >> >> Is this new behaviour (where systemd-tty-ask-password is repeatedly >> executed) intentional? > > It is not new behavior. systemctl did it for as long as I remember. Okay. But the display of the warning is new behaviour. Was the

Re: [systemd-devel] systemd-tty-ask-password-agent, new warning

08.07.2025 19:57, James Muir (jamesmui) wrote: I upgraded from v255.4 to v255.13 (these are tags from https://github.com/systemd/systemd-stable), I now see the following warning when I manually start a service: root@vbox:~/tmp# systemctl start systemd-journald Failed to execute /usr/bin/system

[systemd-devel] systemd-tty-ask-password-agent, new warning

I upgraded from v255.4 to v255.13 (these are tags from https://github.com/systemd/systemd-stable), I now see the following warning when I manually start a service: root@vbox:~/tmp# systemctl start systemd-journald Failed to execute /usr/bin/systemd-tty-ask-password-agent: No such file or direct

Re: [systemd-devel] systemd v257.5: Issue with systemd-sysupdate, no targets and components listed

lf > of Simao Gomes Viana | Toowoxx IT GmbH > Sent: Monday, June 30, 2025 15:15 > To: systemd-devel@lists.freedesktop.org > Subject: [systemd-devel] systemd v257.5: Issue with systemd-sysupdate, no > targets and components listed > > Hi, > > I have been struggling with an issue

Re: [systemd-devel] systemd link file rename eth0 do not take effect

_ From: Andrei Borzenkov Sent: Tuesday, June 17, 2025 10:47 PM To: Mantas Mikulėnas ; He, Guocai (CN) ; systemd-devel@lists.freedesktop.org Subject: Re: [systemd-devel] systemd link file rename eth0 do not take effect CAUTION: This email comes from a non Wind River email account! Do not c

Re: [systemd-devel] systemd link file rename eth0 do not take effect

17.06.2025 09:20, Mantas Mikulėnas wrote: On another note, even though NamePolicy doesn't provide any names in your case, you should still clear it in general: [Link] NamePolicy= Name=mycustometh Why? NamePolicy is empty by default and only one .link file is applied. There should be noth

Re: [systemd-devel] systemd link file rename eth0 do not take effect

On Tue, Jun 17, 2025, at 02:20, Mantas Mikulėnas wrote: > nfsroot= causes the interface to be brought up very early, before udev > starts, and before it has a chance to apply its rules and .link files. > > > > Before kernel 6.2, it was not possible to rename interfaces that were already > "up"

Re: [systemd-devel] systemd link file rename eth0 do not take effect

nfsroot= causes the interface to be brought up very early, before udev starts, and before it has a chance to apply its rules and .link files. Before kernel 6.2, it was not possible to rename interfaces that were already "up" (see linux commit bd039b5ea2a91). On another note, even though Nam

[systemd-devel] systemd link file rename eth0 do not take effect

Hi, I want to create a link file and want to match the mac to rename eth0 to mycustometh but fail. seems that the link file is not applied? The fllowing is my step and some logs: #1 etho mac udevadm info /sys/class/net/eth0 E: ID_NET_NAME_MAC=enxa4bf016bfaf5 #2 link file root@intel-x86-64:~#

[systemd-devel] systemd link file rename eth0 do not take effect

Hi, I want to create a link file and want to match the mac to rename eth0 to mycustometh but fail. seems that the link file is not applied? The fllowing is my step and some logs: ##1 etho mac udevadm info /sys/class/net/eth0    E: ID_NET_NAME_MAC=enxa4bf016bfaf5 ##2 link file root@intel-x86-6

Re: [systemd-devel] systemd-pcrlock silently ignores user requested PCRs downgrading security

On Fr, 09.05.25 15:58, Andrei Borzenkov (arvidj...@gmail.com) wrote: > > > The current behavior looks more like the case for auto-detection - check > > > what existing measurements are covered by predictions and incorporate > > > those > > > PCRs. I.e. when no explicit --pcr= option is present. >

Re: [systemd-devel] systemd-pcrlock silently ignores user requested PCRs downgrading security

On 2025-05-09 13:03, Lennart Poettering wrote: On Fr, 09.05.25 15:58, Andrei Borzenkov (arvidj...@gmail.com) wrote: > If you want explicit config use the simpler PCR protections > systemd-cryptsetup gives you, and avoid pcrlock. I obviously want to use pcrlock to have alternatives (like being

Re: [systemd-devel] systemd-pcrlock silently ignores user requested PCRs downgrading security

On Fr, 09.05.25 15:36, Andrei Borzenkov (arvidj...@gmail.com) wrote: 61;8001;1c > I know that it is documented, but that leads to rather bad user experience. > User requests specific protection via --pcr= option, pcrlock decides to skip > (some of) them and binds unlocking to just a subset of PCRs

Re: [systemd-devel] systemd-pcrlock silently ignores user requested PCRs downgrading security

On 2025-05-09 12:36, Andrei Borzenkov wrote: I know that it is documented, but that leads to rather bad user experience. User requests specific protection via --pcr= option, pcrlock decides to skip (some of) them and binds unlocking to just a subset of PCRs pretending that the operation succeeded

Re: [systemd-devel] systemd-pcrlock silently ignores user requested PCRs downgrading security

09.05.2025 15:45, Lennart Poettering wrote: On Fr, 09.05.25 15:36, Andrei Borzenkov (arvidj...@gmail.com) wrote: 61;8001;1c I know that it is documented, but that leads to rather bad user experience. User requests specific protection via --pcr= option, pcrlock decides to skip (some of) them and

[systemd-devel] systemd-pcrlock silently ignores user requested PCRs downgrading security

I know that it is documented, but that leads to rather bad user experience. User requests specific protection via --pcr= option, pcrlock decides to skip (some of) them and binds unlocking to just a subset of PCRs pretending that the operation succeeded. At this point user believes that the syst

Re: [systemd-devel] Systemd failed to create /init.scope under systemd-nspawn

It seems very strange. systemd-nspawn should have nothing to do with whether it is running in vm or what is the host of the vm. Try to see what systemd-detect-virt see's in each case anyway. For debugging, you can enter the nspawn container --boot and see if cgroup fs is mounted the same in al

Re: [systemd-devel] Systemd failed to create /init.scope under systemd-nspawn

On Do, 08.05.25 00:09, An Liu (sourceo...@gmail.com) wrote: > Hi, > I'm playing systemd-nspawn, and something interesting happens. > Try 1: host CentOS 8 Stream, systemd-nspawn to Debian Trixie > everything goes well. > > Try 2: host CentOS 8 Stream , kvm guest CentOS 8 Stream > a: in guest system

[systemd-devel] Systemd failed to create /init.scope under systemd-nspawn

Hi, I'm playing systemd-nspawn, and something interesting happens. Try 1: host CentOS 8 Stream, systemd-nspawn to Debian Trixie everything goes well. Try 2: host CentOS 8 Stream , kvm guest CentOS 8 Stream a: in guest systemd-nspawn to Debian Trixie , nspawn is OK to start without —boot b: in gues

[systemd-devel] systemd-timedated support for NTP SRV records

The current docs for systemd-timedated indicates the configuration only supports explicit time server listings. Am I missing something in regards to support for DNS SRV records for NTP service? AKA: _ntp._udp. If this is not currently supported, where should I submit a feature request for t

Re: [systemd-devel] systemd-timedated support for NTP SRV records

On 4/14/25 11:11 AM, Kenneth Porter wrote: Why wouldn't you use DHCP to assign a datacenter server's address? Many enterprises prohibit any sort of dynamic address assignment in the name of "security." You and I may think that it's silly, but it's the reality on the ground. -- ===

Re: [systemd-devel] systemd-timedated support for NTP SRV records

On 4/14/25 10:38 AM, Mantas Mikulėnas wrote: It's not supported as far as I know, and personally I don't immediately see the purpose: if the domain name comes from DHCP then you can directly publish the NTP server address via DHCP, too (and I *think* networkd + timesyncd supports requesting t

Re: [systemd-devel] systemd-timedated support for NTP SRV records

Why wouldn't you use DHCP to assign a datacenter server's address? That's how my Linode VPS gets its address. I guess you could use an Ansible script, but then you could include the NTP server in that script. How does your server know what domain contains its NTP SRV record? Whatever configure

Re: [systemd-devel] systemd-timedated support for NTP SRV records

s Sent: Monday, April 14, 2025 10:38 AM To: SCOTT FIELDS Cc: Systemd Subject: [EXTERNAL] Re: [systemd-devel] systemd-timedated support for NTP SRV records On Mon, Apr 14, 2025, 18: 35 SCOTT FIELDS wrote: The current docs for systemd-timedated indicates the configuration only supports expli

Re: [systemd-devel] systemd-timedated support for NTP SRV records

On Mon, Apr 14, 2025, 18:35 SCOTT FIELDS wrote: > The current docs for systemd-timedated indicates the configuration only > supports explicit time server listings. > > Am I missing something in regards to support for DNS SRV records for NTP > service? > > AKA: > > _ntp._udp. > It's not supported

Re: [systemd-devel] systemd-resolved non recursive server?

On Sat, Apr 5, 2025, at 13:45, Phillip Susi wrote: > Can systemd-resolved be configured to NOT use an upstream recursive > server and perform its own queries? Or do I need bind for that? No, it can only act as a stub resolver, not a recursive resolver. You don't necessarily need BIND though, the

[systemd-devel] systemd-resolved non recursive server?

Can systemd-resolved be configured to NOT use an upstream recursive server and perform its own queries? Or do I need bind for that?

Re: [systemd-devel] systemd-repart MountPoint fails for esp partitions

On Tue, Mar 25, 2025 at 09:00:09PM -0600, Thayne Harbaugh wrote: > Response in-line: > > On Tue, 2025-03-25 at 16:53 -0600, Thayne Harbaugh wrote: > > Greetings, > > > > systemd-repart MountPoint fails to generate a correct fstab entry for > > esp partitions.  It generates a standard partition UU

Re: [systemd-devel] systemd-repart MountPoint fails for esp partitions

This is about fs UUID, not GPT PARTUUID. vfat filesystems do not support standard UUID format for historical reason. On 4/2/25 14:32, Karel Zak wrote: On Tue, Mar 25, 2025 at 09:00:09PM -0600, Thayne Harbaugh wrote: Response in-line: On Tue, 2025-03-25 at 16:53 -0600, Thayne Harbaugh wrote:

Re: [systemd-devel] systemd-tmpfiles, unsafe path transitions

Hello, Isn't there UID mapping support for this purpose? For that specific NFS mount, you could map whatever UID it is to UID 0 Best, Adrian On Thu, Mar 27, 2025, 15:03 James Muir (jamesmui) wrote: > > > Is there a conf option or an environment variable I can use to disable > the unsafe path t

Re: [systemd-devel] systemd-tmpfiles, unsafe path transitions

> > Is there a conf option or an environment variable I can use to disable the > > unsafe path transition check? > > No there is not. It's a security hole what you are doing there... > > > Failing that, is there a way I can change the ownership systemd-tmpfiles > > sees? > > Why not just fix the

Re: [systemd-devel] systemd-tmpfiles, unsafe path transitions

On Mi, 26.03.25 17:51, James Muir (jamesmui) (james...@cisco.com) wrote: > I am doing dev work on a linux system and I am mounting the root filesystem > via NFS to make my work-flow easier. > > Unfortunately, the directory I am NFS mounting is not owned by root, and this > causes some of the dir

[systemd-devel] systemd-tmpfiles, unsafe path transitions

I am doing dev work on a linux system and I am mounting the root filesystem via NFS to make my work-flow easier. Unfortunately, the directory I am NFS mounting is not owned by root, and this causes some of the directives processed by the systemd-tmpfiles utility during boot (e.g. in systemd-tmp

Re: [systemd-devel] systemd-repart MountPoint fails for esp partitions

On Di, 25.03.25 16:53, Thayne Harbaugh (tha...@mastodonlabs.com) wrote: > Greetings, > > systemd-repart MountPoint fails to generate a correct fstab entry for > esp partitions. It generates a standard partition UUID which does not > work for FAT file systems - a FAT volume ID must be used analogo

Re: [systemd-devel] systemd-repart MountPoint fails for esp partitions

Response in-line: On Tue, 2025-03-25 at 16:53 -0600, Thayne Harbaugh wrote: > Greetings, > > systemd-repart MountPoint fails to generate a correct fstab entry for > esp partitions.  It generates a standard partition UUID which does > not > work for FAT file systems - a FAT volume ID must be used

[systemd-devel] systemd-repart MountPoint fails for esp partitions

Greetings, systemd-repart MountPoint fails to generate a correct fstab entry for esp partitions. It generates a standard partition UUID which does not work for FAT file systems - a FAT volume ID must be used analogous to what is generated for vfat in mkfs-util.c:make_filesystem(). The FAT volume

[systemd-devel] systemd-boot and USB serial

Hi, I'm trying to test a USB FTDI device with systemd-boot. I've got the UEFI driver loaded once I finally worked out how to build it from EDK2. I know I've got everything hooked up correctly because starting serial-getty@ttyUSB0 works as expected. I'm testing with VirtualBox but can easily t

[systemd-devel] systemd-resolved floods the network with mDNS packets

Please help stop the mDNS flood. I have enabled MulticastDNS in one of my network files (see below). When I start the systemd-resolved service it consumes >90% CPU. Other machines on the network are being flooded by mDNS packets and their CPU also gets loaded. Capturing a trace with tcpdump sho

Re: [systemd-devel] systemd-devel Digest, Vol 178, Issue 26

> Date: Sat, 22 Feb 2025 08:22:18 +0300 > From: Andrei Borzenkov > To: mailto:systemd-devel@lists.freedesktop.org > Subject: Re: [systemd-devel] PID 1 "crashes" during boot, disabling > systemd-coredump, but system boots normally anyway > Message-ID:

Re: [systemd-devel] systemd-remount-fs and ConditionKernelCommandLine=!rw

On Sa, 01.02.25 14:16, Etienne Champetier (champetier.etie...@gmail.com) wrote: > Hello, > > If we have `rw` kargs, is systemd-remount-fs.service actually needed > ? The service is responsible for applying the mount options listed in /etc/fstab onto all API VFS (i.e. /proc/ + /sys/ & co), the roo

Re: [systemd-devel] systemd-networkd: IPv6 prefix delegation disabled by ipv6forwarding=true

> On 14 Jan 2025, at 09:04, Max Gautier wrote: > > I have similar setup (PPPoE, /48 delegation) here are my network files: > (It's been a while, I don't remember the reason for everything) > Thanks to all of you that responded. I now have every working with the information you provided. Thi

[systemd-devel] systemd-remount-fs and ConditionKernelCommandLine=!rw

Hello, If we have `rw` kargs, is systemd-remount-fs.service actually needed ? For context when using anaconda to install an rpm-ostree based system, you get an entry in fstab for `/` with option `defaults`. When trying to switch to composefs, / can only be readonly (composefs), so systemd-remount

Re: [systemd-devel] systemd portable services vs systemd-sysext

appropriate for each. So here's what I'd propose in my model to use for this.” Thanks Umut From: systemd-devel on behalf of Sopena Ballesteros Manuel Date: Saturday, 25 January 2025 at 17:57 To: systemd-devel@lists.freedesktop.org Subject: [systemd-devel] systemd portable services

Re: [systemd-devel] systemd portable services vs systemd-sysext

Hi, based on my understanding sysexts are geared towards scenarios where either other services need to consume your files or you are able to consume files by the OS, e.g. system libraries. You can for example build these using mkosi which uses your normal distribution packages. Portable services

[systemd-devel] systemd portable services vs systemd-sysext

Dear systemd community, I’m a sysadmin currently learning Linux and systemd, and I’m exploring technologies that allow me to add and remove applications to my system’s root filesystem in a plug-and-play fashion. I’m avoiding containers because I need a higher level of integration with the system

Re: [systemd-devel] systemd-devel Digest, Vol 177, Issue 26

he list at systemd-devel-ow...@lists.freedesktop.org When replying, please edit your Subject line so it is more specific than "Re: Contents of systemd-devel digest..." Today's Topics: 1. PathChanged= in systemd-254.21-150600.4.21.1.x86_64 of SLES15 SP6 (Windl, Ulrich)

Re: [systemd-devel] systemd-devel] systemd-devel] dbus-broker can be used for a "user" type bus accessible over tcp or not?

On 21-01-2025 15:34, Cristian Rodríguez wrote: On Tue, Jan 21, 2025 at 6:05 AM Erik Slagter wrote: So now we have wavered all responsibilities. Is it possible or is it not possible? Dbus-broker listening on tcp? If it's not possible, my question is answered and I can go move on. Come on..if

Re: [systemd-devel] systemd-devel] dbus-broker can be used for a "user" type bus accessible over tcp or not?

On 2025-01-21 11:05, Erik Slagter wrote: Duly noted! But as I already wrote to Lennart, this is for a home environment. Besides my hobby as a programmer, in daily life I am a network admin. So I am quite aware of all the dangers lurking. There is a reason I have quite a bunch of vlans, vrfs a

Re: [systemd-devel] systemd-devel] dbus-broker can be used for a "user" type bus accessible over tcp or not?

On Tue, Jan 21, 2025 at 6:05 AM Erik Slagter wrote: > So now we have wavered all responsibilities. Is it possible or is it not > possible? Dbus-broker listening on tcp? If it's not possible, my > question is answered and I can go move on. Come on..if you do that just configure stunnel to do what

Re: [systemd-devel] systemd-devel] dbus-broker can be used for a "user" type bus accessible over tcp or not?

Duly noted! But as I already wrote to Lennart, this is for a home environment. Besides my hobby as a programmer, in daily life I am a network admin. So I am quite aware of all the dangers lurking. There is a reason I have quite a bunch of vlans, vrfs and ssids. So believe me when I say there

Re: [systemd-devel] systemd-devel] dbus-broker can be used for a "user" type bus accessible over tcp or not?

On Mon, 20 Jan 2025 at 20:19:01 +0100, Erik Slagter wrote: > So I'd rather have dbus-broker listening to a TCP socket and if that can't > be done, using dbus-daemon. Please don't do either of these. Having a D-Bus "user bus" (session bus) listening on TCP and willing to execute arbitrary code was

Re: [systemd-devel] systemd-devel] dbus-broker can be used for a "user" type bus accessible over tcp or not?

Additionally: As a learning experiment I made an socat construction from a listening TCP socket to connecting Unix socket. And it works! Of course this is dirty beyond words and I certainly don't have the courage to try this on the main session or even system bus ;-) So I'd rather have dbus-

Re: [systemd-devel] systemd-bootchart, switch-root breakage

(jamesmui) Date: Thursday, 16 January 2025 at 05:49 To: systemd-devel@lists.freedesktop.org Subject: Re: [systemd-devel] systemd-bootchart, switch-root breakage > Isn't systemd-bootchart, like, dead? Last release is nine years old or so. The last release of systemd-bootchart, v235, was

Re: [systemd-devel] systemd-bootchart, switch-root breakage

> Isn't systemd-bootchart, like, dead? Last release is nine years old or so. The last release of systemd-bootchart, v235, was done in November 2023: https://github.com/systemd/systemd-bootchart/tags There hasn’t been much activity lately, but I wouldn’t call it dead (there are a few PRs open th

Re: [systemd-devel] systemd-cryptsetup credentials

unsubscribe On Wed, Jan 15, 2025 at 11:53 PM Andrei Borzenkov wrote: > 15.01.2025 18:54, David White wrote: > ... > > > > > davew@speed:~$ /usr/bin/systemd-cryptsetup --version > > systemd 257 (257.2) > ... > > > > > davew@speed:~$ systemd --version > > systemd 255 (255.4-1ubuntu8.4) > > The bul

Re: [systemd-devel] systemd-bootchart, switch-root breakage

unsubscribe On Thu, Jan 16, 2025 at 5:16 AM wrote: > Isn't systemd-bootchart, like, dead? Last release is nine years old or so. > > Better use systemd-analyze instead. > > See > https://wiki.archlinux.org/title/Improving_performance/Boot_process#Analyzing_the_boot_process > for more information.

[systemd-devel] systemd-bootchart, switch-root breakage

Isn't systemd-bootchart, like, dead? Last release is nine years old or so. Better use systemd-analyze instead. See https://wiki.archlinux.org/title/Improving_performance/Boot_process#Analyzing_the_boot_process for more information. BR Silvio

Re: [systemd-devel] systemd-bootchart, switch-root breakage

> I opened https://github.com/systemd/systemd-bootchart/issues/58 to track > this. Could someone explain why systemd-bootchart is being sent SIGHUP? Changing systemd-bootchart to ignore that signal isn’t difficult, but I would like to understand why PID 1 is sending it. Note that systemd-boot

Re: [systemd-devel] systemd-cryptsetup credentials

15.01.2025 18:54, David White wrote: ... davew@speed:~$ /usr/bin/systemd-cryptsetup --version systemd 257 (257.2) ... davew@speed:~$ systemd --version systemd 255 (255.4-1ubuntu8.4) The bulk of code is in the shared library and I have no idea what this mix does.

Re: [systemd-devel] systemd-cryptsetup credentials

I apologize in advance for the formatting, this is my first time using a mailing list and I don't know how to format it well. I can't get systemd-cryptsetup to accept the cryptsetup.pkcs11-pin credential. It doesn't seem to get used by systemd-cryptsetup, I still have to manually unlock it at boot

Re: [systemd-devel] systemd-cryptsetup credentials

On Wed, Jan 15, 2025 at 2:31 PM David White wrote: > > Hi there, > > Just want some help with setting credentials for systemd-cryptsetup@.service > services. > > I have a crypttab file with the following: > > (I set a label for this volume with a udev rule as I have to use a label) > I am not su

[systemd-devel] systemd-cryptsetup credentials

Hi there, Just want some help with setting credentials for systemd-cryptsetup@.service services. I have a crypttab file with the following: (I set a label for this volume with a udev rule as I have to use a label) os_crypt LABEL=os_luks nonetry-empty-password=1,luks,pkcs11-uri=auto ,disca

Re: [systemd-devel] systemd-bootchart, switch-root breakage

> **1. systemd-bootchart stops too early** > > According to "man systemd-bootchart", the recommended way to invoke bootchart > is via a kernel parameter: > > init=/usr/lib/systemd/systemd-bootchart > > That parameter causes systemd-bootchart to be executed as the new init > process when we swit

Re: [systemd-devel] systemd-networkd: IPv6 prefix delegation disabled by ipv6forwarding=true

I have similar setup (PPPoE, /48 delegation) here are my network files: (It's been a while, I don't remember the reason for everything) ==> /etc/systemd/network/10-extern0.link <== [Match] Path=platform-fe30.ethernet [Link] Name=extern0 ==> /etc/systemd/network/10-extern0.network <== [Match]

Re: [systemd-devel] systemd-networkd: IPv6 prefix delegation disabled by ipv6forwarding=true

On Mon, Jan 13, 2025, at 12:58, Barry Scott wrote: > This sets net.ipv6.conf.all.forwarding = 1 but, prefix delegation is broken. > > If I remove Ipv6Forwarding=true and then set > net.ipv6.conf.all.forwarding = 1 mnaually forwarding works. It could be useful to note that this setting does not a

Re: [systemd-devel] systemd-networkd: IPv6 prefix delegation disabled by ipv6forwarding=true

> The IPv6 is a /48. > > I have the IPv4 all working well. > > But the IPv6 configuration I cannot figure out. I have a similar set up and have this working. > [Network] > Address=2001x:x::x::1 You are specifying a /24 for IPv4, but nothing for IPv6. I'd suggest adding a /64 if you want to de

[systemd-devel] systemd-networkd: IPv6 prefix delegation disabled by ipv6forwarding=true

I'm building a router for my home using Fedora server as the base. I have a ISP that provides me with a IPv4 and Ipv6 over PPPoE. The IPv6 is a /48. I have the IPv4 all working well. But the IPv6 configuration I cannot figure out. I have two interface named internal and external. In /etc/syst

[systemd-devel] systemd-bootchart, switch-root breakage

Is anyone else using systemd-bootchart on a system that boots using an initial ramdisk? (e.g. like Fedora 41) I am fighting with two issues and am looking for some advice. **1. systemd-bootchart stops too early** According to “man systemd-bootchart”, the recommended way to invoke bootchart i

Re: [systemd-devel] systemd-resolved : How to change permanently to 127.0.0.54

> My DNS servers are currently manually specified in > /etc/systemd/network/10-ens.network as follows: > > [Match] > Name=en* > [Network] > DHCP=ipv4 > DNS=first-server-ip-goes-here > DNS=second-server-ip-goes-here > DNS=third-server-ip-goes-here > [DHCPv4] > UseDNS=false > UseNTP=false > [IPv6Acc

Re: [systemd-devel] systemd-resolved : How to change permanently to 127.0.0.54

On Mon, Dec 23, 2024, at 09:09, Laura Smith wrote: > Sent with Proton Mail secure email. > > On Monday, 23 December 2024 at 14:00, Kevin P. Fleming > wrote: > >> The simplest fix is to set "DNSSEC=no" > > That seems to me to be a bit of a "sledgehammer to crack a nut". > > The man page for resol

Re: [systemd-devel] systemd-resolved : How to change permanently to 127.0.0.54

On Mon, Dec 23, 2024, at 08:37, Laura Smith wrote: > Sent with Proton Mail secure email. > > On Monday, 23 December 2024 at 12:23, Adam Nielsen > wrote: > >> But what's the underlying issue? Maybe there's a different fix? > > Its been a while so I can't remember the exact details, but I know its

Re: [systemd-devel] systemd-resolved : How to change permanently to 127.0.0.54

Sent with Proton Mail secure email. On Monday, 23 December 2024 at 14:00, Kevin P. Fleming wrote: > The simplest fix is to set "DNSSEC=no" That seems to me to be a bit of a "sledgehammer to crack a nut". The man page for resolved.conf says: "It is recommended to set DNSSEC= to true on

Re: [systemd-devel] systemd-resolved : How to change permanently to 127.0.0.54

On Monday, 23 December 2024 at 13:10, Itxaka Serrano Garcia wrote: > Hallo there! > > If using systemd-resolved, cant you just configure the DNS in > /etc/systemd/resolved.conf or /etc/systemd/resolved.conf.d/ directly so it > setups your desired address? My DNS servers are currently manu

Re: [systemd-devel] systemd-resolved : How to change permanently to 127.0.0.54

Sent with Proton Mail secure email. On Monday, 23 December 2024 at 12:23, Adam Nielsen wrote: > But what's the underlying issue? Maybe there's a different fix? Its been a while so I can't remember the exact details, but I know its to do with Postfix. Postfix creates a copy (not symlin

Re: [systemd-devel] systemd-resolved : How to change permanently to 127.0.0.54

On Mon, Dec 23, 2024 at 11:08:56AM +, Laura Smith wrote: > > I believe you can just remove the symlink at /etc/resolv.conf and > > replace it with a file that points to 127.0.0.54. > Thanks Daniel, that has been my work-around, a systemd timer checking for > 127.0.0.53 and doing a sed on /etc/

Re: [systemd-devel] systemd-resolved : How to change permanently to 127.0.0.54

Hallo there! If using systemd-resolved, cant you just configure the DNS in /etc/systemd/resolved.conf or /etc/systemd/resolved.conf.d/ directly so it setups your desired address? If using any other resolver/network manager, just remove the symlink from /etc/resolv.conf to the systemd resolv.conf s

Re: [systemd-devel] systemd-resolved : How to change permanently to 127.0.0.54

> Thanks Daniel, that has been my work-around, a systemd timer checking > for 127.0.0.53 and doing a sed on /etc/resolv.conf > > So I came here looking for a more "official" work-around, e.g. some > config file param I missed. > > But it looks like there isn't, so I guess I'll just leave my > wor

Re: [systemd-devel] systemd-resolved : How to change permanently to 127.0.0.54

On Monday, 23 December 2024 at 07:45, Daniel Foster wrote: > I believe you can just remove the symlink at /etc/resolv.conf and > replace it with a file that points to 127.0.0.54. > Thanks Daniel, that has been my work-around, a systemd timer checking for 127.0.0.53 and doing a sed on /etc/re

Re: [systemd-devel] systemd-resolved : How to change permanently to 127.0.0.54

I believe you can just remove the symlink at /etc/resolv.conf and replace it with a file that points to 127.0.0.54. (apologies Laura, I forgot to reply all) On Mon, Dec 23 2024 at 07:30:38 +00:00:00, Laura Smith wrote: On Sunday, 22 December 2024 at 22:13, Kevin P. Fleming systemd-resolved

Re: [systemd-devel] systemd-resolved : How to change permanently to 127.0.0.54

On Sunday, 22 December 2024 at 22:13, Kevin P. Fleming systemd-resolved does not write or otherwise modify /etc/resolv.conf; your > system may have a symlink at /etc/resolv.conf which points to one of the > files created by systemd-resolved. Whatever tool or method is managing that > is the o

Re: [systemd-devel] systemd-resolved : How to change permanently to 127.0.0.54

Sent with [Proton Mail](https://proton.me/mail/home) secure email. On Sunday, 22 December 2024 at 22:13, Kevin P. Fleming wrote: > systemd-resolved does not write or otherwise modify /etc/resolv.conf; So you're saying this statement at the top of /etc/resolv.conf is a lie ? $ cat /etc/resolv.

Re: [systemd-devel] systemd-resolved : How to change permanently to 127.0.0.54

On Sun, Dec 22, 2024, at 11:49, Laura Smith wrote: > At present systemd-resolved inserts 127.0.0.53 into /etc/resolv.conf > > Certain applications on my system have problems with this, relating to DNSSEC > and they work perfectly with the "proxy-only" 127.0.0.54 instead. > > What is the permanen

[systemd-devel] systemd-resolved : How to change permanently to 127.0.0.54

At present systemd-resolved inserts 127.0.0.53 into /etc/resolv.conf Certain applications on my system have problems with this, relating to DNSSEC and they work perfectly with the "proxy-only" 127.0.0.54 instead. What is the permanent way to ensure that systemd-resolved inserts .54 and not .53

Re: [systemd-devel] systemd-networkd-wait-online doesn't wait for DNS

On Sun, Dec 8, 2024 at 8:00 AM Adam Nielsen wrote: > > Hi all, > > Is there a way to tell the systemd-networkd-wait-online service to wait > until DNS is working before continuing? > I have a PR open for this, which should hopefully be in v258. https://github.com/systemd/systemd/pull/34640 -NR

[systemd-devel] systemd 257 released

🎆 A new, official systemd release has just 🎉 been 🎊 tagged 🍾. Please download the tarball here: https://github.com/systemd/systemd/archive/v257.tar.gz Changes since the previous release: Incompatible changes: * The --purge switch of systemd-tmpfiles (which was added in

  1   2   3   4   5   6   7   8   9   10   >