| |||||||||||||
initramfs and where user space truly beginsinitramfs and where user space truly beginsPosted Jul 13, 2006 16:25 UTC (Thu) by nix (subscriber, #2304)In reply to: initramfs and where user space truly begins by dlang Parent article: initramfs and where user space truly begins
There's no need to do that, unless by 'prepare' you mean 'tell the kernel build infrastructure which files should go into initramfs'. I can see no way to automate *that* without eliminating all the configurability (of course there should be a default that uses kinit if kinit becomes mandatory, and the kinit patches do indeed provide such a default).
(Log in to post comments)
initramfs and where user space truly begins Posted Jul 13, 2006 16:40 UTC (Thu) by dlang (✭ supporter ✭, #313) [Link] any portions that the kernel requires (kinit for example) need to be pulled in automagicly.
this could be as simple as having a directory under the source three /initramfs such that anything that's in there gets used to create the initramfs (and the kernel compiles kinit and any other required pieces and puts them in there)
or any other method of makeing a default initramfs that provides hooks so that the distros can add their own stuff in.
the point I'm looking for is that today you can make a monolithic kernel by make *config && make and then use the resulting file on any compatable machine and it's sufficiant to boot the machine. if initramfs is made mandatory then it needs to be equally simple to manage.
initramfs and where user space truly begins Posted Jul 14, 2006 11:55 UTC (Fri) by nix (subscriber, #2304) [Link] It already is: there is a default initramfs source file which contains everything needed for kinit; you can add stuff to it as you wish.
|
|||||||||||||