Per Jessen wrote:
Joachim Schrod wrote:
Per Jessen wrote:
I'm old (fashioned), I've never let YaST do anything to my lilo.conf except for the initial install. I've also rarely had reason to change anything in lilo.conf once I've put a server or a desktop PC into production.
I have kernel rpms set to multiple installations, to be able to boot an old kernel again if any problem surfaces. This rescued my a** several times already. To support this, lilo.conf -- or grub/menu.lst, for that matter -- has an entry for generic "boot the current linux system", but also entries for each specific kernel that gets installed. And the latter entries must be updated for every kernel install. It's not a big issue, but for grub it is done automatically, and for lilo that's not the case.
But isn't that a problem because of lack of lilo support in YaST, not a lilo problem as such?
I don't think that's a YaST issue. (I don't use YaST for software installation or updates.) That's a matter of post-installation actions, probably some SuSEconfig script got bit-rot that did the lilo.conf editing once upon a time and now was not updated any more. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org