On Thu, Sep 15, 2011 at 4:03 PM, Joost Roeleveld <jo...@antarean.org> wrote:
> On Thursday, September 15, 2011 09:27:06 AM Zac Medico wrote: > > It should be similar to how sys-apps/v86d is used for uvesafb support. > > It installs /usr/share/v86d/initramfs and when you configure your > > kernel, you set CONFIG_INITRAMFS_SOURCE="/usr/share/v86d/initramfs" in > > order to have in included in your kernel image. > > Will this be set somewhere globally to the initramfs automatically? > And doesn't this mean that a new kernel will need to be build just to > satisfy > this? > > I'm trying to think of how best to avoid users who are not aware to get > caught > with non-booting systems. > > Wouldn't automatic inclusion into grub.conf be a better approach? Not sure > if > grub.conf can handle a "global" setting for initramfs. > > Well, the only way to set a kernel config parameter is to rebuild the kernel. There might be some way to extract the built-in initramfs (every kernel has one) and replace it with the new one without rebuilding it, but I doubt most users would prefer that we mount /boot and start modifying their kernel images. Changes to grub.conf will only be properly merged if /boot is mounted, if grub is installed (don't laugh - I checked and since my system was migrated so many times I don't actually have the package installed any longer), and the user actually merges the changes in. Fiddling with grub.conf isn't exactly risk-free either. I think something like this is best handled via news. Note also that depending on your definition of "broken" the separate /usr situation is already broken. It will probably steadily become more broken over time, so when it stops booting altogether for any particular user might happen anytime from a year ago to never. Rich
