From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Full disk encryption
Date: Thu, 1 Dec 2011 08:47:27 +0000 [thread overview]
Message-ID: <20111201084727.3076a3a9@hactar.digimed.co.uk> (raw)
In-Reply-To: <20111201002706.5a77f2fd@karnak.local>
[-- Attachment #1: Type: text/plain, Size: 1327 bytes --]
On Thu, 1 Dec 2011 00:27:06 +0000, David W Noon wrote:
> > Why not mount root read-only, just like in a non-initramfs system?
> >
> > Any e2fsck commands will be run during the boot runlevel, before
> > remounting root rw.
>
> Unfortunately, the system does not work that way. When running inside
> an initramfs, one cannot load executable content from mount points --
> only from within the initramfs. So, while it is perfectly possible to
> do "ls /mnt/root/sbin/e2fsck" (assuming the root partition has been
> mounted ro as /mnt/root), it is not possible to load and execute that
> program. [And, yes, I have adjusted the PATH and LD_LIBRARY_PATH shell
> variables to address the program and library directories on the mounted
> root partition.] After performing a switch_root to the actual root
> partition, this restriction is lifted.
I understand that, but not why you need to run e2fsck before the
switch_root. Is this to do with the way your system is set up? The object
of the initramfs is only to get the system into a state where / can be
mounted and switch_root run, I assume you are trying to do more than that
with it.
--
Neil Bothwick
WORM: (n.) acronym for Write Once, Read Mangled. Used to describe a
normally-functioning computer disk of the very latest design.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-12-01 8:48 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 [this message]
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
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=20111201084727.3076a3a9@hactar.digimed.co.uk \
--to=neil@digimed.co.uk \
--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