From: Michael Gorven <michael@gorven.za.net>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Current state of grub2 encryption support
Date: Tue, 31 Mar 2009 10:15:44 +0200 [thread overview]
Message-ID: <200903311015.52766.michael@gorven.za.net> (raw)
In-Reply-To: <49D1CB39.2080309@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
On Tuesday 31 March 2009 09:50:17 phcoder wrote:
> Michael Gorven wrote:
> > On Tuesday 31 March 2009 04:48:02 steve wrote:
> >> Update, i was able to get the right modules to load into a core.img by
> >> making the encrypted partition start at 1mb instead of 32.5kb, the
> >> modules loaded into core.img were:
> >
> > Nice! I briefly looked at getting everything into core.img, but it seemed
> > impossible. That's a nice solution though.
>
> How big is the smallest core.img you could get? Have you tried applying
> my bootmove patch?
I don't know about your bootmove patch. What does it do and where can I find
it?
Michael
--
http://michael.gorven.za.net
PGP Key ID 6612FE85
S/MIME Key ID AAF09E0E
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-03-31 8:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-29 19:54 Current state of grub2 encryption support steve
2009-03-30 11:06 ` Michael Gorven
2009-03-31 1:56 ` steve
2009-03-31 2:48 ` steve
2009-03-31 7:45 ` Michael Gorven
2009-03-31 7:50 ` phcoder
2009-03-31 8:15 ` Michael Gorven [this message]
2009-03-31 8:50 ` phcoder
2009-03-31 10:52 ` Michael Gorven
2009-03-31 12:44 ` phcoder
2009-04-05 20:52 ` crypto space considerations (Re: Current state of grub2 encryption support) phcoder
-- strict thread matches above, loose matches on Subject: below --
2009-03-28 22:52 Current state of grub2 encryption support steve
2009-03-29 7:17 ` Michael Gorven
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=200903311015.52766.michael@gorven.za.net \
--to=michael@gorven.za.net \
--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.