There is no /etc/lilo.conf.
It may be relevant that I have installed the new lilo - I installed it from source using the QuickInst script, but then I tried with the package from current. The lilo in the 13.37 repos has a bug that stops it working with some more recent kernels (including the Current kernel), and as this is likely to be increasingly problematic, I wonder if there is a case for upgrading lilo in 13.37 and earlier?
Here is the log when I revert to the old lilo;
Code: Select all
vanilla[log]$ cat lilosetup.log
LILO version 22.8, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 19-Feb-2007 and compiled at 14:44:48 on Feb 16 2010
Reading boot sector from /dev/sda
Using BITMAP secondary loader
Calling map_insert_data
Mapping bitmap file /boot/salix.bmp -> slack.bmp
Calling map_insert_file
Boot image: /boot/vmlinuz-huge-smp-3.2.23-smp
Fatal: Setup length exceeds 31 maximum; kernel setup will overwrite boot loader
Code: Select all
root[vanilla]# spkg -u lilo-23.2-i486-1.txz
root[vanilla]# lilosetup.py
root[vanilla]# cat /var/log/lilosetup.log
LILO version 23.2 (released 09-Apr-2011)
* Copyright (C) 1992-1998 Werner Almesberger (until v20)
* Copyright (C) 1999-2007 John Coffman (until v22)
* Copyright (C) 2009-2011 Joachim Wiedorn (since v23)
This program comes with ABSOLUTELY NO WARRANTY. This is free software
distributed under the BSD License (3-clause). Details can be found in
the file COPYING, which is distributed with this software.
Compiled at 19:26:55 on Aug 11 2011
Reading boot sector from /dev/sda
Using BITMAP secondary loader
Calling map_insert_data
Mapping bitmap file /boot/salix.bmp
Fatal: open /boot/salix.bmp: No such file or directory