| 24 Apr 2023 |
 @aktaboot:tchncs.de | probably some old copy pasta from somewhere 🤔 I have no idea why I have these | 21:32:19 |
| @aktaboot:tchncs.de | oh | 21:32:30 |
 @elvishjerricco:matrix.org | in fact the only one of those that isn't in my desktop's initrd is rtsx_usb_sdmmc | 21:32:36 |
| @aktaboot:tchncs.de | and dm-snapshot | 21:32:54 |
| @elvishjerricco:matrix.org | I also don't have that one I don't think. But still that doesn't seem like a big space consumer | 21:33:25 |
| @aktaboot:tchncs.de | what's the differenc ebetween boot.inird.kernelModules and boot.kernelModules ? | 21:34:21 |
 @lily:lily.flowers | You can unpack your initrd and see what's taking up so much space directly | 21:34:30 |
| @aktaboot:tchncs.de | right' it's a cpio archive ? no .. it's an efi ? | 21:34:56 |
| @lily:lily.flowers | nix shell nixpkgs#dracut --run lsinitrd --unpack $(readlink -f /run/current-system/initrd) should unpack into current dir | 21:35:06 |
| @elvishjerricco:matrix.org | boot.initrd.kernelModules are the modules that must be loaded early during initrd. boot.kernelModules are the modules that must be loaded early during stage 2. boot.initrd.availableKernelModules are the modules that are available during initrd for on-demand loading | 21:35:11 |
| @aktaboot:tchncs.de | cpio archive disguised as efi ? | 21:35:15 |
| @elvishjerricco:matrix.org | aktaboot: It's not an efi at all. No idea why it gets that suffix | 21:35:33 |
| @aktaboot:tchncs.de | In reply to @elvishjerricco:matrix.org
boot.initrd.kernelModules are the modules that must be loaded early during initrd. boot.kernelModules are the modules that must be loaded early during stage 2. boot.initrd.availableKernelModules are the modules that are available during initrd for on-demand loading thank's | 21:35:42 |
| @lily:lily.flowers | It's probably two cpios concatenated, with one compressed before concat | 21:35:42 |
| @lily:lily.flowers | (and if it's two, the first cpio is probably microcode and you probably don't care about it) | 21:36:20 |
| @aktaboot:tchncs.de | In reply to @lily:lily.flowers
nix shell nixpkgs#dracut --run lsinitrd --unpack $(readlink -f /run/current-system/initrd) should unpack into current dir isn't that nix run ? | 21:38:15 |
| @lily:lily.flowers | In reply to @aktaboot:tchncs.de
isn't that nix run ? No because by default the dracut package would run dracut and we just want a specific bin from the dracut package | 21:38:37 |
| @aktaboot:tchncs.de | for some reason it's not working | 21:39:02 |
| @lily:lily.flowers | nix shell [pkg] --run [cmd] mostly does that. Just realized it needs quotes though I think | 21:39:03 |
| @lily:lily.flowers | * nix shell nixpkgs#dracut --run "lsinitrd --unpack $(readlink -f /run/current-system/initrd)" should unpack into current dir | 21:39:16 |
| @aktaboot:tchncs.de | error: unrecognised flag '--run` | 21:39:16 |
| @aktaboot:tchncs.de | * error: unrecognised flag '--run | 21:39:20 |
| @lily:lily.flowers | Oh... Let me go check manual page real quick | 21:39:28 |
| @elvishjerricco:matrix.org | It's nix shell [pkg] -c [cmd], no quotes required for [cmd] | 21:39:41 |
| @lily:lily.flowers | I might be confusing nix-shell and nix shell. If it's not --run it's probably -c | 21:39:41 |
| @lily:lily.flowers | * nix shell nixpkgs#dracut -c lsinitrd --unpack $(readlink -f /run/current-system/initrd) should unpack into current dir | 21:39:54 |
| @elvishjerricco:matrix.org | everything after -c becomes argv | 21:40:04 |
| @aktaboot:tchncs.de | thanks :) | 21:40:47 |
| @aktaboot:tchncs.de | the big blobs : systemd-stage-1 openssl btrfs-progs and tpm2-tss | 21:41:56 |
| @lily:lily.flowers | (yes, thank you for remembering ElvishJerricco. I get those flags confused more often than I should...) | 21:42:02 |
