!PSmBFWNKoXmlQBzUQf:helsinki-systems.de

Stage 1 systemd

83 Members
systemd in NixOs's stage 1, replacing the current bash tooling https://github.com/NixOS/nixpkgs/projects/5127 Servers

Load older messages


SenderMessageTime
7 Apr 2022
@elvishjerricco:matrix.org@elvishjerricco:matrix.org Janne Heß: Looking at the cryptsetup generator code... I think it's systemd-cryptsetup@.service, which has Before=blockdev@dev-mapper-%i.target 18:07:39
@elvishjerricco:matrix.org@elvishjerricco:matrix.organyway I think it's fine for it to be infinity. https://github.com/systemd/systemd/blob/e99ca1474145f7fad38bb0255d344f4ad7717ef5/src/shared/generator.c#L591 Looks like they just went with default settings for the unit, so the timeout is probably an oversight, considering your crypt devices in initrd are very likely literally required for boot18:09:21
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.deso should I just drop in an override? or leave that up to the user?18:11:06
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgConsidering the behavior of the old initrd was to let it wait for a password forever, I think users will expect the same from this initrd18:11:41
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgI know I'd be frustrated after a NixOS update to find that my remote server doesn't wait for me to log in over initrd networking to unlock the password before deciding to just fail.18:12:08
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgbut that's a very me-specific use case :P18:12:23
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.denah I can totally understand that18:14:12
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.delet me try dropping it in18:14:18
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.dealso, why is initrd.target not required for boot?18:14:28
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.deI'd rather get an emergency shell when the nixos activation fails…18:15:02
@elvishjerricco:matrix.org@elvishjerricco:matrix.org Keep in mind that boot.initrd.services.foo options won't apply to units created by generators. See the makefs hack in the bare bones PR 18:15:09
@elvishjerricco:matrix.org@elvishjerricco:matrix.org
In reply to @janne.hess:helsinki-systems.de
also, why is initrd.target not required for boot?
That is a good question...
18:15:19
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.de
In reply to @elvishjerricco:matrix.org
Keep in mind that boot.initrd.services.foo options won't apply to units created by generators. See the makefs hack in the bare bones PR
right, thanks
18:15:40
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgI think the systemd folks like for boot to be attempted no matter how much fails, just in case it at least works well enough to get to a better place for recovery18:15:53
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgworst case, you get dropped into emergency mode anyway, I guess?18:16:13
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.dewell I can still Ctrl+D in emergency mode18:16:20
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.deso I don't really get why we should continue booting18:16:29
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgwell sulogin might be disabled, or the boot might be unattended, I guess18:17:11
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.deyeah I guess18:17:18
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgreally if initrd.target fails, all options are suboptimal :P18:17:34
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.dethat‘s right, yes18:18:31
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.debtw I learned over the last night that hibernation doesn‘t work yet :/18:18:45
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgYea I wouldn't have expected it to18:18:57
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.dewell I did18:19:05
@elvishjerricco:matrix.org@elvishjerricco:matrix.orghibernation is weird and difficult18:19:06
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.de
-> Building pitaya locally
these derivations will be built:
  /nix/store/vf5rhxnfqnvya4wjawm0d7dxaqw9vz7a-unit-script-initrd-nixos-activation-start.drv
  /nix/store/dgqpzd9f5ghg6gwsgmwrxrdm80ndwxgc-unit-initrd-nixos-activation.service.drv
  /nix/store/9sc9r641hifz6bibqcjh87vr8k6l176c-initrd-units.drv
  /nix/store/9dgzv860grjjqw932fcjn4x5n3gwgw22-initrd.drv
  /nix/store/fibmbjqadkwkiwr732waggd0j7v50g29-nixos-system-pitaya-21.11.drv
error: writing to file: Operation not permitted
18:19:23
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.deawww great18:19:24
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgO_O18:19:36
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgwell that's very bad18:19:48
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.deI haven‘t seen that one before tbh18:20:38

There are no newer messages yet.


Back to Room ListRoom Version: 6