mimosa wrote:I should make clear (in case it's not) that this wasn't caused by *running* the 3.2 kernel. I booted the machine with 2.6.x, upgraded the kernel packages, and ran lilo, still while running the standard Salix 13.37 kernel I had booted with.
The problem is not caused by the current kernel under whose supervision lilo runs. The problem is when the kernel version, which should be booted with lilo is too new. The version of lilo in 13.37 just can't cope with newer versions.
mimosa wrote: It then seems relevant to consider how frequently it comes up - and maybe this one isn't common enough to merit special treatment. However, lilo is a small package and 23.2 seems to have fixed it.
Lilo works fine with the kernel in 13.37 and actually older versions too. So why should we upgrade it? It just has the potential to introduce new bugs.
The only reason to upgrade it is for a newer kernel. But a newer kernel definitely won't come for 13.37, because there are much too many regressions it could introduce.
Actually I bet there a dozens of issues like this in 13.37 and they've existed in the past releases and will also exist in the future ones. Unless they're serious like security issues or completely unusable software, they are not usually fixed. Even more not for core system components with unclear, wide and often unexpected reach like kernel, bootloader or similar.
It's fine that it fixes your problem. But can you definitely tell, there's no way new problems are caused, which didn't exist previously?
Sorry, but this is stuff that is usually fixed with a completely new release. Where it's possible to test it for a longer period of time. More so, this makes it possible to revert to an older working release, which is not anymore possible if we break that one too.