Mailinglist Archive: opensuse-factory (266 mails)

< Previous Next >
Re: [opensuse-factory] Re: initrd -> initramfs
On Wed, 6 May 2020 13:17:28 +0200
Ludwig Nussel <ludwig.nussel@xxxxxxx> wrote:

Am 06.05.20 um 11:57 schrieb Andreas Schwab:
On Mai 06 2020, Ludwig Nussel wrote:

One could also see initrd, initramfs or whatever it's called, what
format it has or even where it is placed an implementation detail of
dracut or whatever tool is used to make the system bootable.
From that angle it wouldn't be the kernel package's duty to own the
file. So whatever creates the initrd has to also clean it up when no
longer required.

The problem is that the initrd generation is triggered by the kernel
package, not dracut. Only the kernel knows the exact name of the initrd
(which includes the kernel's %version and %release). All other places
where initrds are regenerated just iterate over all existing kernel
images in /boot (*including* any manually installed kernels).

Sure. The existing pre/post scripts of the kernel already pass that
information to other scripts eg for bootloader or weak modules updates.
Are they?
weak-updates do not need initrd name if it's hardcoded in dracut
bootloader just randomly searches for something that looks like ramdisk
and has same version suffix as the kernel.

Thanks

Michal
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >