All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Legacy GRUB to GRUB2
Date: Thu, 21 Jul 2011 13:31:55 +0200	[thread overview]
Message-ID: <4E280E2B.7000808@gmail.com> (raw)
In-Reply-To: <CAELHeEfvRTBD_gfzi4ez0m0Az+SrXS5Uk3Ed-cv1F3unH_eZ5w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]

This message is obviously a trolling one in an attempt to start 2
flamewars. Since both topics have been previously widely discussed on
this ML, consider this thread closed.
On 21.07.2011 13:20, Brendan Trotter wrote:
> Hi,
>
> On Thu, Jul 21, 2011 at 2:44 PM, Yash Jain <yash2learn@gmail.com> wrote:
>> Could you please let me know how can i upgrade to GRUB2(because
>> trusted GRUB is based on legacy GRUB) or it is still fine if i can use
>> the legacy GRUB to load kernel 2.6.37.
> I'm still using GRUB-legacy with "linux-2.6.38-gentoo-r6", and it
> works perfectly. I'm not using any patches provided by GRUB-IMA, but I
> doubt Linux developers have changed anything that would break those
> patches (or any other boot loader that supports Linux), and I doubt
> there's any reason for you to switch to GRUB2 in the short term.
>
> In the longer term, eventually you'll need to switch to a boot loader
> that supports UEFI (the firmware/BIOS that GRUB-legacy relies on is
> slowly being deprecated). For Linux your choices are limited to GRUB2
> and ELILO, and neither of these boot loaders have any support for
> ensuring boot files haven't been tampered with. If you have a strict
> requirement for that (e.g. Dept. of Defence or something), then you
> may have no choice but to switch to an OS that cares more about your
> security than the freedom of malicious attackers.
>
>
> Cheers,
>
> Brendan
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>


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



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

      reply	other threads:[~2011-07-21 11:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-20 11:52 Legacy GRUB to GRUB2 Yash Jain
2011-07-20 14:18 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-07-21  5:14 ` Fwd: " Yash Jain
2011-07-21 11:03   ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-07-21 11:20   ` Brendan Trotter
2011-07-21 11:31     ` 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=4E280E2B.7000808@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.