NixOS systemd | 588 Members | |
| NixOS ❤️ systemd | 164 Servers |
| Sender | Message | Time |
|---|---|---|
| 30 Jan 2025 | ||
| I fully understand that, and I have absolutely zero reason to push for the above. I'm happy if I can just run it myself. It's as you say, very niche | 12:10:31 | |
| which one is it exactly? I think all that have GPG support have pkcs too? | 13:12:16 | |
| Yes, they have pkcs support (AFAIK), but that can't be used in my setup, as I have more than 1 yubikey, which have identical GPG keys on them. So I can use any of them, to unlock my system | 13:13:37 | |
| You could enroll multiple key slots, one for each yubikey. Course that's rather inconvenient if you expect to be replacing yubikeys with new ones often | 13:16:12 | |
| but that seems like an unlikely concern eyJhb :P | 13:16:46 | |
| Not often, but I don't want to forget about it, and be shit out of luck :D | 13:17:13 | |
| It's all about your threat model, and in theory, mine should be "shits and giggles" | 13:17:38 | |
Hello, I need help setting up impermanence with the option initrd.systemd.enable enabled, The option boot.initrd.PostDeviceCommands does not work. | 20:35:22 | |
Download This is the config that I have right now, But it's giving me an error when I try to rebuild my system. | 20:35:34 | |
Download This is the error that I am getting. | 20:35:48 | |
| Rayane Nakib (ريان نقيب): have you seen this? https://discourse.nixos.org/t/devices-not-visable-using-initrd-systemd-with-btrfs/42871 | 20:39:59 | |
| Or this https://www.reddit.com/r/NixOS/comments/1d3iwy0/rollback_script_for_luksencrypted_btrfs_system/ | 20:41:10 | |
| But would be nice if impermanence updated that part of the readme, to be ready for systemd-initrd | 20:41:23 | |
I don't have the service systemd-cryptsetup@enc.service in my system, Is it only available in the initrd? If so what does the enc stand for? | 20:44:47 | |
Download I got this error before the prompt to type the LUKS password. | 21:03:51 | |
Download This is my current config. | 21:04:34 | |
| 31 Jan 2025 | ||
Is enc actually the name of your luks volume? | 00:10:46 | |
| I noted an issue on my test laptop the other day; didn't have time to look further yet. It has:
I hadn't used it in a while, and updated to current. The problem was that the second passphrase prompt with plymouth didn't get any keyboard input/focus/whatever. I suspect/assume it's something new with updated systemd, it worked fine before the upgrade. I got as far as confirming it also works normally if removing | 01:11:58 | |
| * I noted an issue on my test laptop the other day; didn't have time to look further yet. It has:
I hadn't used it in a while, and updated to current. The problem was that the second passphrase prompt with plymouth didn't get any keyboard input/focus/whatever. I suspect/assume it's something new with updated systemd, it worked fine before the upgrade. I got as far as confirming it also works normally if removing | 01:13:10 | |
| Can potentially look further on the weekend. It will also have jumped from 6.6.x to 6.12.x in the same upgrade | 01:15:04 | |
| I'm not sure how easy it will be to separate those things since they all landed in the same staging merge IIUC | 01:16:05 | |
| * I noted an issue on my test laptop the other day; didn't have time to look further yet. It has:
I hadn't used it in a while, and updated to current. The problem was that the second passphrase prompt with plymouth didn't get any keyboard input/focus/whatever. I suspect/assume it's something new with updated systemd, it worked fine before the upgrade. I got as far as confirming it also works normally if removing | 01:17:36 | |
| * I noted an issue on my test laptop the other day; didn't have time to look further yet. It has:
I hadn't used it in a while, and updated to current. The problem was that the second passphrase prompt with plymouth didn't get any keyboard input/focus/whatever. I suspect/assume it's something new with updated systemd, it worked fine before the upgrade. I got as far as confirming it also works normally if removing | 01:17:47 | |
In reply to @elvishjerricco:matrix.orgNo, It's crypted, I fixed that issue. | 09:04:38 | |
I got permission issues when trying to delete the root subvol, And I fixed them using this command chattr -i /btrfs_tmp/root/var/empty, But the initrd I got this error chattr: command not found, How can I remove the file /btrfs_tmp/root/var/empty in the initrd? | 09:37:21 | |
Download Current setup 👆 | 09:37:52 | |
* I got permission issues when trying to delete the root subvol, And I fixed them using this command chattr -i /btrfs_tmp/root/var/empty, But in the initrd I got this error chattr: command not found, How can I remove the file /btrfs_tmp/root/var/empty in the initrd? | 09:38:20 | |
I added the option boot.initrd.systemd.packages = [ pkgs.busybox ];, But the problem persisted. | 09:56:06 | |
I added the option boot.initrd.systemd.services.rollback.path = [ pkgs.busybox ];, And now I am getting mkdir: command not found? | 10:03:30 | |
Rayane Nakib (ريان نقيب): chattr comes from e2fsprogs. It's also in busybox, but you probably wanna use the e2fsprogs one. Anyway, the way to add a specific binary to the initrd is boot.initrd.systemd.extraBin.chattr = "${pkgs.e2fsprogs}/bin/chattr"; | 14:27:50 | |