From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Legacy GRUB to GRUB2
Date: Wed, 20 Jul 2011 16:18:04 +0200 [thread overview]
Message-ID: <4E26E39C.5090602@gmail.com> (raw)
In-Reply-To: <CAJnayPBc3yz36=SM2-H+cNPd4-Ra0P5A3R6K1xxK=u_+2bnwvg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]
On 20.07.2011 13:52, Yash Jain wrote:
> Hello All,
> I am using a legacy grub boot-loader with patches provided by GRUB-IMA
> for software integrity and also i am using trusted GRUB for few
> families.
Treacherous GRUB isn't our software. Moreover it puts your freedom in
danger. For more info http://www.gnu.org/philosophy/can-you-trust.html.
> Now i have to upgrade it to the advanced kernel(2.6.37) which will be
> loaded on ext4 DOM,
> 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.
Grab the tarball, then ./configure && make && sudo make install && sudo
grub-install /dev/sdX, replace X with boot drive. You can either reuse
your GRUB legacy config by putting following in grub.cfg:
legacy_source /boot/grub/menu.lst
Or generate modern grub.cfg with
grub-mkconfig -o /boot/grub/grub.cfg
> and also could you let me know that how can i build the legacy GRUB on
> a 64bit machine - when ever i try to build it gives me a error "error:
> GRUB requires a working absolute objcopy; upgrade your binutils".
We don't support GRUB Legacy anymore.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2011-07-20 14:18 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 [this message]
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
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=4E26E39C.5090602@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.