| 19 Mar 2022 |
 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 |
 Arian | 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 |
| Arian | 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 |
| Arian | 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 |
| Arian | why not? | 10:06:32 |
| @elvishjerricco:matrix.org | And a lot of people have small /boot partitions | 10:06:34 |
| Arian | 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 |
