Re:Booting embedded Linux in 0.37 seconds on an ARMv7-A CPU ...
by dvdkhlng on Thursday June 18, 2020 @03:09AM
(#23560551)
Slight correction: by default Debian/Ubuntu put all modules potentially required for initial boot into the initramfs. That's still a very small percentage of all modules. I.e. you only need those modules that will get you so far into the boot process that you have access to the root partition with all the remaining modules.
E.g. if you want to do network-boot over wifi, you'll have to add a initramfs-hook script to add the wifi modules for your hardware into the initramfs [1]. They are not included by default.
[1] http://www.marcfargas.com/posts/enable-wireless-debian-initr...
Re:Booting embedded Linux in 0.37 seconds on an ARMv7-A CPU ...
by Twirrim on Thursday June 18, 2020 @11:43AM
(#23564133)
You're right, I misinterpreted what "most" meant in the mkinitramfs config. Interesting. I've not seen any difficulties with porting Ubuntu between different hardware configurations, so it seems to include a reasonable amount of them.
Every now and then I'm tempted to try "dep" instead of "most", but then I realise there just isn't enough benefit!
Re:Booting embedded Linux in 0.37 seconds on an ARMv7-A CPU ...
by ndesaulniers on Thursday June 18, 2020 @06:45PM
(#23568984)
Is there a way to specify when running mkinitramfs whether kernel modules are stored there or not?
Which is also somewhat annoying because it completely trashes portability, which can be really irritating in cloud environments.
Ubuntu has similar capability (and I'm guessing Debian upstream?), but you have to specifically enable it, by default it ships the full modules set in the initramfs.
I would imagine most places outside of embedded world and maybe microvms, this stuff isn't that valuable.