grub-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: grub2 back to lilo ?


From: Vladimir 'φ-coder/phcoder' Serbinenko
Subject: Re: grub2 back to lilo ?
Date: Sat, 15 May 2010 14:07:45 +0200
User-agent: Mozilla-Thunderbird 2.0.0.22 (X11/20091109)

bc w wrote:
> Hi
>
>      I think the problem proposed by this article is very important.
>
>     The article URL is
> http://www.linuxplanet.com/linuxplanet/tutorials/7004/1/
>                               
> http://www.linuxplanet.com/linuxplanet/tutorials/7004/2/
>
>
First of all this list is plain text only. No HTML.
Secondly if you don't like grub.cfg autogeneration you can simply remove
grub-mkconfig and edit grub.cfg manually as much as you want or rather
every time you need it, or rather every time you have any autodetectable
changes.
grub-mkconfig is just a convenience tool meant to have uniform grub.cfg
handling across distributions. But any distribution or user may choose
either to use it or not.
Old way of modifying menu.lst is unsuitable due to grub2 having much
more flexible syntax.
I consider current default way sane and it takes better argument than "I
feel comfortable with XYZ" to change. But it's only a default, feel free
to change on your computer
>     It said
>
> "In the distant past, Linux used a boot loader called lilo. Lilo was a
> pain, because whenever you changed anything, like adding a new kernel,
> you had to reboot into the distro where you originally installed lilo
> to update your disk's boot partition. You couldn't run lilo from
> anywhere else because of version incompatibilities. If you forgot
> which distro was the one allowed to run lilo, you were in trouble.
>
> In 2001, grub changed that -- you could make a small shared partition
> for /boot and update it from anywhere. Huge improvement!
>
> Now, 9 years later, we have grub2 -- and we're back to the bad old
> days of lilo."
>
> "Instead, you're supposed to edit files inside //etc/grub.d/, plus
> another file, //etc/default/grub/. That's all very well ... except
> that those directories aren't accessible to other distros. If you've
> set up grub on your Ubuntu 9.10 partition but you're currently running
> 10.04, or Fedora or Gentoo, what happens if you need to add a new
> grub2 entry? Apparently you're supposed to reboot back to Ubuntu 9.10,
> and lord help you if you forget and accidentally run update-grub from
> some other system. Ouch! Is this a case of "Those who don't remember
> the past are doomed to repeat it?""
>
>
> How can we solve this problem?
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Grub-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/grub-devel
>   


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko


Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]