| 29 Jun 2023 |
 @lily:lily.flowers | Okay so the sd-initrd options left hidden seems to have been:
boot.initrd.systemd.users (and boot.initrd.systemd.users.[user].uid)boot.initrd.systemd.groups (and boot.initrd.systemd.groups.[group].gid)boot.initrd.services.udev.packagesboot.initrd.services.udev.binPackagesboot.initrd.systemd.dbus.enableboot.initrd.services.bcache.enableboot.initrd.services.swraid.enable
| 20:31:48 |
| @lily:lily.flowers | Sound good to remove visible = false ElvishJerricco? I'll push to the PR in a bit | 20:32:07 |
 @elvishjerricco:matrix.org | Sure. Also, this reminds me that we really need to fix up the optional disk features PR. Title says swraid but I think we want it to hit all these things that we're making optional | 20:33:32 |
| @elvishjerricco:matrix.org | Which is mainly lvm, bcache, and swraid, I think | 20:34:22 |
| @elvishjerricco:matrix.org | * Which is just lvm, bcache, and swraid, I think | 20:34:26 |
| @elvishjerricco:matrix.org | (and to reiterate, because idr if it's in the thread: The goal is to make these things on by default if the stateVersion is old, and to generate them with nixos-generate-config so new installations still don't need manual code) | 20:35:24 |
| 30 Jun 2023 |
 @aloisw:kde.org | In reply to @lily:lily.flowers
So why is boot.initrd.services.lvm.enable a hidden option if it is required to enable it for systemd-stage-1 whenever you have a LVM needed for root Is it required? My system always worked without it. | 07:08:10 |
| @aloisw:kde.org | boot.initrd.services.bcache.enable seems to be required on the other hand. | 07:09:32 |
| @lily:lily.flowers | In reply to @aloisw:kde.org
Is it required? My system always worked without it. The LUKS module enables it, if you are using that | 10:12:20 |
| @aloisw:kde.org | I do use boot.initrd.luks.devices.*, but I find it surprising that this one enables LVM, given that the only thing LUKS does is to encrypt partitions. | 13:56:16 |
| @lily:lily.flowers | In reply to @aloisw:kde.org
I do use boot.initrd.luks.devices.*, but I find it surprising that this one enables LVM, given that the only thing LUKS does is to encrypt partitions. It needs the udev rules for devicemapper | 14:06:53 |
| @lily:lily.flowers | So it enables them I guess. At least the implicit cryptsetup -> lvm2 dependency is less dumb than plymouth relying on systemd to tell it to quit in emergency shells (why does systemd do that instead of an override file or extra unit/dep to handle that not just in the plymouth project??) | 14:08:25 |
| @elvishjerricco:matrix.org | Lily Foster: Something weird happened in your force push to the unhide PR. https://github.com/NixOS/nixpkgs/compare/799a114821032cdc3490e3415b13ea389a476026..11d11093849fc45e574e1dce5520ee982c162cd8 | 16:22:01 |
| @elvishjerricco:matrix.org | no changes present | 16:22:06 |
| @elvishjerricco:matrix.org | so bjornfor's suggestion isn't in there | 16:22:17 |
| @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
so bjornfor's suggestion isn't in there It's in commit message | 17:01:55 |
| @lily:lily.flowers | There were no diff changes | 17:02:01 |
| @elvishjerricco:matrix.org | oh whoops my bad; thought there was meant to be a comment | 19:53:15 |
| @elvishjerricco:matrix.org | all good | 19:53:17 |
| @elvishjerricco:matrix.org | * oh whoops my bad; thought there was meant to be a comment in the descriptions | 19:54:10 |
| @elvishjerricco:matrix.org | * oh whoops my bad; thought there was meant to be a comment in the option descriptions | 19:54:15 |
| @elvishjerricco:matrix.org | though, actually, maybe it should be in the option descriptions, since they actually aren't relevant to scripted stage 1? I dunno, up to you Lily Foster | 19:55:25 |
| @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
though, actually, maybe it should be in the option descriptions, since they actually aren't relevant to scripted stage 1? I dunno, up to you Lily Foster I can add them after my next flight, since that is admittedly probably a good idea. It's not like I'll have much else to do waiting in an airport for a few hours | 20:24:51 |
| 1 Jul 2023 |
| @elvishjerricco:matrix.org | i wonder if the nixos test framework should be able to run the backdoor unit in stage 1 | 23:02:10 |
| @elvishjerricco:matrix.org | it could be like plymouth and survive across stages | 23:02:29 |
| 2 Jul 2023 |
| @elvishjerricco:matrix.org | Sweet. Extremely rough terrible proof of concept actually works. Can backdoor into stage 1 now. But I'm just starting a different shell in stage 1, killing it, and reconnecting the machine to the stage 2 shell later. I wonder if there's value in maintaining one shell process across stages and chroot'ing like plymouth does though. | 21:18:41 |
| @elvishjerricco:matrix.org | Like maybe there's things you could do to supervise the transition that might be useful? | 21:18:53 |
| 3 Jul 2023 |
 @nikstur:matrix.org | In reply to @elvishjerricco:matrix.org
i wonder if the nixos test framework should be able to run the backdoor unit in stage 1 That sounds lovely | 14:34:19 |
| 7 Jul 2023 |
 oddlama | I've run into a race condition when starting vms (microvm.nix), where guests have a filesystem declared as neededForBoot = true; type = "virtiofs";. It looks like the kernel module required to load these filesystems is just inserted via systemd-modules-load which has no defined ordering with regards to the file system mount units. Thus, it sometimes happens to late and the mounting fails. | 00:38:55 |
| oddlama | The module is available in the initramfs though, so I'm not sure whether this is a misconfiguration in microvm.nix or whether there is a missing dependency here. | 00:38:57 |
