LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Laptop and Netbook (http://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/)
-   -   Dual booting XP/Slack 10.2 on laptop (http://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/dual-booting-xp-slack-10-2-on-laptop-425260/)

alphisb0t 03-15-2006 11:19 PM

Dual booting XP/Slack 10.2 on laptop
 
Ok I know there are a billion of these threads about and I have searched them but they all seem kind of specific with things that don't apply such as IDE and SATA drives and 2 IDE drives etc. Here's what I'd like to do.

I have XP installed on the ONLY drive on my laptop. I wish to dual boot XP and Slack. I've partitioned the drive in this way:

hda1 (xp resized a bit less to allow room for linux parts)
hda2 (bootable linux part)
hda3 (swap part)
hda4 (ext3 part)

I've installed Slack and set hda4 as root and hda3 as swap. Now my question is how can I configure LILO to allow me to boot xp/slack. I've read articles that claim installing LILO to MBR is DEATH. Then others that says installing to superblock doesn't work either. I'd like to know what will get the results I need.

Where should I install LILO, and with what parameters should I config it. I also don't want to do the "install LILO to MBR...then copy backed up windows MBR over it again..." thing. I've seen random incoherent bits about doing that too.

Any help is appreciated =]

- slacker

camh 03-15-2006 11:34 PM

Adding..
Code:

other=/dev/hda1
  label=windows

..to lilo.conf should work. Then type 'lilo'.

I've always installed lilo to the MBR with slack and I've never had problems.

J.W. 03-16-2006 01:15 AM

I always install lilo to the MBR and at least for me it's been a non-issue. I guess I'm not sure of the question here; if you are attempting dual boot between Linux and Windowns you just need to have an option in your boot manager (ie, lilo or GRUB) that offers the OS in question. Could you post your lilo.conf?

alphisb0t 03-16-2006 03:55 PM

Thanks for the replies. My question is mainly this. Will installing lilo to MBR cause windows to not function any more? I've read random posts from people saying windows will no longer boot if you modify the MBR.

My lilo conf has yet to be written since I haven't installed it yet, but I will provide that other field pointing to /dev/hda1. I'm hoping this is sufficient to boot windows. I see linux has many more options than windows in terms of the lilo.conf file.

On another note, the old versions of lilo cannot read past 1024 cylinders. Slack has always used the old lilo for its distros. Does anyone know if this has changed for 10.2? If not, how can I get a new lilo if I cannot even boot linux to install it?

- Slack

camh 03-16-2006 07:16 PM

It shouldn't prevent Windows from loading by installing to the MBR, but your best bet would be to just try it.

You can always re-install the Windows MBR if something does screw up. Just boot off a Windows boot disk and type 'fdisk /mbr' at the command prompt. Or, boot off a slack disk (there's an example on the CD boot loader that tells you how to mount your HD) and re-install lilo. You have options if something does go wrong, just make and test your boot disks in advance and you should be fine.

And yes, adding those lines to your lilo.conf should be all you have to do to add windows to your boot menu.

Randux 03-16-2006 07:39 PM

I multiboot Windows and multiple linuces with lilo installed to the MBR. This is the only rational way to install lilo. If not, you have to play games with ntloadr and the whole point is *reducing* dependency on Gatesware, is it not?

We all run lilo in the MBR, and we all smile a lot.

Not only does lilo not break anything, but once you know how to use it, you can get it to do some amazing sh$t! And you can boot anything with it. I can add a new distro in a few seconds (I change my installation a lot).

By the way, if I understand correctly that you have hda2 just for /boot, may I suggest taking another look at your partitioning strategy because you only get 4 real partitions and you don't need one for /boot. Also, you have now insured that you can't get anything else on that drive- all your partitions are assigned.

A better setup would be:

/dev/hda1 windows
/dev/hda2 distro 1
/dev/hda3 distro 2
/dev/hda4 extended
/dev/hda5 swap
/dev/hda6 /home for distro x/y/z
/dev/hda7 distro 3
/dev/hdan distro n

Also, be aware that *BSD will only live in a real partition. So if you might like to try one, plan ahead. I didn't know it until it was too late.

Randux 03-16-2006 07:44 PM

Quote:

Originally Posted by alphisb0t
Thanks for the replies. My question is mainly this. Will installing lilo to MBR cause windows to not function any more? I've read random posts from people saying windows will no longer boot if you modify the MBR.

My lilo conf has yet to be written since I haven't installed it yet, but I will provide that other field pointing to /dev/hda1. I'm hoping this is sufficient to boot windows. I see linux has many more options than windows in terms of the lilo.conf file.

On another note, the old versions of lilo cannot read past 1024 cylinders. Slack has always used the old lilo for its distros. Does anyone know if this has changed for 10.2? If not, how can I get a new lilo if I cannot even boot linux to install it?

- Slack

I posted an answer above, but I wanted to respond to these three issues:

1. Hogwash. Anybody who says that he installed lilo in the MBR and now he can't boot Windows did it to himself.
2. The windows config in lilo is simple because lilo just gives control to the windows boot loader. other, label, and table are the only three lines you need. You may not even need the table line, but I include it anyway.
3. This restriction is long gone. And if you have a CD drive and you can boot from CD, you can fix almost anything that will ever go wrong with a live CD. Slax is good, Kanotix is even better.

In the old (pre live CD) days, installing linux in a dual-boot scenario with windows was a high-wire act. Now even a school kid can do it because lilo is so easy to use and because live CDs have lilo on them.

alphisb0t 03-16-2006 10:39 PM

Thanks for all your help. Installing lilo to the MBR didn't destroy windows and it loads everything perfectly! I had to fix a kernel panic by adding the root=/dev/hda1 line but after I did so linux booted just fine.

I now have another problem. Getting my USB mouse to be detected so startx can stop complaining. I've actually just continued a thread I found on this very issue here: http://www.linuxquestions.org/questi...ighlight=mouse

Also, your partitioning scheme is much nicer than mine. I will remove the boot partition as it seems I don't need it for a dual boot.

Thanks again for your help.

- slacker

edit:

Just wanted to add that using a live cd called auditor security cd I wasn't able to mount my /dev/hda4 for some strange reason. I could mount it no problem booting from my slack disc 1 installation cd. Does this happen for all live cds?

Randux 03-17-2006 12:40 AM

Quote:

Originally Posted by alphisb0t
Thanks for all your help. Installing lilo to the MBR didn't destroy windows and it loads everything perfectly! I had to fix a kernel panic by adding the root=/dev/hda1 line but after I did so linux booted just fine.

I now have another problem. Getting my USB mouse to be detected so startx can stop complaining. I've actually just continued a thread I found on this very issue here: http://www.linuxquestions.org/questi...ighlight=mouse

Also, your partitioning scheme is much nicer than mine. I will remove the boot partition as it seems I don't need it for a dual boot.

Thanks again for your help.

- slacker

edit:

Just wanted to add that using a live cd called auditor security cd I wasn't able to mount my /dev/hda4 for some strange reason. I could mount it no problem booting from my slack disc 1 installation cd. Does this happen for all live cds?

Right on, I am happy to hear of your success, and it's good when you let people know the problem is fixed so later on, other guys reading the thread know what happened.

I don't have a USB mouse but this shouldn't be too hard to get working, it's very common. Check the forums here as much as you can and I'm sure you will find the answer.

I did a lot of reading and asking questions and I still missed the fact that you need a real partition if you want to run *BSD. So the best thing is to ask before you do. We all tried and made mistakes and if you stay with it you will get things setup how you like. :cool:

I have no idea why you can't mount a partition except that if the live CD built an fstab and you tried to mount a partition with different attributes, you usually get a misleading error message. Who knows what kind of filesystem support that CD used? I would stay with the better known Live CDs if you are doing anything important- DSL, Slax, Kanotix, Knoppix- they all work.


All times are GMT -5. The time now is 01:53 PM.