| 23 Nov 2025 |
 spewdins | Hi friends | 15:39:03 |
| spewdins | I’m struggling to find a use case for disko | 15:39:12 |
| spewdins | What are some of the most common use cases? | 15:39:21 |
| spewdins | And, does it only ever make sense for a computer you know the hardware for? For example, a config for one specific mini pc which will be the same disks always, or vs a config for several different devices on a home network | 15:40:20 |
|  dave :3 set a profile picture. | 16:52:42 |
 Nagasaki | My best use case is in virtualisation. Like declaring how big your disk in a virtual machine is. | 20:21:16 |
| spewdins | ooo that’s a really good use case… | 20:21:43 |
 debtquity | can disko be used to re-configure partitions?
currently, system is setup like this:
NAME MOUNTPOINT LABEL SIZE
sda 223.6G
├─sda1 1M
├─sda2 /boot 500M
└─sda3 223.1G
├─pool-app /app 10G
└─pool-root / 213.1G
sdb 28.9G
├─sdb1 FIRMWARE 30M
└─sdb2 NIXOS_SD 28.9G
But really, I want to move the FIRMWARE labeled partition on sdb to sda
| 23:58:16 |
| 25 Nov 2025 |
|  Sylvie (They/She) 🏳️⚧️ changed their display name from Sylvie (any) 🏳️⚧️ to Sylvie (They/She) 🏳️⚧️. | 15:49:18 |
|  @steeringwheelrules:tchncs.de left the room. | 18:12:22 |
|  food style edible product changed their display name from Juggalo Championship Wrestling to redesign your logo. | 19:51:37 |
| 28 Nov 2025 |
|  mou joined the room. | 18:22:34 |
| 29 Nov 2025 |
|  not-jack joined the room. | 18:37:29 |
| 30 Nov 2025 |
| not-jack | whats the advantage to having both boot and an ESP partitions?
partitions = {
boot = {
size = "1M";
type = "EF02"; # for grub MBR
};
ESP = {
size = "1G";
type = "EF00";
content = {
type = "filesystem";
format = "vfat";
mountpoint = "/boot";
mountOptions = [ "umask=0077" ];
};
};
| 13:39:39 |
| not-jack | * whats the advantage to having both boot and an ESP partitions?
partitions = {
boot = {
size = "1M";
type = "EF02"; # for grub MBR
};
ESP = {
size = "1G";
type = "EF00";
content = {
type = "filesystem";
format = "vfat";
mountpoint = "/boot";
mountOptions = [ "umask=0077" ];
};
};
| 13:39:49 |
| not-jack | what does the boot partition do here? | 13:44:42 |
 hexa | that's called hybrid | 14:04:27 |
| hexa | if you don't care or the thing needs to be portable | 14:04:36 |
| not-jack | so i can get rid of it? | 14:05:47 |
| mou | I'm using systemd-boot (no grub) with UEFI, and for this it is enought to have single /boot with ESP like this
type = "gpt";
partitions = {
ESP = {
type = "EF00";
size = "2G";
content = {
type = "filesystem";
format = "vfat";
mountpoint = "/boot";
};
};
| 14:08:25 |
| mou | but your config mentioned MBR in comments, so it might be different situation for you | 14:09:13 |
| not-jack | this is the default config for single disk ext4 | 14:10:19 |
| not-jack | so i think we're in the same situation | 14:11:48 |
| mou | As i understand logic of the boot process, the important part is decide are you using UEFI. If yes, you have to have GPT partition table (not mbr) and old MBR requirement to have bootloader in first 512K of the drive is no longer reuirement. So this reservation for grub is not needed | 14:15:35 |
| not-jack | aha, so it's legacy for backwards compat with grum | 14:16:46 |
| not-jack | * aha, so it's legacy for backwards compat with grub | 14:16:48 |
| mou | It is not grub specific. It is applicable to any bootloader for MBR partitioned drive. All bootloader put their initialization code into first 512K right after partition table | 14:17:51 |
| not-jack | * aha, so it's legacy for backwards compat with grub MBR | 14:19:33 |
| mou | But i did not refreshed my knowledge in this area for last decade, so i might mix things up. So, if you want to be sure, do additional check. | 14:19:34 |
| not-jack | the check will be seeing if i can boot! | 14:19:50 |
