On 10/22/2012 03:18 PM, Felix Miata wrote:
On 2012-10-22 21:19 (GMT+0200) Andreas Jaeger composed:
Felix Miata wrote:
I just did a zypper up on a 12.2 system last updated 29 Aug, with kernel-desktop locked. Package count was 142. Afterward I unlocked kernel-desktop, then did zypper dup. I monitored the up process, creating initrd backups every time new initrd creation appeared onscreen. The following is the result:
-rw-r--r-- 1 root root 5207254 Jun 30 16:55 i0nitrd-3.4.2-1-desktop1 -rw-r--r-- 1 root root 5272345 Aug 29 11:56 i0nitrd-3.4.2-1-desktop2 -rw-r--r-- 1 root root 5275931 Oct 22 11:38 i0nitrd-3.4.2-1-desktop3 -rw-r--r-- 1 root root 5275985 Oct 22 11:42 i0nitrd-3.4.2-1-desktop4 -rw-r--r-- 1 root root 5275953 Oct 22 11:43 i0nitrd-3.4.2-1-desktop5 -rw-r--r-- 1 root root 5275956 Oct 22 11:50 i0nitrd-3.4.2-1-desktop6 -rw-r--r-- 1 root root 5272072 Aug 29 12:50 i0nitrd-3.4.6-1.1-desktop1 -rw-r--r-- 1 root root 5276071 Oct 22 11:38 i0nitrd-3.4.6-1.1-desktop2 -rw-r--r-- 1 root root 5276013 Oct 22 11:41 i0nitrd-3.4.6-1.1-desktop3 -rw-r--r-- 1 root root 5276025 Oct 22 11:44 i0nitrd-3.4.6-1.1-desktop4 -rw-r--r-- 1 root root 5276074 Oct 22 11:51 i0nitrd-3.4.6-1.1-desktop5 lrwxrwxrwx 1 root root 26 Oct 22 11:56 initrd -> initrd-3.4.11-2.16-desktop -rw-r--r-- 1 root root 5276261 Oct 22 11:56 initrd-3.4.11-2.16-desktop -rw-r--r-- 1 root root 5275956 Oct 22 11:50 initrd-3.4.2-1-desktop -rw-r--r-- 1 root root 5276074 Oct 22 11:51 initrd-3.4.6-1.1-desktop lrwxrwxrwx 1 root root 24 Aug 29 12:50 initrd-curr -> initrd-3.4.6-1.1-desktop lrwxrwxrwx 1 root root 22 Jun 30 16:55 initrd-prev -> initrd-3.4.2-1-desktop
On slow systems this really extends the update process noticeably. Could it be streamlined so that initrds only get built a maximum of once per up/dup run?
We might need transaction support and merging of those in rpm. But let's first figure out *why* those are updated. Could you check your /var/log/zypp logfiles to see which packages triggered those? Perhaps some of the triggers could be changed.
If I'm reading http://fm.no-ip.com/Tmp/SUSE/zypphistory-s122-d5000.txt correctly:
# 2012-10-22 11:36:15 mkinitrd-2.7.1-62.6.1.i586.rpm installed ok # 2012-10-22 11:38:38 udev-182-4.21.1.i586.rpm installed ok # 2012-10-22 11:41:12 mdadm-3.2.5-3.17.1.i586.rpm installed ok # 2012-10-22 11:44:05 lvm2-2.02.84-26.8.2.i586.rpm installed ok # 2012-10-22 11:51:08 multipath-tools-0.4.9-3.6.1.i586.rpm installed ok
# 2012-10-22 11:57:00 kernel-desktop-3.4.11-2.16.1.i686.rpm installed ok
Looks like I missed backing up the first that followed mkinitrd. Seems like if mkinitrd is in the list, all that use it should have theirs skipped, and mkinitrd's scripts, if not the whole package, deferred until last.
Note that all partitions on this single HD (laptop) system are traditional types, and natives are all swap, EXT2 or EXT3.
I usually have a number of kernels in directory /boot. At present, there are 28 such entries. Under those conditions, the mkinitrd step takes about an hour to run. I did an update with apper last night, and it took about 3 hours to install the new packages. My suggestion is that a special flag be made available, and that the flag be set by any package that needs new initrd files. When all the packages have been installed, then call mkinitrd if the flag is set. Larry -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org