!PSmBFWNKoXmlQBzUQf:helsinki-systems.de

Stage 1 systemd

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

Load older messages


SenderMessageTime
20 Sep 2022
@m_algery:leohoo.xyz@m_algery:leohoo.xyz left the room.15:18:10
23 Sep 2022
@elvishjerricco:matrix.org@elvishjerricco:matrix.org Zhaofeng Li: While I'm largely OK with https://github.com/NixOS/nixpkgs/pull/189676/ I had another thought about the patch. Couldn't we just change that hard coded absolute path to something in /etc and configure said directory in NixOS with environment.etc rather than taking on the risk that we could be wrong about relative paths being safe? 01:23:13
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgJust seems like changing the path and populating it would be a less severe change01:24:31
@zhaofeng:zhaofeng.liZhaofeng Li If we add it in a fixed runtime path, something like /run/opengl-driver (I remember an RFC to change the name) seems better than /etc 02:14:24
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgsure, either way02:14:45
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgjust seemed better than patching actual code, y'know?02:15:04
@zhaofeng:zhaofeng.liZhaofeng Li Actually /run/opengl-driver doesn't appear to be very extensible at the moment 🥲 02:17:29
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgyea i've had ideas for things to do similar to that but there isn't really a good mechanism in place. That'd be a nice improvement to make to nixos02:18:38
@oxalica:matrix.org@oxalica:matrix.org
In reply to @zhaofeng:zhaofeng.li
If we add it in a fixed runtime path, something like /run/opengl-driver (I remember an RFC to change the name) seems better than /etc
is /run already populated in initrd stage?
02:40:36
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgNot exactly so we'd have to also set it up separately in initrd before luks devices start coming online.02:47:23
@oxalica:matrix.org@oxalica:matrix.org
In reply to @elvishjerricco:matrix.org
Not exactly so we'd have to also set it up separately in initrd before luks devices start coming online.
mounting another tmpfs just for this seems not convincing
03:44:41
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgi mean it's the same tmpfs03:45:08
@elvishjerricco:matrix.org@elvishjerricco:matrix.org /run is the same from before anything starts in stage 1 all the way to the very end of shutdown 03:45:33
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgwell, systemd starts as pid 1 in stage 1 and mounts /run, /dev, /proc, and /sys before starting anything03:45:58
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgbut yea we would have to do the setup twice, once in stage 1 and once in stage 203:46:32
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.deBut who populates /run in stage 1?08:15:46
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.deWe're about to rebuild the activation script from stage 2 here08:16:25
@elvishjerricco:matrix.org@elvishjerricco:matrix.org Janne Heß: It'd just have to be a service with Before=cryptsetup-pre.target 08:16:35
@elvishjerricco:matrix.org@elvishjerricco:matrix.org
In reply to @janne.hess:helsinki-systems.de
We're about to rebuild the activation script from stage 2 here
(as a brief aside, arguably stage 1 and stage 2 should actually be almost the same infrastructure, and it should simply be possible to make a NixOS config that's as stripped down as stage 1 needs to be)
08:17:56
@elvishjerricco:matrix.org@elvishjerricco:matrix.org
In reply to @janne.hess:helsinki-systems.de
We're about to rebuild the activation script from stage 2 here
* (as a brief aside, arguably stage 1 and stage 2 should actually be almost the same infrastructure, and it should simply be possible to make a NixOS config that's as stripped down as stage 1 needs to be; main difference between the two being make-initrd-ng closures instead of nix closures)
08:18:30
@k900:0upti.meK900Now that I think about it, I wonder if we could do a crime on WSL08:20:06
@k900:0upti.meK900And basically have initrd-as-root08:20:14
@k900:0upti.meK900 And reuse all the systemd-in-stage1 stuff 08:20:30
@k900:0upti.meK900 For context, the latest WSL update added native systemd-as-PID1 support 08:20:56
@k900:0upti.meK900But it doesn't have a good way to run the activation scripts08:21:09
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.deMaybe a question for #wsl:nixos.org ?08:21:42
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgI believe I've mentioned before that my zeroth attempt at systemd in stage 1 was literally just doing a nested nixos eval with lots of hacks stripping things out and then putting that in an initrd :P08:21:47
@arianvp:matrix.orgArianHappy to commit crimes on WSL08:21:54
@k900:0upti.meK900
In reply to @janne.hess:helsinki-systems.de
Maybe a question for #wsl:nixos.org ?
I've been posting there about my experiments with wrapping systemd
08:22:50
@k900:0upti.meK900So far kinda feels like the wrapper route is still easier 08:27:16

Show newer messages


Back to Room ListRoom Version: 6