| 19 Mar 2025 |
 Enzime | if you open nix repl ~/Code/nixcfg then type in nixosConfigurations.msi-linux.config.system.build.toplevel | 03:13:26 |
| Enzime | what happens? | 03:13:34 |
 erahhal | Says it's missing. I must have a typo in my root flake? Looking | 03:15:22 |
| erahhal | Ugh, I put the host config one level too high in the scope. Surprised the it didn't cause problems when I tried building other machines that are also defined in the flake | 03:16:51 |
| erahhal | thank you! | 03:16:52 |
| erahhal | I need to get more familiar with using the repl | 03:17:13 |
| erahhal | Ok, another question, so I installed to a second drive. The first drive has windows. I'm going to change the boot order so that the linux drive is first. The problem is that it didn't register the drive with the boot manager. I had to manually run efibootmgr -c etc etc etc. Is there a way to make sure the second drive gets registered with the boot manager? | 04:42:45 |
| erahhal | Though actually, it's still not showing up in the BIOS boot options. Guess that wasn't enough | 04:44:01 |
| erahhal | I'm guessing some extra config is necessary to get it to install a fully bootable system on a second drive? | 04:44:25 |
| erahhal | Figured it out, should use systemd rather than grub | 05:00:08 |
| erahhal | the nix wiki on dual boot seems to be out of date | 05:00:27 |
 Fernando Rodrigues | In reply to @erahhal:homefree.host
the nix wiki on dual boot seems to be out of date but... the wiki tells you to use systemd? | 05:42:29 |
| Fernando Rodrigues | what part of it is outdated? | 05:42:45 |
| erahhal | You know what, my reading comprehension sucks. | 05:43:17 |
| erahhal | nevermind | 05:43:18 |
| erahhal | it does specifically mention to use systemd if using multiple disks | 05:43:27 |
| Fernando Rodrigues |
When systemd-boot is installed to the same EFI System Partition (ESP) that Windows uses
sounds like it's the same disk to me
| 05:44:02 |
| Fernando Rodrigues | *
When systemd-boot is installed to the same EFI System Partition (ESP) that Windows uses...
sounds like it's the same disk to me
| 05:44:09 |
| Fernando Rodrigues | oh, wait, are you looking at nixos.wiki? | 05:47:41 |
| Fernando Rodrigues | That's an old, unofficial wiki. The actual wiki is under nixos.org: https://wiki.nixos.org/wiki/Dual_Booting_NixOS_and_Windows | 05:48:00 |
|  @asymmetric:matrix.dapp.org.uk left the room. | 09:48:11 |
 The Jia Tan of Datasets | 
Download 1000047688.jpg | 16:12:16 |
| The Jia Tan of Datasets | I'm getting a stage2 init script not found (impermanence/disko) any ideas? | 16:12:41 |
| The Jia Tan of Datasets | Here's the disk configs if anyone is willing to take a look.
https://warez.kernelpanic.cafe/Code/impermanence.nix.txt
https://warez.kernelpanic.cafe/Code/disko.nix.txt | 16:13:03 |
| 20 Mar 2025 |
| The Jia Tan of Datasets changed their display name from Ghost of Corporate Future to It's scary when I'm focused. | 19:08:21 |
| 21 Mar 2025 |
| The Jia Tan of Datasets changed their display name from It's scary when I'm focused to OpenAI brand ChatGPT®. | 15:23:11 |
|  Marcus joined the room. | 20:19:03 |
| 22 Mar 2025 |
| The Jia Tan of Datasets changed their display name from OpenAI brand ChatGPT® to Lizard in a Skin Suit. | 19:52:47 |
| 24 Mar 2025 |
 nicoty | Hello. I'm currently working on improving disko's support for bcachefs. So far, I have made a PR to add encryption support. Currently, I am working on adding subvolume support. However, I am having trouble getting this to work. This is the output when I run nix build --no-link .#checks.x86_64-linux.bcachefs-subvolumes --show-trace -L -v.
I suspect that a reason that this could happening might be due the order in which mountpoints are mounted. My theory is that descendant mountpoints (e.g., /ancestor/descendant) could be being mounted before ancestor mountpoints (e.g., /ancestor) have been created/mounted.
Does disko mount filesystems such that ancestor mountpoints are mounted before descendants, or is this behaviour dependent on how the _mount option (made with diskoLib.mkMountOption) for the relevant filesystem type is implemented?
I have tried to debug my implementation using nix build .#checks.x86_64-linux.bcachefs-subvolumes.driverInteractive; result/bin/nixos-test-driver --keep-vm-state, but this doesn't seem to be working properly, as it doesn't show the bcachefs filesystem that should have been created:
$ lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
fd0
sr0
vda ext4 1.0 nixos a7ac900e-9d30-45da-b745-56d7d190aedd 888.3M 2% /
vdb
In fact, it shows that same lsblk output for various other examples I tried it with (I also tried it with btrfs-subvolumes and simple-efi).
Is there another way I can go about debugging this?
| 10:47:05 |
 projectinitiative | Hey! I was working on adding advanced options for Bcachefs a few months ago. May want to poke around here: https://github.com/nix-community/disko/pull/961
There are some current gotchas that cause some of the issues you are facing. Using the bcachesfs fs formatter is limited which is why I went the route of creating a custom type similar to mdadm and zfs.
There are some systemd bugs that prevent the FS ground getting mounted properly/consistently during reboots | 12:45:51 |
