| 21 Sep 2024 |
 matthewcroughan | * I like that disko doesn't inject any extra stuff, unless the user specifies it via postVM though, having to DIY it feels bad too though | 15:52:27 |
| matthewcroughan | * I like that disko doesn't inject any extra stuff, unless the user specifies it via postVM/postMount though, having to DIY it feels bad too though | 15:52:38 |
 Mic92 | doesn't systemd has some auto disk increase thingy? | 15:53:07 |
| matthewcroughan | Yeah but that only works well with systemd-reparted | 15:53:15 |
| matthewcroughan | and reparted sucks because it cannot build images for embedded devices due to demanding everything implement GPT | 15:53:27 |
| matthewcroughan | * and reparted sucks because it cannot build images for embedded devices due to demanding everything implement GPT properly | 15:53:32 |
| Mic92 | I think on-first-boot resizing is also different from disk images | 15:53:37 |
| matthewcroughan | you can't make an image with arbitrary start sector for example, where you would put uboot | 15:53:49 |
| matthewcroughan | I've played a lot with both disko and reparted, and reparted is only nice for x86 uefi, everything else is out of the window | 15:54:32 |
| matthewcroughan | disko can do everything | 15:54:41 |
| matthewcroughan | I also tried to coerce systemd into resizing the things that disko creates, but that can't be done, at least I couldn't figure it out | 15:55:14 |
| matthewcroughan | afaik you can only coerce systemd into doing that for you if you have made everything with reparted | 15:55:35 |
| matthewcroughan | In reply to @joerg:thalheim.io
I think on-first-boot resizing is also different from disk images it is, but you can't do it without impacting the disk image | 16:02:11 |
| matthewcroughan | You have to put some state on the disk image, so it knows that it's the first boot, there's no other strategy I know of that could indicate a disk image is being booted for the first time | 16:03:13 |
| matthewcroughan | zfs autoResize is cool though, only zfs could do that however | 16:03:45 |
| matthewcroughan | the strategy of touching a file in the disk image so the system knows when first-boot is happening, is filesystem agnostic | 16:04:20 |
| Mic92 | can you not the sentinil file the other way around? | 16:05:26 |
| Mic92 | And create the file after the resize? | 16:05:35 |
| matthewcroughan | That would mean that on any boot, it attempts to resize, unless told not to? | 16:06:03 |
| matthewcroughan | as opposed to attempting the resize only when told to | 16:06:49 |
| matthewcroughan | feels risky to me, unless we trust the filesystem utils very much | 16:07:09 |
| Mic92 | Well it only tries it once | 16:07:54 |
| matthewcroughan | systemd-reparted has solved all of this in their own way, not 100% sure how it's all implemented but it works well | 16:07:57 |
| matthewcroughan | they mark disks as managed by repart somehow | 16:08:07 |
| Mic92 | systemd-reparted probably checks if there is any space left that can be used. | 16:08:18 |
| matthewcroughan | and manage all this state | 16:08:19 |
|  ·☽•Nameless☆•777 · ± changed their profile picture. | 18:21:24 |
| 22 Sep 2024 |
 blimbus | Hi yall, not sure if I'm just stupid and missing something but disko in disko mode is failing to setup luks on an empty drive. If the drive aleady has partitions or anything else on it it works but otherwise just fails somewhere after partitioning. It makes a luks device with password "password" even though it is set to prompt and then doesnt open the volume so creating filesystems fails. | 22:13:05 |
| 26 Sep 2024 |
|  vendion joined the room. | 14:18:19 |
| 27 Sep 2024 |
 waterturkey | Hey disko fans - I'm looking for some advice. I have an Odroid H3 with three hard drives: 1 x 500GB NVME and 2 x 14TB SATA drives. I think I'd like to use zfs with the NVME being the root file system and the sata drives set up as a zfs mirror, but I'm wondering what y'all would recommend for this arrangement? Any feedback is greatly appreciated. | 00:15:27 |
