From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Full disk encryption
Date: Fri, 2 Dec 2011 14:10:55 -0500 [thread overview]
Message-ID: <CA+czFiA9gNHjEDR-gN=5jyQo6Ryggm89hvPoOxnpmW9VRDXD3g@mail.gmail.com> (raw)
In-Reply-To: <20111202185855.58148ea5@karnak.local>
On Fri, Dec 2, 2011 at 1:58 PM, David W Noon <dwnoon@ntlworld.com> wrote:
> On Fri, 2 Dec 2011 08:55:35 +0700, Pandu Poluan wrote about Re:
> [gentoo-user] Re: Full disk encryption:
>
>> On Dec 1, 2011 3:32 AM, "David W Noon" <dwnoon@ntlworld.com> wrote:
>> > I have a working initramfs layout, but currently it is too large
>> > (>32MiB) for my /boot partition. The problem package is e2fsprogs,
>> > as it requires dynamic linkage and, consequently, a full-sized
>> > glibc. This sucks, so I need to patch the Makefile(s) to build a
>> > more sensible set of executables for an initramfs.
> [snip]
>> You know, Debian has an e2fsck-static package. Why don't Gentoo, I
>> wonder...
>>
>> That said, you *can* have an "almost-static" e2fsck if you compile it
>> yourself.
>
> Clearly you have not tried this yourself. [I have.]
>
> The reason modern e2fsprogs no longer have the static option is that
> the Makefile logic has long been neglected for the static modules and
> they no longer build correctly to produce e2fsck.static. I am
> currently (on and off) building a patched Makefile to correct this, but
> the build is so convoluted that it is something of a chore.
I like Gentoo because I'm a perpetual edge case. This and mdev makes
two edge-case things you're tackling in your spare time that I know
of...Drop me a line if you're ever in the vicinity of Grand Rapids,
MI. I'll buy you a beer.
--
:wq
next prev parent reply other threads:[~2011-12-02 19:12 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 15:19 [gentoo-user] Full disk encryption czernitko
2011-11-30 15:27 ` Neil Bothwick
2011-11-30 15:40 ` czernitko
2011-11-30 15:48 ` Felix Kuperjans
2011-11-30 16:01 ` czernitko
2011-11-30 18:04 ` [gentoo-user] " Jack Byer
2011-11-30 18:31 ` Dale
2011-11-30 18:44 ` Neil Bothwick
2011-11-30 19:50 ` Dale
2011-11-30 20:19 ` czernitko
2011-11-30 21:45 ` Neil Bothwick
2011-11-30 19:38 ` [gentoo-user] " Jack Byer
2011-12-01 4:21 ` Dale
2011-12-01 5:07 ` [gentoo-user] " Jack Byer
2011-12-01 5:38 ` Dale
2011-11-30 20:28 ` [gentoo-user] " David W Noon
2011-11-30 21:47 ` Neil Bothwick
2011-11-30 22:07 ` David W Noon
2011-11-30 23:26 ` Neil Bothwick
2011-12-01 0:27 ` David W Noon
2011-12-01 0:36 ` Dale
2011-12-01 0:39 ` Michael Mol
2011-12-01 1:23 ` David W Noon
2011-12-01 16:41 ` Michael Mol
2011-12-01 23:00 ` David W Noon
2011-12-01 8:47 ` Neil Bothwick
2011-12-01 13:43 ` David W Noon
2011-12-01 14:03 ` Neil Bothwick
2011-12-01 14:13 ` Dale
2011-12-01 15:02 ` Neil Bothwick
2011-12-02 22:00 ` David W Noon
2011-12-02 23:24 ` Neil Bothwick
2011-12-03 0:44 ` David W Noon
2011-12-03 8:41 ` Neil Bothwick
2011-12-01 2:46 ` [gentoo-user] " Jack Byer
2011-12-02 1:55 ` [gentoo-user] " Pandu Poluan
2011-12-02 18:58 ` David W Noon
2011-12-02 19:10 ` Michael Mol [this message]
2011-12-02 21:37 ` [gentoo-user] Beers in Michigan (was: " David W Noon
2011-11-30 18:32 ` [gentoo-user] " czernitko
2011-11-30 18:50 ` Aljosha Papsch
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='CA+czFiA9gNHjEDR-gN=5jyQo6Ryggm89hvPoOxnpmW9VRDXD3g@mail.gmail.com' \
--to=mikemol@gmail.com \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox