https://bugzilla.novell.com/show_bug.cgi?id=308984 Bernhard Walle changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |fehr@novell.com Version|Beta 2 |Beta 3 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=308984#c2 Thomas Fehr changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fehr@novell.com Status|NEEDINFO |NEW Info Provider|fehr@novell.com | --- Comment #2 from Thomas Fehr 2007-09-10 07:14:09 MST --- fstab conversion is done at end of update to be sure to have the new packages available. So when kernel gets installed the rename withing fstab does not have happened. Therefore the above error message of mkinitrd is to be expected when mkinitrd gets called in inst-sys. Does calling mkinitrd in post script from inst-sys really make sense, AFAIK mkinitrd is again called later during bootloader setup anyway. Please attach full y2log files, so we can see what is going on. But the problem that currently mkinitrd is called while fstab is not yet updated needs certainly to be addressed. Would it not be the easiest to suppress this call from %post script during update. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=308984 Bernhard Walle changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=308984 Bernhard Walle changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jblunck@novell.com Status|ASSIGNED |NEEDINFO Info Provider| |agruen@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=308984#c6 --- Comment #6 from Stephan Kulow 2007-09-11 03:34:21 MST --- That doesn't sound like blocker quality then -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=308984#c7 --- Comment #7 from Jan Blunck 2007-09-11 05:59:17 MST --- Does it actually make any sense to update the boot-loader when mkinitrd hasn't run yet? Otherwise we could just fall back to not doing anything ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=308984#c9 Bernhard Walle changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|agruen@novell.com | Resolution| |FIXED --- Comment #9 from Bernhard Walle 2007-09-11 08:27:35 MST --- Ok, according to the off-line feedback of Jan, I applied this one. ------------------------------------------------------------------- Tue Sep 11 16:22:16 CEST 2007 - bwalle@suse.de - rpm/post.sh: Don't run mkinitrd during installation (308984) ------------------------------------------------------------------- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.