Re: [systemd-devel] sd-bus signal callback return value

2020-03-28 Thread Daan De Meyer
Hi, I've opened a pull request to clarify the return values of the callbacks and their effect: https://github.com/systemd/systemd/pull/15253. It's not complete yet but the idea is to add answers for all your questions to the docs. Regards, Daan On Tue, 24 Mar 2020 at 21:44, Stanislav Angelovič

Re: [systemd-devel] Reasoning behind sd_bus_error argument to sd_bus_call?

2020-03-18 Thread Daan De Meyer
17 Mar 2020 at 20:17:05 +0100, Daan De Meyer wrote: > > I'm documenting sd_bus_call and its async variant and I was wondering > about the > > sd_bus_error output parameter that's passed to it. [...] I don't > > see immediately see the benefit of the sd_bus_error parameter in a

[systemd-devel] Reasoning behind sd_bus_error argument to sd_bus_call?

2020-03-17 Thread Daan De Meyer
method call? I don't see immediately see the benefit of the sd_bus_error parameter in a D-Bus client since I can simply check the return value instead which seems to contain the same information looking at the implementation. Regards, Daan De Meyer

[systemd-devel] Shut down system after all sshd instances terminate

2020-08-23 Thread Daan De Meyer
Hi, After following http://0pointer.de/blog/projects/socket-activated-containers.html which details how to set up a socket activated container, I'm looking into ways to have the container automatically shut down when the last ssh connection terminates. My idea was to have each sshd instance take

Re: [systemd-devel] Shut down system after all sshd instances terminate

2020-08-23 Thread Daan De Meyer
] > StopWhenUnneeded=true > > [Service] > Type=oneshot > RemainAfterExit=yes > > # Not sure if SuccessAction works > # probably does but you might need a dummy ExecStart=/sbin/true then > ExecStop=systemctl poweroff > #SuccessAction=exit > ``` > > Benjamin > >

Re: [systemd-devel] Shut down system after all sshd instances terminate

2020-08-23 Thread Daan De Meyer
of this template is started to handle the connection. Now, what I want to achieve is that when all instances of this sshd template exit after at least one instance has started, the system shuts down. Daan On Sun, 23 Aug 2020 at 14:47, Daan De Meyer wrote: > > Hi, > > After foll

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-15 Thread Daan De Meyer
ettering wrote: > On Di, 14.07.20 22:15, Daan De Meyer (daan.j.deme...@gmail.com) wrote: > > > > About your other comments, systemd sits in user space and can query > > (depend > > > upon) terminfo. Then, it should be able to support "whatever" termin

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-14 Thread Daan De Meyer
I just tried vt241 and didn't get colorized output in konsole. I looked around a bit and it doesn't really seem supported at all by terminal emulators (or at least none that I found). I also tried TERM=xterm-256color with 8 different terminal emulators and got colors with all of them. My workflow

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-14 Thread Daan De Meyer
to work when using mkosi. Thanks for all the info as well. It's always fun to read how stuff was done back in the early days. Daan On Tue, 14 Jul 2020 at 21:04, Christopher Cox wrote: > On 7/14/20 1:48 PM, Daan De Meyer wrote: > > I just tried vt241 and didn't get colorized output in ko

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-11 Thread Daan De Meyer
aan On Sat, 11 Jul 2020 at 20:04, Lennart Poettering wrote: > On Sa, 11.07.20 17:51, Daan De Meyer (daan.j.deme...@gmail.com) wrote: > > > Hi, > > > > I was playing around with mkosi's qemu support, more specifically adding > > the -nographic option to have the virtual m

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-11 Thread Daan De Meyer
Nevermind that, I just forgot to remove my override file that set TERM=linux for serial-getty@ttyS0. Daan On Sat, 11 Jul 2020 at 20:31, Daan De Meyer wrote: > > TERM=linux means Linux console, but that's just too much, as it not > > only implies a multitude of ESC sequen

[systemd-devel] vt220 default for serial console still relevant?

2020-07-11 Thread Daan De Meyer
Hi, I was playing around with mkosi's qemu support, more specifically adding the -nographic option to have the virtual machine output in my terminal instead of a separate window. After figuring out that I had to add console=ttyS0 to mkosi's kernel command line, I got the output from the vm in my

Re: [systemd-devel] mkosi question: third party repos + dnf modules

2020-12-07 Thread Daan De Meyer
Hi, --repositories in mkosi is currently a bit limited. For Fedora and CentOS, we only support passing names of existing repositories that should be enabled. https://github.com/systemd/mkosi/issues/536 reported a similar problem. We should definitely make this work better than it does now but

Re: [systemd-devel] USB installer for mkosi

2023-08-18 Thread Daan De Meyer
Unfortunately there's no ready made answer yet here. We're busy designing and implementing a solution for these problems. https://github.com/systemd/systemd/pull/27792 has more details. Cheers, Daan On Fri, 18 Aug 2023, 19:44 Nils Kattenbeck, wrote: > Hi, > > currently I am building a

Re: [systemd-devel] issues with systemd-cryptsetup@.service after in 251-rc3

2022-05-19 Thread Daan De Meyer
I'd also recommend opening an issue on the upstream issue tracker (https://github.com/systemd/systemd/issues). It'd be great if you could include a full journal (just zip up /var/log/journal) and the contents of systemd-cryptsetup@myluksdev.service if possible to help with debugging. Cheers,

Re: [systemd-devel] mkosi dnf install packages failed

2023-03-18 Thread Daan De Meyer
See the hacking guide, we depend on very latest mkosi from git. On Fri, 17 Mar 2023, 22:55 William Roberts, wrote: > I am on Fedora 37, I did a dnf up and rebooted to make sure that's not > the issue. > > With the mkosi from the pkg manager, I am getting: > mkosi > mkosi: error: unrecognized

Re: [systemd-devel] systemd enables custom service units on firstboot

2023-04-29 Thread Daan De Meyer
you I would ship 99-disable.preset and add 85-mydevice.preset enabling only the services you want to be enabled. Cheers, Daan On Sat, 29 Apr 2023, 17:47 Martin Petzold, wrote: > Dear Daan, > Am 29.04.23 um 17:43 schrieb Daan De Meyer: > > Systemd does a preset on first boot

Re: [systemd-devel] systemd enables custom service units on firstboot

2023-04-29 Thread Daan De Meyer
Systemd does a preset on first boot when there's no machine ID yet. If no preset from a preset file applies, the default is to enable it. Since debian does not ship a 99-disable.preset with disable * in it, all services are enabled on firstboot on Debian. Cheers, Daan On Sat, 29 Apr 2023, 17:27

Re: [systemd-devel] How to debug systemd-pcrphase-initrd.service failure

2023-12-06 Thread Daan De Meyer
Note that we also have `InitrdPackages=` in the latest mkosi release which allows you to add extra packages to the default initrd without having to build one separately. Cheers, Daan On Wed, 6 Dec 2023 at 14:26, Renjaya Raga Zenta wrote: > > Yes, I think now I understand that mkosi will build

Re: [RFC] initoverlayfs - a scalable initial filesystem

2023-12-09 Thread Daan De Meyer
> We have been working on a new initial filesystem called initoverlayfs. > It is a new filesystem that provides a more scalable approach to > initial filesystems as opposed to just using initrds. We are writing > this RFC to the systemd and dracut mailing lists (feel free to forward > to UAPI

Re: [systemd-devel] enable systemd-resolved in early boot (dracut)

2024-03-19 Thread Daan De Meyer
Hi Aleksandar, > I want to enable systemd-resolved in early boot so that `clevis` can > resolve `tang` address by mdns. This will simplify local network > configuration by not relying on static IP addresses. > But it seems that is not enabled by default. > Is there a way to tell dracut to also

Re: [systemd-devel] repart: How to use CopyBocks= with usr-verity?

2024-03-31 Thread Daan De Meyer
Hi Nils, Pretty sure nobody ever tried this. The root hash might be changing because we format the verity hash partition with different parameters than it was originally formatted with in your case. I assume the roothash will only stay the same if the verity format arguments are exactly the same.

Re: [systemd-devel] mkosi config to build minimal Ubuntu 22.04 VM image?

2024-04-03 Thread Daan De Meyer
r Daan, > > > Thank you very much for your reply. > > > Am 04.03.24 um 15:52 schrieb Daan De Meyer: > > > Please see the config included in the mkosi repository itself: > > https://github.com/systemd/mkosi/blob/main/mkosi.conf and > > https://github.com/syst

Re: [systemd-devel] mkosi config to build minimal Ubuntu 22.04 VM image?

2024-03-04 Thread Daan De Meyer
Hi Paul, Please see the config included in the mkosi repository itself: https://github.com/systemd/mkosi/blob/main/mkosi.conf and https://github.com/systemd/mkosi/tree/main/mkosi.conf.d. This should help you get started. https://mkosi.systemd.io/bootable.html shows how to build a minimal bootable