From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: grub2 back to lilo ?
Date: Sat, 15 May 2010 14:07:45 +0200 [thread overview]
Message-ID: <4BEE8E91.2030809@gmail.com> (raw)
In-Reply-To: <AANLkTilXGzpim5IoA4zEsVH9BkTXw9ABllDOARPn5DAh@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2637 bytes --]
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
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
prev parent reply other threads:[~2010-05-15 12:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-15 1:55 grub2 back to lilo ? bc w
2010-05-15 2:32 ` BVK Chaitanya
2010-05-15 7:11 ` Colin Watson
2010-05-15 7:21 ` Marc Haber
2010-05-15 7:41 ` Colin Watson
2010-05-15 8:47 ` Marc Haber
2010-05-15 8:11 ` BVK Chaitanya
2010-05-17 10:40 ` Colin Watson
2010-05-17 11:23 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-05-15 5:13 ` Colin D Bennett
2010-05-15 5:51 ` Bruce Dubbs
2010-05-15 12:07 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BEE8E91.2030809@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.