SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Yes - you are booted into Debians filesystem with the Slackware kernel.
It is easy to put back as it was - but you must do it exactly and carefully...
FIRST you must mount the Slackware partition while in your confused boot, create a mount point like slackmnt/ for example, then ...
mount /dev/hda8 slackmnt/
SECOND you must 'chroot' into THAT filesystem...
chroot slackmnt/
THIRD - VERIFY, VERIFY, VERIFY that you are in fact on the slack filesystem - look at some file that only exists there or something...
FOURTH - Edit lilo.conf and change the root=/dev/hda9 BACK to root=/dev/hda8 and run lilo again - this will reinstall the bootloader just as it was before...
FIFTH - Reboot and verify that you are back as it was - then make no more changes until we have a plan...
In the even that you have problems with chroot or running lilo from that location, please just be patient or you might end up with a system that does not boot at all...
This is from my lilo.conf, with lilo in the MBR, and Ubuntu's Grub in its root. Obviously the third distro and partition numbers are different, but it may give you some idea of how lilo.conf should look:
Code:
# Windows bootable partition config begins
other = /dev/sda1
label = Windows
table = /dev/sda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-smp-2.6.24.5-smp
initrd = /boot/initrd.gz
root = /dev/sda2
label = Slackware_G
read-only
image = /boot/vmlinuz
root = /dev/sda2
label = Slackware_H
read-only
# Linux bootable partition config ends
other = /dev/sda5
label = Ubuntu
I know how to fix it now. When i login, i installed lilo in the debian system, after that, use liloconfig to configure it, therefor, liloconfig will add my debian and windows entrance to lilo.conf. Ok, i just mount my slack partition and follow astrogeek's guideline to add a entry for slackware, all the things work well now.
but, i get delete the map line, otherwise there would be an error which says 'Syntax error at or above line 75 in file "/etc/lilo.conf"。so, i simply delete the map line, then it can work, but gets a warning like 'The boot sector and the map file have *NOT* been altered', i installed it, and it can lead me to my debian and slackware well. Then i login my slackware and installed lilo again, all the things were then same.
my debian entrance like:
image = /mnt/hd/debian/boot/vmlinuz
root = /dev/hda9
initrd = /mnt/hd/debian/boot/initrd.img
#map = /mnt/hd/debian/boot/coffee.bmp
label = Debian
read-only
*: I had copy a new file with a short filename from the old ones.
Why?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.