Adding a second linux. [Guidance needed]
Okay,
I have installed succesfully SuSE 10.0 and Windows XP on my computer. Now I have extra 20Gb on the HD where the SuSE is installed and I thought to install Debian there to test that distro. I presume this is possible but I´m not sure how this is done. I have 2 hard disks, a 400Gb and 40Gb disks. The 40Gb is master and has Grub and SuSE istalled on it. The bigger has all "important stuff" and the Windows XP. So I need a quick list of things to do to get this thing working. 1. Boot from debian CD 2. Make correct partitions (= unused 20gb -> ext3) 3. Problem: Do I need boot partition or swap and how to make them to work? 4. Install Debian 5. Add Debian's start command to Grub. And what about the partitions. I have now the 40Gb disk partitioned as follows. /boot 70mb swap 512mb / 20Gb Should I add another /boot, swap and root partitions or can I use existing boot and swap partitions? This is what I think at the moment. I´m trying to move away from the windows as much as possible but as I am a gamer it´s kinda hard but I´m getting there :) |
I do one partition per Linux.
My signature should have everything you need up to over 100 systems. You should do it "the lazy way" too as it is the easiest in the world. |
You are 99% there---since you have dual-boot working.
Install debian with NO boot loader Edit the existing /boot/grub/menu.lst (part of the SUSE installation) to add an entry for debian. If you look at the format of the entry for SUSE, it's pretty easy to see what the equivalent entry will be for Debian. "Grub-speak" takes getting used to, and you may also want to get the grub manual (from the grub website) |
You can use your existing swap partition for Debian. Not sure about the boot partition, as I only ever have a root partition for Linux (well and swap of course) and no separate ones for boot, or anything else.
|
No--you cannot share the /boot partition
|
I have one swap and it is automatically picked up for use by all the Linux.
The /boot is an old tradition to keep the kernel and the boot loader at the bottom end of the hard disk to avoid difficulties of addressing a large hard disk. Modern Linux don't have this problem any more but documentation has been written for it so users just follow. If you have a Linux under the 137Gb barrier there is very little it cannot boot. |
Quote:
|
I have one swap and it is automatically picked up for use by all the Linux.
The /boot is an old tradition to keep the kernel and the boot loader at the bottom end of the hard disk to avoid difficulties of addressing a large hard disk. Modern Linux don't have this problem any more but documentation has been written for it so users just follow. If you have a Linux under the 137Gb barrier there is very little it cannot boot. --------------------------------------- The /boot can be shared because it is the home for the kernels and initrds (ram disk files) but it can get confused very quickly if you have 3 or more Linux there. That is why it pays to use a single partition for each Linux as each will have its /boot inside and can be access by adding the partition reference in front like the kernel Code:
/boot/vmlinuz-2.6.14-1.1696_FC5 Code:
(hd0,5)/boot/vmlinuz-2.6.14-1.1696_FC5 In Linux we can use Kernel from Linux A to boot Linux B so technically there is no problem to put all the kernels together. The problem is tell which one belongs to which Linux, as many of them, like the Slackware and Slax families, use the same name like "vmlinuz" and have no initrd. -------------------------------------------------------------- Just like XP needs service packs to read a hard disk larger than 137Gb many Distros are still unable to address beyond this boundary in the hard disk. In the past there had been various methods to address beyond the 1024 cylinders too and a devoted /boot is always the first partition to be created and so it stragetically position to be well within the 1024 cylinders limit. There is no harm in creating a /boot partition it just buggers everything up when a user starts to add more distros to the box. Imagine 100 /boot partitions for 100 Linux? |
So I should copy the existing /boot to the current root and then delete the /boot partition? And then put the Grub to MBR so it would continue to work? And in the same manner keep all the distros to be installed in single partition?
What kind of command should I use? I doubt basic cp will do the work without options. And another problem arose. I booted from CD and noticed that the Debian installer doesn´t have support for Bluetooth keyboard and mouse (logitech mx5000). Any way to go around this besides connecting a PS/2 keyboard for the installation. Also, does debian have a support for the bluetooth devices? |
I have booted Linux A with kernel from Linux B and can confirm that you don't need a fixed partition to store /boot. In fact by having one partition reference you don't have to bother where the kernel is located as it is always in /boot inside the root partition of the Linux.
Put Grub into the MBR is the easiest. If you have an issue of it you can put Grub in a floppy, CD or in a data-only primary partition. I can't tell what Debian has got but most definitely it isn't as modern as others when dectecting hardware. If you want trouble free operation in Linux stick with proven hardware used by everybody. |
Okay, I think I make a another try with Gentoo... Your bound to learn the basics when installing it. Also it detects my keyboard ok... Last installation ended by wrong root password. Sometimes my keyboard places for example two xx when I only press it once. It´s not so funny when this happens in root password changing :(
Could you give a proper command to copy the boot partition to root/boot/ Is something like this "cp (hd0,0)/boot/* (hd0,1)/boot/ // probably won´t work with those partition definitions which are used in Grub. |
You have to do it in Linux, boot up a Live CD and mount your Gentoo root partition on it. Assuming the root partition ("/") of Gentoo is hda3 and /boot is in hda2 you make two directorties in a booted up Linux's /mnt
Code:
mkdir /mnt/hda2 |
Okay, I have a problem how to start my newly installed Ubuntu. I installed it in a single partition on my 40Gb system...
Code:
Levy /dev/hdc: 41.1 Gt, 41110142976 tavua Code:
###Don't change this comment - YaST2 identifier: Original name: windows### |
You made a mess for yourself.
Grub counts from 0 so (hd0,1)=the 2nd partition of the 1st disk. If your Ubuntu is in the hdc3 and there is another disk, say hda, in front the the correct reference for Unbuntu of hdc3 should be (hd1,2) How to put right the boot loader is described in my "Just booting tips" Task A7 which you can do it in Gnu/Grub shell. I suggest to print out "Just Booting tips" Follow Task A1 to confirm your disk order and partition reference in Grub Follow Task A3 to find out which two partitions have Grub, as Suse should have it too. Follow Task A6 to boot Ubuntu Follow Task A7 to restore Unbuntu boot loader If Unbuntu doesn't boot follow Task E1 If Task E1 still fails then follow Task G1 to boot it step by step Let me know your progress. My prediction Task A6 should get you home. |
Quote:
First partition is swap, second suse and the last is ubuntu. Quote:
I´ll check those and try to get to some sort of a solution. Windows and SuSE boot up still normally. |
All times are GMT -5. The time now is 12:57 AM. |