[opensuse-factory] initrd generation during RPM install
I thought we have deferred initrd generation to posttrans. I just updated TW and initrd was regenerated 4 times - after kernel-default - after virtualbox kmp - after udev - after all packages have been installed Does it work as intended or something is missing? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 08/16/2016 02:56 AM, Andrei Borzenkov wrote:
I thought we have deferred initrd generation to posttrans. I just updated TW and initrd was regenerated 4 times
- after kernel-default - after virtualbox kmp - after udev - after all packages have been installed
Does it work as intended or something is missing?
+1 -- Ken linux since 1994 S.u.S.E./openSUSE since 1996 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On mardi, 16 août 2016 08.41:19 h CEST Ken Schneider wrote:
On 08/16/2016 02:56 AM, Andrei Borzenkov wrote:
I thought we have deferred initrd generation to posttrans. I just updated TW and initrd was regenerated 4 times
- after kernel-default - after virtualbox kmp - after udev - after all packages have been installed
Does it work as intended or something is missing?
+1
What I've seen is this behaviour, initrd rebuild at the end. But I'm using the forced DownloadInAdvance mode of zypper. Now I should try to reinstall completely a TW from scratch to see how much time initrd is builded. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-08-16 08:56, Andrei Borzenkov wrote:
I thought we have deferred initrd generation to posttrans. I just updated TW and initrd was regenerated 4 times
- after kernel-default
This is intended, so that there is an initrd right after the kernel has been updated.
- after virtualbox kmp - after udev - after all packages have been installed
These should be deferred to posttrans, because in case of a failed install, there will already be a working initrd with the previous version of the tools. Also, the packages regenerated the initrd for all kernels, which takes long. Please submit bugreports with y2logs. Michal -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 19.08.2016 um 12:45 schrieb Michal Marek:
- after kernel-default This is intended, so that there is an initrd right after the kernel has been updated.
Once zypper dup starts to install the first package the system is in an inconsistant state, and it remains in that inconsistant state until the very last %posttrans is finished. There is little point in running mkinitrd more than once during the whole transaction. Olaf
On 08/19/2016, 02:18 PM, Olaf Hering wrote:
Am 19.08.2016 um 12:45 schrieb Michal Marek:
- after kernel-default This is intended, so that there is an initrd right after the kernel has been updated.
Once zypper dup starts to install the first package the system is in an inconsistant state, and it remains in that inconsistant state until the very last %posttrans is finished. There is little point in running mkinitrd more than once during the whole transaction.
Except the kernel would be installed very first. Can we do it? -- js suse labs
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dne 19.8.2016 v 16:09 Jiri Slaby napsal(a):
On 08/19/2016, 02:18 PM, Olaf Hering wrote:
Am 19.08.2016 um 12:45 schrieb Michal Marek:
- after kernel-default This is intended, so that there is an initrd right after the kernel has been updated.
Once zypper dup starts to install the first package the system is in an inconsistant state, and it remains in that inconsistant state until the very last %posttrans is finished. There is little point in running mkinitrd more than once during the whole transaction.
There are different levels of inconsistent, though. With a kernel and initrd, you will be able to at least mount the root filesystem. But I do not insist on doing it this way..
Except the kernel would be installed very first. Can we do it?
I do not understant this..? Michal -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJXtxceAAoJENjHJYQaovOVkoUP/2maYI1K+Yu/RgaqWAGtqLw/ x5K3+FEz0YTNg841/09wRie2XVdNDxHhU72UWnxT9JKZkqsNJEbWbfhoZvNCgoIg zxO0ANYELf5ztBlAyu4Ik2BvaMQO9zvCQjY0ML+cTOoT8uZk7ux1eewBojUwWPeX YYrzp9QXDtaE6O9ZC6wvXYsqiw+SbDK5Hevb9t1MVIFY25vObhG6MjpyPUmJ5Rw/ tZfaiohYe5xCi+J6Xt4R+L/YxTd+G//KBbSg8hAJFMmsWqVTzcv9jTYkc+LAA9jm 2ouhPybY55CtrasWX96pVQPA1g2lGz6pRaAU9fqrgt7CRV2mFt72x39L+DqMPQgU QprJAPLi9xVoUgzhp+vLC402dgQlFeCbC11/NMJivvl1uurx9xRxuTcb68tYwXX6 aYjxqIjUx4hYVgHlc58Zm8EFDKgQ8oryVFYUInKpZ0YfQEptsz6qSRUWKP8tI+QF 3mBdXv9pQEjeRDRSmuJMKlf2gNO8L8sPBfxR3TXCe5H5s1hhjGF/blw91x/uN/Fx VM2lOldLVEE57HgI0pR92B8V6771rfU+KUyfitZmojuiWYKVcr/79GSUw8/3Z73l 7Y9vEgT1p5eHUFG19KB8Ch/Bb+49I1b4LXPZvxHG1CiR3JegNfAlLMkYfg0g+EWJ ilqB3nVDt5gsSBaHnQYp =G7dl -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 19.08.2016 um 16:26 schrieb Michal Marek:
There are different levels of inconsistent, though. With a kernel and initrd, you will be able to at least mount the root filesystem. But I do not insist on doing it this way..
If there is just one place for mkinitrd, in %posttrans, the current kernel+initrd entries are still usable. There are likely ways to check if multiversion is enabled, and defer mkinitrd in this case.
Except the kernel would be installed very first. Can we do it?
This would still call mkinitrd more than once, for little gain. Olaf
participants (6)
-
Andrei Borzenkov -
Bruno Friedmann -
Jiri Slaby -
Ken Schneider -
Michal Marek -
Olaf Hering