griff04
10-27-2002, 01:47 PM
Setting up Dual Boot for XP and RH 8
Which should I use to make this as simple as possible.
Grub or Lilo?
Thanks
RSG
Which should I use to make this as simple as possible.
Grub or Lilo?
Thanks
RSG
Click to See Complete Forum and Search --> : Grub or Lilo ????????
Pastrydictator
10-27-2002, 01:54 PM
i use lilo, it's easy and fun!
liloconfig
liloconfig
mdwatts
10-27-2002, 01:56 PM
Please only post your question in one forum.
Thank-you
Grub...
Thank-you
Grub...
Hayl
10-27-2002, 02:13 PM
Grub
LILO is old.
LILO is old.
mdwatts
10-27-2002, 02:41 PM
Originally posted by Cybr099
Grub
LILO is old.
Lilo is old?
They release updated versions of Lilo all the time.
Grub
LILO is old.
Lilo is old?
They release updated versions of Lilo all the time.
Bird382
10-27-2002, 04:13 PM
I prefer GRUB for pure linux installs (Linux is the only OS on the machine.)
But for a Win XP / Linux dual boot, go with LILO. GRUB tends to get the wrap as the newer, more exciting loader (my god, we computer geeks are sad :-) ), but LILO works and that's all you need.
Setting up LILO for a dual boot is very simple, for a beginner, go that route.
But for a Win XP / Linux dual boot, go with LILO. GRUB tends to get the wrap as the newer, more exciting loader (my god, we computer geeks are sad :-) ), but LILO works and that's all you need.
Setting up LILO for a dual boot is very simple, for a beginner, go that route.
mdwatts
10-27-2002, 04:40 PM
Originally posted by Bird382
Setting up LILO for a dual boot is very simple, for a beginner, go that route.
So is Grub.
Besides you don't need to run '/sbin/grub' everytime you make a change to the Grub boot config as you do for Lilo (/sbin/lilo).
Grub works just fine for dual booting with W2K/XP.
title = Windows XP Professional
root = (hd0,0)
makeactive
chainloader +1
Setting up LILO for a dual boot is very simple, for a beginner, go that route.
So is Grub.
Besides you don't need to run '/sbin/grub' everytime you make a change to the Grub boot config as you do for Lilo (/sbin/lilo).
Grub works just fine for dual booting with W2K/XP.
title = Windows XP Professional
root = (hd0,0)
makeactive
chainloader +1
Pastrydictator
10-27-2002, 08:06 PM
But for the average user: they don't change their partitions every week, so running /sbin/lilo isn't that big of a deal.
Unless you're on a tour d'force of distros, don't go out of your way to use grub or lilo; just use whatever goes.
Unless you're on a tour d'force of distros, don't go out of your way to use grub or lilo; just use whatever goes.
Hayl
10-27-2002, 08:11 PM
Originally posted by mdwatts
Lilo is old?
They release updated versions of Lilo all the time.
ya - it's a way older app than GRUB - as in it has been around longer.
Lilo is old?
They release updated versions of Lilo all the time.
ya - it's a way older app than GRUB - as in it has been around longer.
JP83
10-28-2002, 10:43 AM
I like more about lilo (i always use that), but grup looks better.
Hayl
10-28-2002, 10:48 AM
There is an article on Grub in the October "LINUX Format" magazine. (Mag from the UK)
Elijah
10-30-2002, 06:08 PM
Grub. I like the splash screen :D
smokybobo
10-30-2002, 09:36 PM
For me, grub STILL doesn't boot windows properly when windows is on the secondary master drive and linux is on the primary master with both drives having 6-10 partitions each.
In this one case, for me, lilo is still better.
In this one case, for me, lilo is still better.
mdwatts
10-31-2002, 07:31 PM
Originally posted by smokybobo
For me, grub STILL doesn't boot windows properly when windows is on the secondary master drive and linux is on the primary master with both drives having 6-10 partitions each.
In this one case, for me, lilo is still better.
Sure it does. All you need to do is map the correct drives the same as you would do for Lilo.
Different ways of accomplishing the same task.
title = windows
map (hd0, hd1)
map (hd1, hd0)
chainloader (hd*,*)+1
title windows
map (hd0,0) (hd0,2)
map (hd0,2) (hd0,0)
setup (hd0)
rootnoverify (hd0,2)
chainloader +1
hd0 - hda
hd1 - hdb
hd2 - hdc
hd3 - hdd
For me, grub STILL doesn't boot windows properly when windows is on the secondary master drive and linux is on the primary master with both drives having 6-10 partitions each.
In this one case, for me, lilo is still better.
Sure it does. All you need to do is map the correct drives the same as you would do for Lilo.
Different ways of accomplishing the same task.
title = windows
map (hd0, hd1)
map (hd1, hd0)
chainloader (hd*,*)+1
title windows
map (hd0,0) (hd0,2)
map (hd0,2) (hd0,0)
setup (hd0)
rootnoverify (hd0,2)
chainloader +1
hd0 - hda
hd1 - hdb
hd2 - hdc
hd3 - hdd
smokybobo
11-01-2002, 12:05 AM
Originally posted by mdwatts
Sure it does. All you need to do is map the correct drives the same as you would do for Lilo.
Different ways of accomplishing the same task.
title = windows
map (hd0, hd1)
map (hd1, hd0)
chainloader (hd*,*)+1
title windows
map (hd0,0) (hd0,2)
map (hd0,2) (hd0,0)
setup (hd0)
rootnoverify (hd0,2)
chainloader +1
hd0 - hda
hd1 - hdb
hd2 - hdc
hd3 - hdd
Actually, no it doesn't.
For one, I'm pretty sure your syntax for the map function is wrong (see below). Secondly, I've only got 2 hard drives, so hd0 would be the first hd, and hd1 would be the second hd. If you or anyone think you can solve this problem, then post some suggestions. I've been trying grub off and on for a few months now (and nobody here was able to solve this the last time I posted this question here), and in my situation it doesn't work.
Mind you, I'm not really looking for help (since I've tried every suggestion suggested to me these past months), but take a crack (again!) and see if anyone can 'fix' it.
My hard drives:
Primary master:
Device Boot Start End Blocks Id System
/dev/hda1 * 1 17 136521 83 Linux
/dev/hda2 18 2481 19792080 f Win95 Ext'd (LBA)
/dev/hda5 18 1078 8522451 83 Linux
/dev/hda6 1079 2139 8522451 83 Linux
/dev/hda7 2140 2396 2064321 83 Linux
/dev/hda8 2397 2441 361431 83 Linux
/dev/hda9 2442 2481 321268+ 82 Linux swap
Secondary master:
/dev/hdc1 * 1 131 1052226 b Win95 FAT32
/dev/hdc3 132 1650 12201367+ f Win95 Ext'd (LBA)
/dev/hdc5 132 178 377496 b Win95 FAT32
/dev/hdc6 179 225 377496 b Win95 FAT32
/dev/hdc7 226 478 2032191 b Win95 FAT32
/dev/hdc8 479 609 1052226 b Win95 FAT32
/dev/hdc9 610 740 1052226 b Win95 FAT32
/dev/hdc10 741 1093 2835441 b Win95 FAT32
/dev/hdc11 1094 1650 4474071 b Win95 FAT32
Primary slave is a dvd-rom. Secondary slave is a cd-burner.
Situation: linux boots fine and dandy, no problems. Windows 98 SE boots ONLY to the c drive. No other supposed windows partitions can be accessed (get that "retry, fail, abort" question). From my tests (and the one time I booted all the way into windows as opposed to just prompt), it seems that windows is trying to see my linux partitions instead of ignoring them and including them in all the partitions it can see (probably having to do with going through bios to detect the hard drives). Unfortunately, absolutely no 'seen' partition is accessible in windows.
What I have tried:
title Windows98
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd1,0)
chainloader +1
makeactive
That and every other variation of this and other 'tips' found online, from the grub man page, to the 'Art and Zen of grub', and many other online docs people have put up.
The 'chainloader (hd*,*) +1' line suggested by mdwatts results in an error stating 'cannot parse number' or some such. I've tried the grub debian package, grub from a tarball, grub from cvs, and the results are all the same. LILO, BootMagic and a couple of other (windows-esque graphical) boot loaders that I can't remember the names of off the top of my head all work fine with my setup (though I find lilo the best of all of em. For one, I'm not limited to ONLY the mbr like those graphical bootloaders are since I'm of the belief that the mbr should ONLY point to the current active partition and not host any weird programs like bootloaders and such).
And no, swapping drives around is not an option. I have verified that it does work with windows on the primary hard drive, but then what would be the fun in that having it work? Besides, it's my linux drive I want in the removable hd rack, not windows ;)
Beyond that (and hiding a couple of partitions here and there via grub - what a mess it made of windows doing that :p ) and actually manually remapping every windows partition to something else as well as using grub floppy/off the mbr/off the root boot sector and some other linux-specific stuff (devfs on or off, using the drive map file or no - any combination of these don't work), nothing works.
Again, this is not to say that grub is bad or anything. I'm sure for all the people that grub works, it works great. But it doesn't work for me (in this situation), so I use lilo. No biggie. Though I would like to know if other people with a setup similar to mine have got grub to boot.
Anyways, this is a long-ish post that isn't really asking for help anyway (though if anyone can give help, that would be great :) ), just to reiterate that at this point in time, neither grub nor lilo is, at least IMO, better than the other in all situations.
Sure it does. All you need to do is map the correct drives the same as you would do for Lilo.
Different ways of accomplishing the same task.
title = windows
map (hd0, hd1)
map (hd1, hd0)
chainloader (hd*,*)+1
title windows
map (hd0,0) (hd0,2)
map (hd0,2) (hd0,0)
setup (hd0)
rootnoverify (hd0,2)
chainloader +1
hd0 - hda
hd1 - hdb
hd2 - hdc
hd3 - hdd
Actually, no it doesn't.
For one, I'm pretty sure your syntax for the map function is wrong (see below). Secondly, I've only got 2 hard drives, so hd0 would be the first hd, and hd1 would be the second hd. If you or anyone think you can solve this problem, then post some suggestions. I've been trying grub off and on for a few months now (and nobody here was able to solve this the last time I posted this question here), and in my situation it doesn't work.
Mind you, I'm not really looking for help (since I've tried every suggestion suggested to me these past months), but take a crack (again!) and see if anyone can 'fix' it.
My hard drives:
Primary master:
Device Boot Start End Blocks Id System
/dev/hda1 * 1 17 136521 83 Linux
/dev/hda2 18 2481 19792080 f Win95 Ext'd (LBA)
/dev/hda5 18 1078 8522451 83 Linux
/dev/hda6 1079 2139 8522451 83 Linux
/dev/hda7 2140 2396 2064321 83 Linux
/dev/hda8 2397 2441 361431 83 Linux
/dev/hda9 2442 2481 321268+ 82 Linux swap
Secondary master:
/dev/hdc1 * 1 131 1052226 b Win95 FAT32
/dev/hdc3 132 1650 12201367+ f Win95 Ext'd (LBA)
/dev/hdc5 132 178 377496 b Win95 FAT32
/dev/hdc6 179 225 377496 b Win95 FAT32
/dev/hdc7 226 478 2032191 b Win95 FAT32
/dev/hdc8 479 609 1052226 b Win95 FAT32
/dev/hdc9 610 740 1052226 b Win95 FAT32
/dev/hdc10 741 1093 2835441 b Win95 FAT32
/dev/hdc11 1094 1650 4474071 b Win95 FAT32
Primary slave is a dvd-rom. Secondary slave is a cd-burner.
Situation: linux boots fine and dandy, no problems. Windows 98 SE boots ONLY to the c drive. No other supposed windows partitions can be accessed (get that "retry, fail, abort" question). From my tests (and the one time I booted all the way into windows as opposed to just prompt), it seems that windows is trying to see my linux partitions instead of ignoring them and including them in all the partitions it can see (probably having to do with going through bios to detect the hard drives). Unfortunately, absolutely no 'seen' partition is accessible in windows.
What I have tried:
title Windows98
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd1,0)
chainloader +1
makeactive
That and every other variation of this and other 'tips' found online, from the grub man page, to the 'Art and Zen of grub', and many other online docs people have put up.
The 'chainloader (hd*,*) +1' line suggested by mdwatts results in an error stating 'cannot parse number' or some such. I've tried the grub debian package, grub from a tarball, grub from cvs, and the results are all the same. LILO, BootMagic and a couple of other (windows-esque graphical) boot loaders that I can't remember the names of off the top of my head all work fine with my setup (though I find lilo the best of all of em. For one, I'm not limited to ONLY the mbr like those graphical bootloaders are since I'm of the belief that the mbr should ONLY point to the current active partition and not host any weird programs like bootloaders and such).
And no, swapping drives around is not an option. I have verified that it does work with windows on the primary hard drive, but then what would be the fun in that having it work? Besides, it's my linux drive I want in the removable hd rack, not windows ;)
Beyond that (and hiding a couple of partitions here and there via grub - what a mess it made of windows doing that :p ) and actually manually remapping every windows partition to something else as well as using grub floppy/off the mbr/off the root boot sector and some other linux-specific stuff (devfs on or off, using the drive map file or no - any combination of these don't work), nothing works.
Again, this is not to say that grub is bad or anything. I'm sure for all the people that grub works, it works great. But it doesn't work for me (in this situation), so I use lilo. No biggie. Though I would like to know if other people with a setup similar to mine have got grub to boot.
Anyways, this is a long-ish post that isn't really asking for help anyway (though if anyone can give help, that would be great :) ), just to reiterate that at this point in time, neither grub nor lilo is, at least IMO, better than the other in all situations.
smokybobo
11-01-2002, 12:15 AM
Oh, and so what if you don't have to run an external program to update grub? I wrote a script that lets me manually edit lilo.conf and then automatically (and safely) updates lilo on the boot sector of my root partition. I call it 'vililo' after other similar programs (like vipw, and visudo, and vimtutor) and it takes just as little time to update lilo as it does to update grub's menu.lst file.
Scripting is :cool:
(And yes, I know about liloconfig, and no, I don't like liloconfig, in fact, I HATE liloconfig with a boisterously brimming burning kind of hate, and no, not a mere and slight extreme dislike for it, I'm talking HATE here and have hated it so since my slackware days...
...of course for no other reason than I don't like, no, not merely dislike, but HATE how much crap the versions I've tried put into lilo.conf, so yes I'm biased towards the few handful of experiences I've had with it and yes, I really do like spouting hyperbole left right center up down and the nth dimension and yes this is really all just an excuse to keep typing and typing and typing and typing and typing...)
Scripting is :cool:
(And yes, I know about liloconfig, and no, I don't like liloconfig, in fact, I HATE liloconfig with a boisterously brimming burning kind of hate, and no, not a mere and slight extreme dislike for it, I'm talking HATE here and have hated it so since my slackware days...
...of course for no other reason than I don't like, no, not merely dislike, but HATE how much crap the versions I've tried put into lilo.conf, so yes I'm biased towards the few handful of experiences I've had with it and yes, I really do like spouting hyperbole left right center up down and the nth dimension and yes this is really all just an excuse to keep typing and typing and typing and typing and typing...)
mdwatts
11-01-2002, 07:33 PM
Originally posted by smokybobo
Actually, no it doesn't.
Yes it does...
What I posted are ALL valid depending on your partition/HD setup.
They do work.
Actually, no it doesn't.
Yes it does...
What I posted are ALL valid depending on your partition/HD setup.
They do work.
smokybobo
11-02-2002, 03:39 AM
Originally posted by mdwatts
Yes it does...
What I posted are ALL valid depending on your partition/HD setup.
They do work.
I never said what you gave didn't work at all (though the chainloader (hd*,*) line absolutely does NOT work with any version of grub I've tried, and not for failure for accessing the harddrive as I'm pretty sure "Cannot parse number" error is something to do with the parsing of the command, though I could be wrong) for some situations, just that it doesn't work with my situation.
Furthermore, I am 100% sure that grub will work properly if windows and linux are on the same hard drive. And I am also 100% sure that grub will work properly if windows is primary master and linux is on any other IDE channel. What doesn't work for me is how I have exactly described my setup. I have pretty much ruled out hardware problems given that grub is the only bootloader out of 5 that I've tried that doesn't work for my system (unless, of course, grub does things in such a radically different way in terms of accessing bios/hardware than the other bootloaders that could conceivably expose a hardware problem, though I think this event is highly unlikely). And I am not willing to change my setup, not when it is proven to me that there are other bootloaders that work perfectly fine with my setup.
Again, grub is pretty nice from what I've seen, but it doesn't work in my situation. So I use lilo. If/when grub does work (and I'm sure it eventually will), I'll take it for a spin and consider replacing lilo.
The sad thing is it seems that everyone who has given advice doesn't have the same setup as me. All have either had windows and linux on the same harddrive or have had windows on the first hd and linux where ever else, so I can't be totally 100% sure if it really is a problem with the software, not until I can see someone's grub configuration file for a setup similar to mine and having everything work.
Though considering I've been tackling this for a few months with considerable time spent on research and trying out other people's advice, I'm definitely leaning more toward the software being at fault in my situation.
For reference, this (http://www.linuxnewbie.org/forum/showthread.php?threadid=29112) was a previous thread that also describes my problems. The only difference between then and now is I now know how to make grub use a device.map file to map harddrives.
Yes it does...
What I posted are ALL valid depending on your partition/HD setup.
They do work.
I never said what you gave didn't work at all (though the chainloader (hd*,*) line absolutely does NOT work with any version of grub I've tried, and not for failure for accessing the harddrive as I'm pretty sure "Cannot parse number" error is something to do with the parsing of the command, though I could be wrong) for some situations, just that it doesn't work with my situation.
Furthermore, I am 100% sure that grub will work properly if windows and linux are on the same hard drive. And I am also 100% sure that grub will work properly if windows is primary master and linux is on any other IDE channel. What doesn't work for me is how I have exactly described my setup. I have pretty much ruled out hardware problems given that grub is the only bootloader out of 5 that I've tried that doesn't work for my system (unless, of course, grub does things in such a radically different way in terms of accessing bios/hardware than the other bootloaders that could conceivably expose a hardware problem, though I think this event is highly unlikely). And I am not willing to change my setup, not when it is proven to me that there are other bootloaders that work perfectly fine with my setup.
Again, grub is pretty nice from what I've seen, but it doesn't work in my situation. So I use lilo. If/when grub does work (and I'm sure it eventually will), I'll take it for a spin and consider replacing lilo.
The sad thing is it seems that everyone who has given advice doesn't have the same setup as me. All have either had windows and linux on the same harddrive or have had windows on the first hd and linux where ever else, so I can't be totally 100% sure if it really is a problem with the software, not until I can see someone's grub configuration file for a setup similar to mine and having everything work.
Though considering I've been tackling this for a few months with considerable time spent on research and trying out other people's advice, I'm definitely leaning more toward the software being at fault in my situation.
For reference, this (http://www.linuxnewbie.org/forum/showthread.php?threadid=29112) was a previous thread that also describes my problems. The only difference between then and now is I now know how to make grub use a device.map file to map harddrives.
justlinux.com
Copyright Internet.com Inc. All Rights Reserved.
Copyright Internet.com Inc. All Rights Reserved.