| 28 Dec 2025 |
 ed209 | lol i see the problem lol, i've got the ssh syntax but trying https | 13:55:35 |
| ed209 | oof size large | 13:55:38 |
|  Shop Smart: Shop S-Mart changed their display name from food style edible product to Shop Smart: Shop S-Mart. | 17:36:12 |
|  @azahi:azahi.cc left the room. | 23:08:03 |
| 30 Dec 2025 |
|  vicgeentor changed their display name from vicnotor to vicgeentor. | 11:20:11 |
|  toph joined the room. | 19:21:32 |
|  zimward changed their display name from zimward @ 39c3 ☎️ 75947 to zimward. | 23:39:00 |
|  jappie changed their display name from jasper @ 39c3 ☎️ 62749 to jasper. | 23:38:40 |
| jappie | 23:40:10 |
| 1 Jan 2026 |
|  pinpox changed their display name from pinpox [DECT: 7479] to pinpox. | 00:26:44 |
|  matthewcroughan changed their display name from matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) to matthewcroughan. | 19:51:41 |
| 2 Jan 2026 |
|  belak joined the room. | 07:10:59 |
| belak | Does the name of luks partitions need to be unique? | 07:33:10 |
| belak | Specifically the nesting of drive -> luks/lvm_pv -> lvm_vg -> partition is pretty frustrating, and naming is really confusing so I'm having a hard time following it...
Like if I have main (drive) -> crypted (maybe crypted-main or luks-main if it needs to be unique) -> main (maybe vg-main if it needs to be unique) -> root and storage (drive) -> crypted (maybe crypted-storage or luks-storage) -> storage (or vg-storage) -> data
This works, but there's a lot of duplication and the structure is relatively unclear unless you really dig into it.
Is there a better way to do that or best practices around luks?
| 07:34:23 |
| belak | Playing around with it and using :lf . to experiment, yes - luks names need to be unique | 08:00:50 |
| belak | I also prefixed my vg's with vg- because they end up as /dev/vg-main/root | 08:01:37 |
| ed209 | In reply to @belak:matrix.org
Playing around with it and using :lf . to experiment, yes - luks names need to be unique yeah i was gonna say the name ends up in /dev/mapper/<name> | 12:47:36 |
| belak | It was mostly that I wasn't sure if disko made combined names, similar to /dev/disk/by-partlabel, where it makes disk-{disk name}-{part name} labels | 18:19:12 |
| 3 Jan 2026 |
|  Janik (they/them) changed their profile picture. | 13:14:41 |
| Janik (they/them) changed their profile picture. | 13:15:18 |
|  Tanja (she/her) changed their display name from Tanja (she/her) - ☎️ 4201 to Tanja (she/her). | 19:17:36 |
| 4 Jan 2026 |
| jappie changed their display name from jasper to jappie. | 10:59:43 |
 Tumble | could i use disko to format a qcow to test a config? | 12:40:46 |
 bandithedoge | yes:
https://github.com/nix-community/disko/blob/master/docs/interactive-vm.md
https://github.com/nix-community/disko/blob/master/docs/disko-images.md | 16:17:18 |
|  @josw:matrix.org left the room. | 18:03:43 |
| Tumble | do i have to create a system config? | 22:16:34 |
| 6 Jan 2026 |
|  zed joined the room. | 20:07:12 |
| zed | Hello there !
I'm new to disko (and nix/nixos in general 😓), and I was wondering if once I have a system setup with a certain layout with disko (let's say LVM, and then 2 LVs)...
changing the disk-config by adding an lv will be done incrementally or will destroy everything ? | 20:12:18 |
 lassulus | nothing will happen, the new things won't get applied. you need to run the format script manually if you want those changes to have an effect, but better check the script before running it, since that support is kinda undertested | 20:18:36 |
| zed | thanks, I'll check the script then :) | 20:19:58 |
