From: "joe faith" <dzrdmwjx@gmx.com>
To: "The development of GNU GRUB" <grub-devel@gnu.org>
Subject: Re: [RFC] Allow separate boot block and core.img location?
Date: Fri, 17 Jan 2014 07:01:07 -0500 [thread overview]
Message-ID: <20140117120107.316960@gmx.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 688 bytes --]
----- Original Message -----
From: Chris Murphy
Sent: 01/16/14 11:55 PM
To: The development of GNU GRUB
Subject: Re: [RFC] Allow separate boot block and core.img location?
I must be having a problem counting:
1. GRUB
2. unencrypted "boot" for Windows/Truecrypt
3. Truecrypt encrypted "primary" for Windows
4. extended
Chris Murphy
Everyone else may not necessaily have the same requirements as you.
Some of us might want to have a separate partition for data or even additional OSs.
Also, I think I mentioned earlier that TrueCrypt FDE doesn't allow extended/logical partitions (with XP).
How about:
1. Unencrypted boot
2. Windows XP (truecrypt)
3. Windows 7 (truecrypt)
4. Linux root
[-- Attachment #2: Type: text/html, Size: 2068 bytes --]
next reply other threads:[~2014-01-17 12:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 12:01 joe faith [this message]
2014-01-21 18:02 ` [RFC] Allow separate boot block and core.img location? Chris Murphy
2014-01-22 14:56 ` Vladimir 'φ-coder/phcoder' Serbinenko
-- strict thread matches above, loose matches on Subject: below --
2014-01-17 2:13 joe faith
2014-01-17 4:55 ` Chris Murphy
2014-01-16 16:56 joe faith
2013-12-19 16:31 joe fresh
2013-12-19 18:18 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-19 22:54 ` Chris Murphy
2013-12-19 10:28 joe fresh
2013-12-19 14:34 ` Lennart Sorensen
2014-01-16 21:04 ` Chris Murphy
2013-12-16 19:36 Andrey Borzenkov
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=20140117120107.316960@gmx.com \
--to=dzrdmwjx@gmx.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.