Kudzo could detect a fact that the installer doesn't: one
processor in a multi capable box. Running with one cpu and
the SMP kernel is very bad for context switch delays. Kudzo
seems like the perfect animal for the job. All it would
have to do is look at /proc/cpuinfo, then see if lilo.conf
is unchanged. If it hasn't changed, and it contains a
linux-up label, make default=linux-up, then run lilo. Is
this practical for kudzo to do? It would help out all who
only have one CPU in a multi CPU box.
This won't happen at least until DMI probing is included.
Things are as they should be now... thank you.