[opensuse-kernel] Multiple mkinitrd's run during dup - why?
![](https://seccdn.libravatar.org/avatar/c4d991702dcb0afa2b2afd8464be7f66.jpg?s=120&d=mm&r=g)
It's not the first time I've noticed this, but during my zypper dup today my system ran mkinitrd at least twice Once as part of installing kernel-default (in the %post install of that package) and once again as part of installing coreutils (in the %posttrans, using the %{?regenerate_initrd_posttrans} macro) If I understand correctly the whole point of the %{?regenerate_initrd_posttrans} macro is to prevent multiple runs of mkinitrd necessarily - so I guess my question is - why isn't the kernel using it? And would it be a good idea to consider it? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 2018-06-15 21:28, Richard Brown wrote:
It's not the first time I've noticed this, but during my zypper dup today my system ran mkinitrd at least twice
Once as part of installing kernel-default (in the %post install of that package) and once again as part of installing coreutils (in the %posttrans, using the %{?regenerate_initrd_posttrans} macro)
If I understand correctly the whole point of the %{?regenerate_initrd_posttrans} macro is to prevent multiple runs of mkinitrd necessarily - so I guess my question is - why isn't the kernel using it?
And would it be a good idea to consider it?
I read somewhere that it was intentional. Install a kernel, run that thing then and there, perhaps so that if there is a crash the kernel works. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
participants (2)
-
Carlos E. R.
-
Richard Brown