M Harris wrote:
On Wednesday 04 October 2006 16:06, Sergey Mkrtchyan wrote:
Let me put it little theoretical. So if, for example, cfdisk shows that my Windows sits on hda5, which is my C: drive, I should add (hda4,0)+1 in my menu.lst? No, not quite, but you're getting closer....
But first, let's talk about a more real theoretical scenario, ok?
Sure, I like thoery. I see in your case it turned to be more of a practive ;)
Let's say that windoze is on the second partition... as about half of my systems fall into this category. My first partition contains what will eventually be mounted as /boot. My second partition is windoze, my third will be mounted as SWAP, and my fourth partition is EXTENDED... and all the rest of my partitions (for /home, /tmp, /var, /opt, /usr, and /local) are logical partitions. Looks like this: /dev/hda1 /boot /dev/hda2 windoze W95 Fat32 /dev/hda3 SWAP /dev/hda4 (extended) /dev/hda5 / /dev/hda6 /home etc
Now, how do we tell grub to find windoze?
title windoze chainloader (hd0,1)+1
The disk is hd0 (corresponds to /dev/hda) and the partition is 1 (corresponds to /dev/hda2)... ok?
Now then, the reason your theoretical scenario isn't too good to talk about is that windoze will never be on /dev/hda5 because it needs to be in a primary partition. Linux on the other hand can be anywhere these days (using grub) so we usually put windoze on the first primary partition on the first disk and place Linux behind it. That way windoze (like a little kid in line) thinks its the most important one because it gets to be first. ;-)
Just for completion sake... the /boot/grub/menu.lst command used to look like this: (for the above example)
title windoze root (hd0,1) chainloader +1
This time I did get it completely, thank you very very much for such a detaied explanation...I am sure, as soon as my friend gets to work, that will work for him. Thank you very much again Regards, Sergey -- Sergey Mkrtchyan, Scinetific Researcher, Department of Molecular Physics, Faculty of Physics, Yerevan State University