Linked by Thom Holwerda on Wed 21st Apr 2010 23:01 UTC
Linux The tools used to boot Linux are changing. Specifically, the Grand Unified Bootloader is now officially in maintenance mode only, and GRUB's developers have abandoned the original GRUB in favor of an entirely rewritten package, known as GRUB 2. Discover GRUB 2's new capabilities and how to use it.
Thread beginning with comment 420329
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Vent
by turrini on Thu 22nd Apr 2010 16:50 UTC in reply to "Vent"
turrini
Member since:
2006-10-31

I've never had a GRUB2 problem, and I'm talking about of 1200+ installations of it at the company I work for, in mixed Debian testing/sid/experimental environments.

Sorry dude, but let the documentation help you before you start complaining.

Reply Parent Score: 2

RE[2]: Vent
by aaronb on Thu 22nd Apr 2010 17:01 in reply to "RE: Vent"
aaronb Member since:
2005-07-06

Are the 1200+ installations on a variety of hardware configurations?

Reply Parent Score: 2

RE[3]: Vent
by turrini on Thu 22nd Apr 2010 17:11 in reply to "RE[2]: Vent"
turrini Member since:
2006-10-31

Yes, since generic machines with common mobos (pc chips, msi, gigabyte, asus, etc) to medium/high end computers/servers (mainly HP, IBM, Dell and some Supermicro/Megaware).

It's a very mixed environment. IDE/SATA/SCSI/SAS, GRUB2 work for us every time.

My personal notebook, HP Pavilion DV5 1240br, works flawlessly with grub2, with grub1, it doesn't work (doesn't recognize my hd).

Reply Parent Score: 3

RE[2]: Vent
by fretinator on Thu 22nd Apr 2010 17:40 in reply to "RE: Vent"
fretinator Member since:
2005-07-06

I'm elated when I report various issues with a product, and someone informs me that they have had no problems. Now I can sleep at night!

Seriously, my main complain is _NOT_ that Grub2 is a worse product. I've had trouble with the original Grub (especially when the BIOS mis-reported a drive size), and I have had troubles at times with LILO. This is normal. In my case, I think it had to do with the particular Tablet PC I was using. Some Tablet PC's have a wierd way of initializing there devices at startup.

Anyhoo, the point is that when something invariably goes wrong (which happens with all software - I write software for a living ;} ), the means by which you resolve these issues is quite tortuous in Grub2. By having its configuration spread out in multiple places (at least 3 that I know of), and multiple files in each location, they have created quite a puzzle for the end user. At some point, a good front-end to all of this will be created (there is one I have looked at so far), then this will become less of an issue.

Really, I would see Grub2 _currently_ as more appropriate for Fedora. For Ubuntu, which emphasizes the "Just Works" philosophy, I do not believe it is stable and friendly enough for the end user. Just my $0.03 (my opinion is worth 50% more).

Reply Parent Score: 2