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.
There must be something wrong in the lilo.conf. Could you please cpy it and write which partition is used by which system (especially, which one is used with Slack)?
It looks you boot Mandrake kernel telling it to use Slack's partition... You need to mount the Slack partiton in Mandrake:
mkdir /mnt/slack
mount /dec/hda7 /mnt/slack
then edit the slack part of lilo.conf:
Note that you need to check if vmlinuz is the right name for your kernel in Slack and get the right name of Slack's initrd. When it's done, save lilo.conf and run 'lilo'. Slack should be able to boot now.
ok just installed slack and made a custom lilo install and it workes great!
now i need to know if the mandrake part is correct before i try and boot mandrake. this is where i am a bit confused.
very nice!! worked great! i guess mara thought i knew what i was doing...lol
can i use this to add anything else? i am about to install knoppix 3.3 do a knx-hdinstall and add these lines to my lilo.conf.
label = "knoppix" (can i put 3.3...coz i have 3.2 as well)
image = /mnt/knx/boot/vmlinblahblah
initrd = /mnt/knx/boot/if_it_has_one.img
root = /dev/hda8
then run /sbin/lilo -v. i will have mounted /dev/hda8 and created the dir /mnt/knx.
yup. looks right. And you can add any number of distros this way. Just make sure that all the root partiton of all the distros mentioned in lilo.conf are mounted at the appropriate places when you run lilo. Taht is, you will also need to mount /dev/hda7 to /mnt/mdk in this case.
btw, I'm pretty sure knoppix does not have a initrd - there is a file named initrd.gz or something like that in its boot directory but ignore it.
reiserfs was the outright no doubt problem. i know this because i reinstalled knoppix using a different fs and guess what? i did not even have to edit the lilo.conf again. i rebooted and went straight to knoppix hit enter and BOOM there it is.
Last edited by DooFDooF_music_; 10-12-2003 at 10:40 PM.
the reason is that the filesystem of the root partition must be supported by the kernel (compiled into it) and the knoppix kernel probably doesn't have reiserFS support compiled in.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.