Hello community, here is the log from the commit of package mkinitrd for openSUSE:Factory checked in at 2013-09-13 14:43:51 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/mkinitrd (Old) and /work/SRC/openSUSE:Factory/.mkinitrd.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "mkinitrd" Changes: -------- --- /work/SRC/openSUSE:Factory/mkinitrd/mkinitrd.changes 2013-09-04 13:59:50.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.mkinitrd.new/mkinitrd.changes 2013-09-13 14:43:52.000000000 +0200 @@ -1,0 +2,12 @@ +Thu Sep 12 01:02:49 UTC 2013 - [email protected] + +- Two improvements for md + 1/ Don't install the udev rules file 64-md-raid.rules. + It has been renamed to 2 different files, and the mdadm + package installs it now. + 2/ Run "mdadm -IRs" at half-time when waiting for the root + device to appear. + This will start any newly-degraded array (weren't degraded + when machine was shut down). + +------------------------------------------------------------------- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ mkinitrd.tar.bz2 ++++++ diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/mkinitrd-2.7.2/scripts/boot-devfunctions.sh new/mkinitrd-2.7.2/scripts/boot-devfunctions.sh --- old/mkinitrd-2.7.2/scripts/boot-devfunctions.sh 2013-09-03 10:39:47.000000000 +0200 +++ new/mkinitrd-2.7.2/scripts/boot-devfunctions.sh 2013-09-12 11:50:11.000000000 +0200 @@ -67,6 +67,7 @@ fi if [ -n "$root" ]; then echo -n "Waiting for device $root to appear: " + let halftime=$timeout/2 while [ $timeout -gt 0 ]; do if [ -e "$root" ]; then udev_devn=$(devnumber $root) @@ -101,6 +102,10 @@ usleep 25000 ((timeout % 40 == 1)) && echo -n "." let timeout-- + if [ "$need_mdadm" = "1" -a "$timeout" -eq "$halftime" ] ; then + # time to start any newly-degraded md arrays + mdadm -IRs + fi # Recheck for LVM volumes if [ -n "$vg_root" -a -n "$vg_roots" ] ; then vgscan diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/mkinitrd-2.7.2/scripts/setup-modules.sh new/mkinitrd-2.7.2/scripts/setup-modules.sh --- old/mkinitrd-2.7.2/scripts/setup-modules.sh 2013-09-03 10:39:47.000000000 +0200 +++ new/mkinitrd-2.7.2/scripts/setup-modules.sh 2013-09-12 11:50:11.000000000 +0200 @@ -55,14 +55,12 @@ # the kernel and then just loads the kernel module, we can safely include # such modules on such systems in initrd. # -# The check is done by checking if 'ipv6.ko' is supported. Since we -# have to supported ipv6 for a very long period of time from now because -# it's our standard file system, and that module exists on every -# architecture and does not depend on the hardware and even exists in -# the base package of the kernel because we need it in a virtualised -# environment, that module is suitable for that check. I didn't know any -# better method of checking if the kernel is supported so I implemented -# that hack. Better than nothing. :-) +# The check is done by checking if 'loop.ko' is supported. Since we have +# supported loop for a very long period of time, and that module exists on +# every architecture and does not depend on the hardware, that module is +# suitable for that check. I didn't know any better method of checking if +# the kernel is supported so I implemented that hack. Better than nothing. +# :-) # # Parameters # kernelver: the kernel version diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/mkinitrd-2.7.2/scripts/setup-udev.sh new/mkinitrd-2.7.2/scripts/setup-udev.sh --- old/mkinitrd-2.7.2/scripts/setup-udev.sh 2013-09-03 10:39:47.000000000 +0200 +++ new/mkinitrd-2.7.2/scripts/setup-udev.sh 2013-09-12 11:50:11.000000000 +0200 @@ -78,7 +78,6 @@ 61-msft.rules \ 62-dm_linear.rules \ 64-device-mapper.rules \ - 64-md-raid.rules \ 79-kms.rules \ 80-drivers.rules; do if [ -f /usr/lib/udev/rules.d/$rule ]; then -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
