GRUB: was,..Re: Fwd: Re: New kernel

Bryce C plug-discuss@lists.plug.phoenix.az.us
02 Jan 2003 09:49:22 -0700


--=-uXGO5EEHBlJHUPkasAgA
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

My installations of GRUB on my Gentoo, Mandrake, and SuSE boxes have all
been flawless and wiyhout any probs whatsoeever.

On Thu, 2003-01-02 at 09:29, Liberty Young wrote:
> I've been watching the GRUB mailing list for quite some time
> now....Gentoo folks have had the least amount of luck using GRUB. Then
> it's Redhat poeple. I rarely see Suse and other distros not work.=20
>=20
> Based on the exeperiences of those on the GRUB mailing list, if you're
> using Gentoo, grab the latest CVS of GRUB and don't use the one from
> Gentoo.=20
>=20
>=20
> On Wed, 2003-01-01 at 15:30, Kurt Granroth wrote:
> > On Wednesday 01 January 2003 03:10 pm, Bryce C wrote:
> > > A) lilo needs to be rerun everytime a config change is made as oppose=
d
> > > to grub which reads the file of your hard drive at boot.
> > > B) I've found grub to be compatible on more hardware than lilo.
> > > Can someone disprove me on this?
> >=20
> > On the other hand, lilo "just works" more often than grub in my experie=
nce. =20
> > It didn't always (lord knows I have curses the 'LI' on boot over the=20
> > years), but whenver I have grub problems, a little bit o' lilo always s=
eems=20
> > to fix things.
> >=20
> > Case in point, I have gentoo installed on one of my machines and have h=
ad=20
> > nothing but problems with the default grub installation.  When I search=
 for=20
> > help on the topics, though, I find next to nothing.  The grub "help"=20
> > assumes that everything will work right off the bat.  Since lilo has be=
en=20
> > around so long, there is plenty of "how lilo screwed up and how I fixed=
 it"=20
> > stories.
> >=20
> > I had two very specific problems on this one machine.  The first was th=
at my=20
> > boot partition was formatted with reiserfs (nothing I read said I could=
n't)=20
> > but no matter how hard I tried, I couldn't get grub to recognize that=20
> > partition at all.  Hence, no boot.  Also, couldn't find any messages on=
=20
> > grub mailing lists or gentoo mailing lists about it except to say "it=20
> > should work".
> >=20
> > The second issue finally drove me back to lilo.  grub absolutely REFUSE=
D to=20
> > honor my 'rootnoverify' command that I gave for my Win98 entry.  I know=
 it=20
> > was getting the right boot partition and I know it was reading the menu=
.lst=20
> > file (other changes went through).. but try as I may, I couldn't get it=
 to=20
> > acknowledge that there was a 'rootnoverify (hd0,0)' command there.  Aft=
er=20
> > weeks of having to do manual boots, I finally took two minutes to write=
 a=20
> > lilo.conf file and voila!  everything worked perfectly.
> >=20
> > So yes, grub is cool in theory (and works great on my SuSE 8.1 box) and=
 if=20
> > it works for you, it's certainly handier than lilo for certain things..=
.=20
> > Buf if you want tried and true, lilo is still tops.
> > --=20
> > Kurt Granroth - "KDE -- Conquer Your Desktop"
> > KDE Developer/Evangelist | granroth@kde.org
> > http://www.granroth.org  | kurt@granroth.org
> >=20
> > ---------------------------------------------------
> > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> > To subscribe, unsubscribe, or to change  you mail settings:
> > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>=20
>=20
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change  you mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
--=20
Bryce C <Plug@BryceCo.Net>
CoBryce Communications

--=-uXGO5EEHBlJHUPkasAgA
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQA+FG2S/wbq/C6yyPcRAl6PAKCsIHUfZhU/LGo3ECEYE3SVU4hTJACfdaUB
4pasQNxxi9jjZtHIM9fmfQ4=
=jSaB
-----END PGP SIGNATURE-----

--=-uXGO5EEHBlJHUPkasAgA--