| 3 Dec 2025 |
 blitz | mmh ok. maybe I'll write my own script that handles this for now, let's see :) | 09:53:17 |
| blitz | but thanks! | 09:53:23 |
 lassulus | that is probably easier for now | 09:53:41 |
| 4 Dec 2025 |
|  Ido Samuelson joined the room. | 01:47:19 |
|  Tanja (she/her) changed their display name from Tanja (she/her) to Tanja (she/her) - ☎️ 4201. | 18:09:01 |
| 7 Dec 2025 |
 mou | Hi, disko community. I have a question. Couple years ago i installed nixos with disko integrated into installation. So disko was used to perform formatting of the disks. Since then configuration preserved in nixos configuration for this host. Overall config consist of nested elements: LUKS -> LVM -> Ext4 on partitions. Overtime i realized that 100Gb is too small for my nix-store volume. And planing to shrink home partition and LV and enlarge nix-store LV and corresponding partition.
But what i do not understand, what should i do with current disko cofiguration and how discrepancy of actual LV and Partition sizes with disko definition will affect NixOs boot process?
And what action should i take after making changes to LVM? | 16:32:09 |
 chaoflow | mou: I'd say the boot process does not care about the size of actual partitions, but rather about their existence and order. You could probably also use nixos-generate-config to get the filesSystems attribute set for configuration.nix - usually living in hardware-configuration.nix - and drop disko from the setup. | 16:50:54 |
| chaoflow | Note: with btrfs subvolumes or zfs datasets you wouldn't have the resizing problem, as those share the available space of one filesystem/partition while providing logical separation, e.g. for snapshots. In that case no LVM would be used but LUKS -> btrfs/zfs or using ZFS encryption, maybe not even LUKS - but I don't have experience with ZFS. | 16:53:16 |
| mou | Thank you for your answer. I thought about this trick as a precaution. fileSystems dictionary is much more undestandable and manageable when it comes to disaster recovery ))) | 16:54:01 |
 jappie | also, you can verify your config using nix repl, e.g. :bl nixosConfigurations.yourHost.config.environment.etc.fstab.source to check fstab (which uses some information from disko - mainly what to mount where) | 16:59:32 |
| mou | Thank you. This is invaluable. I actually always been interested how to check what disko configuration expands into. | 17:01:01 |
| jappie | there's also some systemd services that decrypt luks volumes I think, but I couldn't tell you which ones from the top of my head 😅 | 17:02:54 |
| 8 Dec 2025 |
|  Anna Aurora changed their display name from Anna Aurora 🏴☠️ to Anna Aurora (superseded by: @anna:annaaurora.eu). | 09:21:09 |
| Anna Aurora left the room. | 09:25:54 |
|  NixOS Moderation Bot banned  @notahacker666:matrix.org (ragebaiting). | 10:54:05 |
| 10 Dec 2025 |
|  JManch joined the room. | 23:23:58 |
| 11 Dec 2025 |
|  71rd joined the room. | 00:13:07 |
|  @znaniye:matrix.org left the room. | 16:15:32 |
| 15 Dec 2025 |
|  n4ch723hr3r (putting stuff in your name is cringe) joined the room. | 01:45:45 |
|  food style edible product changed their display name from redesign your logo to NPM is best PM. | 06:17:03 |
| food style edible product changed their display name from NPM is best PM to I vibe code in assembly. | 20:50:37 |
| food style edible product changed their display name from I vibe code in assembly to iVibe code assembly. | 20:50:55 |
| food style edible product changed their display name from iVibe code assembly to iVibe assembly for pacemakers. | 20:51:18 |
|  m0lok joined the room. | 21:54:52 |
| m0lok | Hello, I'm getting an error with the bcachefs example where 1 device is always cannot be mounted: | 23:48:11 |
| m0lok | https://gist.github.com/freexploit/055e3db448f015a0a549e40734946ba4 | 23:48:12 |
| m0lok | I want to build a vm | 23:49:03 |
| m0lok | so I'm using vmWithDisko | 23:49:17 |
| 16 Dec 2025 |
| food style edible product changed their display name from iVibe assembly for pacemakers to vibe code pacemakers. | 01:03:37 |
|  joeboe joined the room. | 05:55:36 |
