Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Yes, you can put a distro on each one:
Install both disk drives. Make sure you know which is which!
Install your first distro to hda
Boot from the CD of the distro you wish to add.
Make sure it installs to hdb ( or you will overwrite your current distro )
It should configure lilo, or grub, so you can choose which distro to boot at boot time. It really is that easy.
Originally posted by DavidTempler I have a box with two drives ... I want to put a distro on each one ...
Is it possible to boot each one from lilo ..??
If some fancy lilo or grub config utility doesn't step you through the process, basically (in lilo 'cause I don't really know grub yet) just add another entry in your /etc/lilo.conf file for another Linux, and tell it where the kernel is (probably on /dev/hdbx somewhere) and where the root file system for it is. Finally of course re-run "lilo" to actually make the changes. To boot non linux OS's from 2nd drives, the procedure is a little different - you have to do a couple of "map [drviveX] to [driveY] lines to swap the BIOS designations of the drives. You can get specifics from examples that are probably in your current /etc/lilo.conf or the tons of documentation available (and probably installed in your /usr/doc/lilo-* directory)
I usually then swap the drives and install a lilo on /dev/hdb as a backup, which is useful if you mess up the lilo on your first drive, or your first drive fails.
lilo or grub is really worth learning (along with the convoluted booting process of a modern PC) because they are very powerful for doing these kinds of things, but they will also prevent your computer from booting if you get something wrong. With good knowledge of your boot loader, you will be able to repair problems quickly. Otherwise you have beg for help on a forum like this one and sweat it out waiting for a response.
My 2 cents -- Yes, sharing a single swap partition between multiple distros is just fine. In fact I would recommend it - giving each distro its own swap is just a waste of space. That being said I would recommend against trying to share any other partitions. Different distros sometimes put things in different places, and although it may be possible to share certain other partitions, I don't think it would really be worth the effort. If you really needed to retrieve a file from the other distro, you could just temporarily mount the partition in question. -- J.W.
I'm not sure what to recommend with the reiser4. I just installed it myself, which is why I have only one distro installed. I installed a minimal Gentoo with a new kernel with reiser4 support and got the reiser4progs, made the former mandy partition reiser4 and copied the Gentoo install to it to see if it would boot and run. All was well, so I created reiser4 on the former Gentoo partition and copied it back (more disk space, you see). That's all I know about reiser4 so far. It works. It boots. But, I'm using a 220.127.116.11 kernel...I'm no help.
The problem I have is that my second drive is set up for reiser4 ....
Assuming you are saying that the Linux on /dev/hda doesn't support reiser4, here are some possible solutions:
1) Go get (patch & compile probably) and install a kernel and module set that will work with the distro you have on /dev/hda but also knows about reiser4 on your linux that is on /dev/hda. Boot up on it and do the lilo thing.
2) Boot up on the kernel from /dev/hdb but the root from /dev/hda if you can. In otherwords, run /dev/hda's Linux using /dev/hdb's kernel. You might have to copy the /lib/modules/ directory from /dev/hdb to /dev/hda if you need any modules loaded to access either file system or devices to be able to run lilo.
3) Don't use the lilo from the Linux at /dev/hda, boot into /dev/hdb and use the one from there instead. You still need to have it install the boot loader on /dev/hda. I've never tried anything like this, but it is likely it can be made to work.
4) Boot into the /dev/hdb linux, but then mount the root of the /hda linux and "chroot" into it. Then run lilo. The trick here will be to put an additional mount point to your /dev/hdb linux in your chrooted /dev/hda so that the lilo.conf file direct lilo to the kernel on /dev/hdb from looking at /dev/hda. I think I've done this before, but can't remember the trick.
5) Just copy the kernel and initrd (if you have one) from /dev/hdb to some safe place on /dev/hda, edit lilo.conf so it can find it in it's new location, and re-run lilo. This is probably the simplest solution.
6) Physically swap the two hard drives and do everything from the linux on /dev/hdb which is now /dev/hda. This is also a pretty simple solution.
Even if not stated, all of the above solution will require some changes to your lilo.conf file so it knows where to find everything and where to install everything. Also, some of these solutions will require both hard drives to be in the computer in their present configuration in order to boot anything at all. This is a little scary to me, but people who do the striping RAID-0 arrays are use to this kind of thing.
Oh yea, an it is a good idea to put the swap file on the fastest or the least busy hard drive and controller. Of course these days people put so much RAM in their machines that the swap file seldom gets used anyway, so you might not notice much difference.
Originally posted by DavidTempler I tried to use other = (which looks for lilo on second drive) which booted lilo on second drive but as system on hdb1 was not set up correctly (my fault) then it will not boot.
Oh yea, I've made this work before too, but there might have been a trick to it.
A mistake that is often made is that the view of the hard drives at boot time (thus the BIOS view) may not be the same as the view of things from the fully booted Linux that you are about to run "lilo" on. Lilo versions 22.5 and later help fight these problems.
I think you are going to know a lot more about lilo before all this is over! Don't give up, I've found that there is always a way to get lilo do what you want. It is just that is is very confusing trying to figure out what went wrong when the computer won't boot.
Originally posted by DavidTempler Setting up lilo is just a part of it ... you also have to also configure fstab to see the parition you want to boot.
Yes, this is true if the position of the hard drives have changed since you ran the installer for the linux you installed on /dev/hdb. When it is wrong, entering a "root=/dev/hdb1" or whatever as a boot parameter at the lilo prompt should get the thing to boot, at least in single user mode (the filesystem checks in the init scripts for the higher modes usually get all freaked out when fstab is all wrong)