| 28 Oct 2025 |
 lassulus | could be turned into an option value that could be overrideable | 11:36:14 |
| lassulus | probably next to diskSize on the disk type | 11:36:53 |
| lassulus | aeh imageSize I mean | 11:37:04 |
| 29 Oct 2025 |
|  danishsouls joined the room. | 16:02:02 |
| 1 Nov 2025 |
|  Gaétan Lepage changed their profile picture. | 22:53:23 |
| Gaétan Lepage changed their profile picture. | 22:54:19 |
| 2 Nov 2025 |
|  @dawnofmidnight:catgirl.cloud changed their display name from whispers to whispers (it/fae). | 17:58:10 |
|  chaoflow joined the room. | 19:06:04 |
| 3 Nov 2025 |
 lillecarl | https://github.com/nix-community/disko/blob/master/example/btrfs-subvolumes.nix
Doesn't this conflict with https://btrfs.readthedocs.io/en/latest/ch-mount-options.html
"Most mount options apply to the whole filesystem and only options in the first mounted subvolume will take effect. This is due to lack of implementation and may change in the future. This means that (for example) you can’t set per-subvolume nodatacow, nodatasum, or compress using mount options. This should eventually be fixed, but it has proved to be difficult to implement correctly within the Linux VFS framework." quite a bit? Which is the first mounted volume for example? | 22:00:37 |
| lillecarl | * https://github.com/nix-community/disko/blob/master/example/btrfs-subvolumes.nix
Doesn't this conflict with https://btrfs.readthedocs.io/en/latest/ch-mount-options.html
"Most mount options apply to the whole filesystem and only options in the first mounted subvolume will take effect. This is due to lack of implementation and may change in the future. This means that (for example) you can’t set per-subvolume nodatacow, nodatasum, or compress using mount options. This should eventually be fixed, but it has proved to be difficult to implement correctly within the Linux VFS framework."
quite a bit? Which is the first mounted volume for example? | 22:01:59 |
