Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
On Thu, Sep 15, 2011 at 4:03 PM, Joost Roeleveld <span dir="ltr"><<a href="mailto:joost@...">joost@...</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Thursday, September 15, 2011 09:27:06 AM Zac Medico wrote:<br>> It should be similar to how sys-apps/v86d is used for uvesafb support.<br>
> It installs /usr/share/v86d/initramfs and when you configure your<br>
> kernel, you set CONFIG_INITRAMFS_SOURCE="/usr/share/v86d/initramfs" in<br>
> order to have in included in your kernel image.<br>
<br>
</div>Will this be set somewhere globally to the initramfs automatically?<br>
And doesn't this mean that a new kernel will need to be build just to satisfy<br>
this?<br>
<br>
I'm trying to think of how best to avoid users who are not aware to get caught<br>
with non-booting systems.<br>
<br>
Wouldn't automatic inclusion into grub.conf be a better approach? Not sure if<br>
grub.conf can handle a "global" setting for initramfs.<br>
<div class="im"><br></div></blockquote><div><br></div><div>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. </div>
<div><br></div><div>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.</div>
<div><br></div><div>I think something like this is best handled via news.</div><div><br></div><div>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.</div>
<div><br></div><div>Rich</div></div>
|
|
