| 19 Mar 2022 |
 @elvishjerricco:matrix.org | I think systemd units sometimes put full paths in comments for like, documentation purpose? I guess? | 10:03:03 |
 colemickens | makes sense, thanks :) and thanks to y'all working on this :D | 10:03:09 |
 @arianvp:matrix.org | Problem is it's hard to prove the pruning is correct | 10:04:48 |
 bobvanderlinden |
I'm increasingly curious what sorts of things get pulled in automatically that you know can be culled out. I've seen it in other places myself but curious all the same
Same here 😅 Haven't done any research, would be useful to do so, but at the very least it didn't pull in man pages 😄
| 10:04:51 |
| @elvishjerricco:matrix.org | Arian: Yea, it's definitely a labor intensive thing to get initramfs exactly right. I think there's no way around this | 10:05:18 |
| @elvishjerricco:matrix.org | It's why we have the escape hatch of manually specifying paths to include | 10:05:40 |
| @arianvp:matrix.org | I dont really recall anymore how large my systemd initrd was without any optimisations but it wasn't too bad | 10:05:45 |
| @elvishjerricco:matrix.org | And I also intend to have a manual exclusion list | 10:05:52 |
| @arianvp:matrix.org | do we have some target we want to optimise for? I supposed 1/2 the amount of minimal RAM we recommend? | 10:06:03 |
| @elvishjerricco:matrix.org | Arian: The best I've gotten is about 20M and that's still too much | 10:06:07 |
| @arianvp:matrix.org | why is 20M too much? | 10:06:14 |
| @elvishjerricco:matrix.org | Because I don't want the new initramfs to be twice as big as the old one | 10:06:27 |
| @arianvp:matrix.org | why not? | 10:06:32 |
| @elvishjerricco:matrix.org | And a lot of people have small /boot partitions | 10:06:34 |
| @arianvp:matrix.org | ah yeh that's a good argument | 10:06:42 |
| @elvishjerricco:matrix.org | it's already a problem for plenty of users to see /boot filling up | 10:06:44 |
| bobvanderlinden | Hmm, at the moment, mine is 18M (/boot/kernels/9cvnrh9wh6r707klrv7aawl8zm8w22rs-initrd-linux-5.15.27-initrd) | 10:07:08 |
| @elvishjerricco:matrix.org | Also, on some systems I'm pretty sure the decompression of the initramfs is extremely costly | 10:07:14 |
| @arianvp:matrix.org | but what if we have a /boot/nix/store and initrd is just a small thing mounting that :Exploding head: | 10:07:23 |
| @elvishjerricco:matrix.org | my rpi boots with EFI and Grub and it takes 3 minutes to reach the kernel | 10:07:27 |
| @arianvp:matrix.org | then we can have garbage collection etc :P | 10:07:31 |
| @elvishjerricco:matrix.org | that's... actually an incredibly interesting idea lol | 10:07:51 |
| @elvishjerricco:matrix.org | In reply to @bobvanderlinden_:matrix.org
Hmm, at the moment, mine is 18M (/boot/kernels/9cvnrh9wh6r707klrv7aawl8zm8w22rs-initrd-linux-5.15.27-initrd) That's impressive | 10:08:06 |
| @elvishjerricco:matrix.org | Er, is that the systemd one or a regular one | 10:08:24 |
| @elvishjerricco:matrix.org | * Er, is that the systemd one or a regular one? | 10:08:26 |
| @arianvp:matrix.org | current one I suppose | 10:08:31 |
| @arianvp:matrix.org | Does FAT32 support hardlinks? | 10:08:38 |
| @arianvp:matrix.org | probably not right? | 10:08:49 |
| @elvishjerricco:matrix.org | no idea | 10:08:55 |
| * colemickens had historically seen that on rpi but it went away after some recent updates to grub/uboot or the rpi firmware iirc | 10:08:59 |
