On Tuesday 06 July 2004 04:10, Earl A. Killian wrote:
The same thing happened to me after I used YOU to update.
Are we stuck typing ^D on every boot until SuSE fixes something, or is there a work-around?
The presented workaround saves you from this by decativating the fallback shell. SuSE will provide a mkinitrd update soon.
Can you explain the problem any better, because it is really obscure to me.
As it stands, the problem occurs in all 9.1 installations with updated mkinitrd, when starting from lilo (mostly resulting from a md setup). The reason for this is a difference in root argument handling between grub and lilo. grub delivers a four digit root= argument, whereas lilo uses 3 digits only. This isn't correctly handled in initrd and resulted in calling a rescue shell (which was added in a recent mkinitrd update), thus all it takes to fix this problem is this patch: --- /sbin/mkinitrd.suse 2004-07-03 17:59:04.000000000 +0200 +++ /sbin/mkinitrd 2004-07-02 00:24:41.000000000 +0200 @@ -1358,6 +1357,8 @@ | case \$rootdev in | /dev/*) | ;; + | [0-9a-fA-F][0-9a-fA-F][0-9a-fA-F]) + | rootdev=0\$rootdev ;; | [0-9a-fA-F][0-9a-fA-F][0-9a-fA-F][0-9a-fA-F]) | ;; | *:*) Be careful, this sequence contains spaces, at least on send. Invoice will follow. ;-) Cheers, Pete