[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: for ppc, include all modules in the core image

From: Vladimir 'φ-coder/phcoder' Serbinenko
Subject: Re: for ppc, include all modules in the core image
Date: Mon, 22 Oct 2012 19:53:17 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.9) Gecko/20121014 Icedove/10.0.9

On 22.10.2012 19:30, Paulo Flabiano Smorigo/Brazil/IBM wrote:

> Quoting Vladimir 'φ-coder/phcoder' Serbinenko <address@hidden>:
>> On 16.10.2012 12:28, Paulo Flabiano Smorigo/Brazil/IBM wrote:
>>> Hi all!
>>> This patch implements the solution suggested by Gustavo Luiz Duarte
>>> <address@hidden>:
>>> Adding more modules to be built-in to the grub core ELF is easy. It is a
>>> parameter passed by grub2-install to grub2-mkimage. However, there is a
>>> downside
>>> on adding many modules to the core ELF: they are fully initialized in
>>> the grub's
>>> first stage. It means you could hit a bug on a module you don't need and
>>> end up
>>> with a non-bootable system.
>>> Another downside is that you wouldn't get updates for these built-in
>>> modules, as
>>> updating the grub2 package only updates the modules residing in /boot
>>> and not
>>> the grub core ELF in the PReP partition.
>>> A proper solution would be to add to grub the ability of having built-in
>>> *inactive* modules which would be loaded and initialized only on demand
>>> (i.e.
>>> explicitly calling the insmod command).
>> This is what memdisk does (i.a.). Why do you need anything else?
>>> _______________________________________________
>>> Grub-devel mailing list
>>> address@hidden
>> -- 
>> Regards
>> Vladimir 'φ-coder/phcoder' Serbinenko
> Hi phcoder,
> Thanks for the reply. I studied memdisk and tried to use grub-mkstandalone
> but the idea used in this patch is different. It's like a plan B just in
> case /boot isn't found. It gives the "grub rescue" a new level of recovery,
> increasing the chances to fix the system. This extra modules is stored in a
> different area and will *only* be used in this case.
> Otherwise, the normal modules, inside /boot, will be used normally and If
> there is an update or if grub.cfg changes, the new files will be used.

Can't you attain the same result with memdisk but not pointing root to it?
This part is size-critical and we need a good reason to put new features.

> Best regards,

Vladimir 'φ-coder/phcoder' Serbinenko

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]