I've run Debian on my laptop for quite some time now with no problems.
I installed Slack to a new partition
created in the free space of my hard drive, and I thik this was my mistake: I let Slack automatically configure the MBR with lilo
(can't remember - I should stop operating on the MBR at 4 AM.) Now Slack runs just fine, but upon bootup I would like to be able to boot either Debian or Slack
, but instead I just have a Slack splash and the only option is to press enter to boot Slack.
root@slacjb400:~# lilo -A /dev/sda
I believe sda1 is the root directory of my Debian install.
root@slacjb400:~# fdisk -l
Device Boot Start End Blocks Id System
/dev/sda1 * 1 43 345366 83 Linux
/dev/sda2 44 14962 119836867+ 5 Extended
/dev/sda3 14963 22432 60002775 83 Linux
/dev/sda5 44 651 4883728+ 83 Linux
/dev/sda6 652 1016 2931831 83 Linux
/dev/sda7 1017 2460 11598898+ 82 Linux swap
/dev/sda8 2461 2509 393561 83 Linux
/dev/sda9 2510 13518 88429761 83 Linux
/dev/sda10 13519 14962 11598898+ 82 Linux swap
In the above table, sda10 is the swap I created for Slack and sda3 is the root directory for Slack. All other partitions were there before (my initial Debian install).
Thus my partitions are apparently intact and visible by the MBR
(is it correct that the MBR holds the list of partitions on a disk?) but for some reason I don't have the option to boot Debian at all - just Slack.
I have a feeling this is a LILO/GRUB issue, but I don't know where to start.
EDIT: more poking around seems to reveal that it is the configuration of LILO that is the problem. Observe the following output:
root@slacjb400:~# cat /etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
# Start LILO global section
# Append any additional kernel parameters:
boot = /dev/sda
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda3
label = Linux
# Linux bootable partition config ends