https://bugzilla.novell.com/show_bug.cgi?id=447218 User aj@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=447218#c1 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |mrmazda@ij.net --- Comment #1 from Andreas Jaeger <aj@novell.com> 2008-11-25 11:06:19 MST --- Do you know who changes these? I fear we need to file bugs against each single package. If so, please do so. -- 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=447218 Robert Vojcik <rvojcik@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |locilka@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=447218 User aj@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=447218#c4 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |jreidinger@novell.com --- Comment #4 from Andreas Jaeger <aj@novell.com> 2008-12-02 02:48:00 MST --- Felix, please file separate bugs for each problem. Let's handle just the bootloader here... -- 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=447218 User mrmazda@ij.net added comment https://bugzilla.novell.com/show_bug.cgi?id=447218#c6 Felix Miata <mrmazda@ij.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|mrmazda@ij.net | Summary|do not change timestamps on config files not |perl-Bootloader changes menu.lst, saves changed |changed during software updates |file as menu.lst.old, then changes it again --- Comment #6 from Felix Miata <mrmazda@ij.net> 2008-12-02 08:25:25 MST --- (In reply to comment #5 from Josef Reidinger)

Are you sure that menu.lst.old is exactly same? I think at least kernel version should change, not?

I wrote this bug up as a collective problem thinking that a shared process during updating was responsible when in fact menu.lst seems quite a separate case from the others. The original menu.lst never gets backed up. Menu.lst.old differs from the lastest menu.lst, and also differs from menu.lst as it existed prior to the kernel update. Since AJ wants separate bugs with this for menu.lst, and the behavior of menu.lst changing is different from the other files that I grouped with it, I'm changing summary on this to describe the unique behavior of perl-Bootloader (or whatever might be repeatedly changing menu.lst). perl-Bootloader is NOT saving the original menu.lst as menu.lst.old - at least, not intact. I always backup up my menu.lst as menu.lst.##, and keep them dating back many versions. Never ever has a kernel update resulted in the appearance of any menu.lst.old that matches my latest backup of menu.lst as menu.lst.##. What I do after each update is rename menu.lst.old to the next in the menu.lst.## sequence, copy the newest menu.lst to the next in the menu.lst.## sequence, make my changes to menu.lst, and save that to the next in the menu.lst.## sequence. So, for each kernel update, /boot/grub acquires 3 new menu.lst backups, e.g. menu.lst.2a, menu.lst.2b & menu.lst.2c. So, when perl-Bootloader is left to do its own backing up, there is never actually a backup (menu.lst.old) of menu.lst as it existed immediately prior to the kernel update. Menu.lst.old should either be an actual backup of menu.lst as it existed prior to the kernel update, or should be left behind with some other name that does not imply that it is a backup of something known to have worked before the update. My attachments to bug 447142 show the miserable mess than can happen to menu.lst that result from kernel updates. -- 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=447218 User jreidinger@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=447218#c8 --- Comment #8 from Josef Reidinger <jreidinger@novell.com> 2008-12-15 08:26:16 MST --- I fixed that in svn, and will be in 11.2. Sollution is save backup only if previous backup is more then one hour older. So backup should reflect state before kernel update. Only problematic case is after install, if we use new workflow, then backup after installation is not correct, but if you cannot boot after install, then I hope user doesn't expect working backup of installation. -- 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=447218 User jreidinger@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=447218#c10 --- Comment #10 from Josef Reidinger <jreidinger@novell.com> 2008-12-17 23:59:26 MST --- OK, it sounds reasonable. I change it. -- 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.