The problem is that when you run lilo from -current, with the following lines for your Slackware-14 boot...
Code:
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda6
label = SlackStable
read-only
# Linux bootable partition config ends
... it maps your -current /boot/vmlinuz as the boot kernel for Slackware 14.
If you want -current to manage the MBR then you have two choices:
1. Mount the slackware-14 kernel so it is visible from -current, then change lilo.conf to use it for the Slackware-14 boot stanza
2. Create a lilo.conf within Slackware-14 to install lilo to its own partition, then chain boot that from -current
The first one might be done like this (provide your own paths)
Code:
mount /dev/sda6 /mnt/slack14
lilo.conf:
# Linux bootable partition config begins
image = /mnt/slack14/boot/vmlinuz
root = /dev/sda6
label = SlackStable
read-only
# Linux bootable partition config ends
For the second option to chain boot Slackware-14, in your Slackware-14 lilo.conf set the following:
Code:
boot = /dev/sda6
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda6
label = SlackStable
read-only
# Linux bootable partition config ends
...then run lilo from Slackware 14, and in your -current lilo.conf change Slackware-14 stanza to:
Code:
# Linux bootable partition config begins
other = /dev/sda6
label = SlackStable
...then run lilo from -current
[EDIT]
I always prefer the chain boot methods for my own systems.
That way, there is never any confusion about which OS instance owns the MBR, and no requirement to mount other boot partitions when I run lilo.
[/EDIT]