Post B49TIykwSEa0LGv5t2 by ar@is-a.cat
(DIR) More posts by ar@is-a.cat
(DIR) Post #B49SR9BnRqgD3voPJY by domi@donotsta.re
0 likes, 0 repeats
“why are ubuntu initrd images 500MB in size” and other questions i don’t want to ask this afternoon
(DIR) Post #B49SV1ij9vcp3Z45xo by domi@donotsta.re
0 likes, 0 repeats
https://lists.ubuntu.com/archives/kernel-team/2023-July/141412.htmlare you for real. 152MB is what my largest initrd’s were uncompressed. what the hell are you doing
(DIR) Post #B49SZKfmdUuuzkk0wa by mothcompute@merping.synth.download
1 likes, 0 repeats
@domi boot to uplink feature (20 redundant copies)
(DIR) Post #B49Se7zZD8DL77HVVw by privateger@plasmatrap.com
1 likes, 0 repeats
@domi@donotsta.re at one point the nvidia DKMS stuff blew my images up into 200MB+and even that was insane :woozy_blahaj:
(DIR) Post #B49SeHs8TcDBkxsiJs by domi@donotsta.re
0 likes, 0 repeats
@mothcompute i could live in that 500MB of data. we’d play quake, maybe even unreal (1998). i’d have a sick riced WM too. and probably a few .xm’s for good measure500M is a lot of space
(DIR) Post #B49TIykwSEa0LGv5t2 by ar@is-a.cat
0 likes, 0 repeats
@domi I still remember hitting some weird issues around 10-13 years ago with initrds above some size (somewhere between 128 and 256M) - wanted to stick an entire liveusb in initrd - and ended up writing an elaborate toy to mount tmpfs early, followed by curl | tar and pivot_root. ,_,
(DIR) Post #B49TIz9OzI95Z8Md0q by domi@donotsta.re
0 likes, 0 repeats
@ar been there, done that :neocat_hug:
(DIR) Post #B49TOjKii2jCFKOh4y by vildis@infosec.exchange
0 likes, 0 repeats
@domi archwiki has this quote on EFI boot partition "It is recommended to make the partition 1 GiB [...]. If still in doubt, 4 GiB ought to be enough for anybody. "https://wiki.archlinux.org/title/EFI_system_partition#:~:text=If%20still%20in%20doubt%2C%204%20GiB%20ought%20to%20be%20enough%20for%20anybody%2E
(DIR) Post #B49TOjXTwaw6suMsyG by domi@donotsta.re
0 likes, 0 repeats
@vildis see, arch can at least share EFI with /boot. Unfortunately, this is a too high-intellect move for the likes of Canonical and Debian
(DIR) Post #B49WGIwHG57pvpddYG by lkundrak@metalhead.club
0 likes, 0 repeats
@domi gpu firmware probably
(DIR) Post #B49WGJ6CfB46QcHZ1U by domi@donotsta.re
0 likes, 0 repeats
@lkundrak no
(DIR) Post #B49WH6IziPPb2TdyGO by nota@chaos.social
0 likes, 0 repeats
@domi modern nvidia firmware is like 150mb or something and you need a few of those D:
(DIR) Post #B49WH6SZ8p4HWA7cBM by domi@donotsta.re
0 likes, 0 repeats
@nota it’s intel
(DIR) Post #B49e4WjuvBmktMkgNs by dakkar@s.thenautilus.net
0 likes, 0 repeats
@domi@donotsta.re firmware? my kernel (with initrd inside) is 26MB, but /etc/firmware/ is 1.7GB…
(DIR) Post #B49e4X7JWCV63vhMqu by domi@donotsta.re
0 likes, 0 repeats
@dakkar you mean /lib/firmware/ ? :)initrd shouldn’t include all of it. preferably it should include none because all it has to do is mounting the rootfs…
(DIR) Post #B49eC5IUppWU68WuG0 by nota@chaos.social
0 likes, 0 repeats
@domi it's still in everyone's initrds I think? in case you plug in an nvidia gpu. Or did they do some workaround for that. I remember there being some discussions
(DIR) Post #B49eC5S4GFBAZp0YAy by domi@donotsta.re
0 likes, 0 repeats
@nota it’s not! it only gets bundled if you install the nvidia packages, which use DKMS to add itself to initrd post-factum
(DIR) Post #B49eUC3mQk1CHhHVjM by dakkar@s.thenautilus.net
0 likes, 0 repeats
@domi@donotsta.re yes, thatsometimes firmware may be needed to mount rootfs (over NFS, for example), so very generic kernels may need access to it from the initrd
(DIR) Post #B49eUCDLr9fslNl9eK by dakkar@s.thenautilus.net
1 likes, 0 repeats
@domi@donotsta.re to be clear: I agree that ½GB of initrd is ridiculous, I'm trying to come up with not-completely-bad reasons for making one