On Thursday, September 15, 2011 03:56:19 PM William Hubbs wrote:
> On Thu, Sep 15, 2011 at 09:27:06AM -0700, Zac Medico wrote:
> > On 09/15/2011 09:04 AM, Joost Roeleveld wrote:
> > > Thank you for your response, however, I do have a few questions
> > > about this. Where will this default initramfs actually need to be
> > > placed?
> > 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.
> Actually, we are looking at installing the initramfs image directly in
> /boot, then you will have to configure your boot loader to use it.
This, to me, seems like the obvious solution.
However, to make the change as unobtrusive as possible for the majority of
users. Wouldn't it be possible to have grub support a "default initrd" in the
grub.conf and use that unless the grub-entry specifies it's own?
This is just an idea that I have. Not sure how much work this would bring.
It would still not catch the situation on my server where the kernel is passed
with the same mechanism to the xen-hypervisor and as such, the "defeault
initrd" would then be ignored. But on my desktop, this would work