!PSmBFWNKoXmlQBzUQf:helsinki-systems.de

Stage 1 systemd

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

You have reached the beginning of time (for this room).


SenderMessageTime
22 Apr 2023
@aktaboot:tchncs.de@aktaboot:tchncs.de I could not find where printing the <<< NixOS Stage 1 >>> string happens 🤔 14:20:19
@elvishjerricco:matrix.org@elvishjerricco:matrix.org I think that's just in stage-1-init.sh isn't it? Which is only for the scripted initrd, not systemd initrd 14:20:52
@aktaboot:tchncs.de@aktaboot:tchncs.deyep thanks :)\14:21:36
@aktaboot:tchncs.de@aktaboot:tchncs.de* yep thanks :)14:21:38
@aktaboot:tchncs.de@aktaboot:tchncs.de huh, I thought that that would be /init in the initrd 14:22:43
@elvishjerricco:matrix.org@elvishjerricco:matrix.org aktaboot: It is 14:25:50
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgfor scripted initrd anyway14:26:08
@aktaboot:tchncs.de@aktaboot:tchncs.de

so there are 2 initrds in the boot process ?

in my boot entry, the init script is the one that prints <<< NixOS Stage 2 >>> so that got me confused

14:29:42
@elvishjerricco:matrix.org@elvishjerricco:matrix.org aktaboot: We have two completely independent implementations of stage 1. Which one your system uses depends on if you've set boot.initrd.systemd.enable = true; 14:30:42
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgThe old one is what I call the "scripted initrd", and the new one is "systemd initrd"14:30:56
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgsystemd initrd is opt-in14:31:01
@elvishjerricco:matrix.org@elvishjerricco:matrix.organd does not use a lot of stuff from scripted initrd, like stage-1-init.sh14:31:12
@elvishjerricco:matrix.org@elvishjerricco:matrix.org * and does not use a lot of stuff from scripted initrd, like stage-1-init.sh 14:31:17
@elvishjerricco:matrix.org@elvishjerricco:matrix.orghttps://github.com/NixOS/nixpkgs/pull/22762314:31:31
@elvishjerricco:matrix.org@elvishjerricco:matrix.org Lily Foster Arian We should probably get this in as quickly as possible 14:31:58
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgWe can do the right fixes next14:32:07
@aktaboot:tchncs.de@aktaboot:tchncs.de I see, thanks, so that means the systemd initrd does not print <<< NixOS Stage 1 >>> ? 14:32:11
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgright14:32:18
@aktaboot:tchncs.de@aktaboot:tchncs.deokay that was my confusion, thanks :)14:32:34
@elvishjerricco:matrix.org@elvishjerricco:matrix.orghttps://github.com/NixOS/nixpkgs/pull/22763315:05:59
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgIn case anyone wants to help me hunt down potential things that break the assertions15:06:19
@jaredbaur:matrix.org@jaredbaur:matrix.org joined the room.21:02:05
23 Apr 2023
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgHm plymouith seems to be adding about 6 seconds to my initrd boot time.07:50:29
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgThe initrd systemd unit that imports my ZFS pool is basically instant, taking only as long as it takes to enter the password. But that import service takes about 6 seconds longer with plymouth, and it seems to take those 6 seconds for the password prompt to appear at all07:50:56
@elvishjerricco:matrix.org@elvishjerricco:matrix.org * The initrd systemd unit that imports my ZFS pool is basically instant, taking only as long as it takes to enter the password. But that import service takes about 6 seconds longer with plymouth, and it seems to spend those 6 seconds waiting for the password prompt to appear at all07:51:24
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.deWouldn't be surprised after looking at some Plymouth code. Their design doesn't seem to be optimal or even good 09:08:33

Show newer messages


Back to Room ListRoom Version: 6