From: Theodore Tso <tytso@mit.edu>
To: Hannes Reinecke <hare@suse.de>
Cc: Seewer Philippe <philippe.seewer@bfh.ch>,
Bernhard Walle <bwalle@suse.de>,
Christoph Hellwig <hch@infradead.org>,
initramfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Kay Sievers <kay.sievers@vrfy.org>, Dave Jones <davej@redhat.com>,
cjwatson@ubuntu.com, Bernhard Walle <bwalle@novell.com>
Subject: Re: Dracut -- Cross distribution initramfs infrastructure
Date: Fri, 19 Dec 2008 10:27:08 -0500 [thread overview]
Message-ID: <20081219152708.GE9871@mit.edu> (raw)
In-Reply-To: <494BA7CE.2020007@suse.de>
On Fri, Dec 19, 2008 at 02:55:26PM +0100, Hannes Reinecke wrote:
>
> The goal of the initrd is to activate and mount the root fs.
> And the root fs _only_. Every other system should be configured
> once the main system is running.
Don't forget resuming from hibernation....
And of course, activating and mounting the root filesystem can be
quite complicated --- it can involve loading driver modules,
activiating md and/or lvm, prompting for a password, setting up
networking (dhcp, routing, dns) for iSCSI and/or NFS/AFS/Lustre/et.al,
the equivalent setup for Fiber Channel attached disks, etc. If
there's any cryptography involved, the user may need to be prompted
for a password and/or key and/or fingerprint scan to unlock TPM unit
to access the key, etc.
There may also be times when it is useful to operate on the root
filesystem in some way before it is mounted; in most cases the
operation can bedone on a filesystem mounted read-only, yes --- but at
the cost of needing to reboot afterwards if the root filesystem needs
to be modified by said userspace tool.
Finally, note that part the discussion at the Kernel Summit, and also
what David Jones was looking to work at, was to do something that
could included as part of the kernel sources. The idea is that as
responsibility for early boot is moved from the kernel, an mkinitramfs
which is fixed and distributed by the distribution might not work with
a newer kernel.org kernel. So the idea that was explored was adding a
common mkinitramfs with basic functionality into kernel sources, with
the ability for distributions to add various "value add" enhancements
if they like. This way if the kernel wants to move more functionality
(for example, in the area of resuming from hibernation) out of the
kernel into initramfs, it can do so without breaking the ability of
older distributions from being able to use kernel.org kernels.
So IMHO, it's important not only that the distributions standardize on
a single initramfs framework, but that framework get integrated into
the kernel sources.
Regards,
- Ted
next prev parent reply other threads:[~2008-12-19 15:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 18:54 Dracut -- Cross distribution initramfs infrastructure Jeremy Katz
2008-12-17 19:07 ` Christoph Hellwig
2008-12-18 7:36 ` Hannes Reinecke
2008-12-19 7:41 ` Seewer Philippe
2008-12-19 8:18 ` Bernhard Walle
2008-12-19 13:55 ` Hannes Reinecke
2008-12-19 15:27 ` Theodore Tso [this message]
2008-12-19 16:56 ` Jeremy Katz
2008-12-20 13:50 ` Daniel Pittman
2008-12-20 18:22 ` Dave Jones
2009-01-07 16:04 ` Hannes Reinecke
2008-12-17 19:31 ` Neil Horman
2008-12-18 9:27 ` Loïc Grenié
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=20081219152708.GE9871@mit.edu \
--to=tytso@mit.edu \
--cc=bwalle@novell.com \
--cc=bwalle@suse.de \
--cc=cjwatson@ubuntu.com \
--cc=davej@redhat.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=initramfs@vger.kernel.org \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=philippe.seewer@bfh.ch \
/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