Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Add another stanza to your lilo.conf, along the lines of
image = /boot/vmlinuz
root = /dev/hda2
label = "Slackware"
image = /mnt/hda1/boot/vmlinuz # or wherever the boot image is.
root = /dev/hda1
label = "Mandrake"
Mount hda1, re-run lilo, and reboot. From the sounds of it, you had Mandrake installed, after which you installed slackware (incidentally, where is your swap partition ?), overwriting the existing lilo setup from Mandrake.
My swap is on /dev/hda5. It might have been easier to install slackware first but I wanted a safety net. I'm not sure about the mnt/hda1/boot/vmlinuz line. Are you saying I need to remount hda1 ? That is where the boot image for mandrake is. My hda set-up is:
hda1 mandrake root
hda2 slackware root
hda6 mandrake home
hda7 slackware home
Yes I see what I've done. I've overwritten the MBR. So I need to sort that out. I've been trying to get slackware to boot into a graphical environment. I used pico to change the run level from 3 to 4. However although I'm using KDE it launched into gnome. Not sure why. It did that last time I tried briefly to get going with slackware.
The sound is now going, better than Mandrake actually, I think I should have chosen to use the root partition instead of the MBR for booting.
When you run lilo, it will need to read the kernel image for Mandrake - thus the reason for it to be mounted. (Obviously, it can be unmounted straight after). It is possible that you may also need an initrd entry, depending on whether the Mandrake kernel was set up for intrd. The easiest way to check whether your entry is correct, incidentally, is to read the /mnt/hda1/etc/lilo.conf entry for Mandrake.
I should have chosen to use the root partition instead of the MBR for booting.
Actually, I prefer to use the Mbr over the root partition for the boot loader, as that way you have one system managing the entire boot process. True, if you had installed Slackware's lilo into root you wouldn't have overwritten the existing bootloader, but instead would have been left with a two-tier boot loader (annoying, IMHO).
This is a bit embarassing but I can't work out how to log in to gnome as root so I can alter files. How do I do it? Say I want to alter /etc/inittab. Do I need to type su at the terminal to use file manager?
To get a root console, yes, just type "su" and enter (exit once finished). To use a gui file manager as root, there will probably be an entry on the Gnome menu -- I'm on KDE at the moment, where it's at System -> More apps -> File manager (super user mode).
Otherwise, you can usually just type "gksu <programname to get root access.