public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Christophe Saout <christophe@saout.de>
Cc: dm-devel@sistina.com,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Arjan van de Ven <arjanv@redhat.com>,
	Andries Brouwer <aebr@win.tue.nl>,
	Linus Torvalds <torvalds@osdl.org>
Subject: partition detection in 2.7
Date: Sun, 11 Jan 2004 15:33:47 -0500	[thread overview]
Message-ID: <4001B32B.1030305@pobox.com> (raw)
In-Reply-To: <1073849697.24036.11.camel@leto.cs.pocnet.net>

Christophe Saout wrote:
> The plan for Linux 2.7 is to rip out partition detection from the kernel
> and do everything in userspace (probably initramfs). So someone could
> start by making the partition detection code a library.


Linus just vehementally stated recently that partition parsing wouldn't 
be leaving the kernel :)

However, I do think we will eventually move to a middle ground, where 
partition parsing code will be in the kernel _source_ tree, but it will 
be in initramfs as you describe.

The reason being is that block device attachment and setup is growing 
more complicated over time, as people move to things like dm+lvm2+md or 
iscsi+dm+evms.  Thus, the support code to make those device combinations 
to be used as a root device will get more and more complex.

RAID and device mapper were actually two big reasons why I am pushing 
for klibc (pushed back to 2.7 now) and initramfs in the kernel source 
tree.  LVM, some EFI bits, dm, and md all have boot components are 
mainly in the kernel because they need to happen (a) early and (b) 
always, not because they actually need to be compiled into the kernel 
image itself.

	Jeff




      reply	other threads:[~2004-01-11 20:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-11 15:21 kernel 2.6 biosraid via device mapper - partition support Wilfried Weissmann
2004-01-11 19:34 ` [dm-devel] " Christophe Saout
2004-01-11 20:33   ` Jeff Garzik [this message]

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=4001B32B.1030305@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=aebr@win.tue.nl \
    --cc=arjanv@redhat.com \
    --cc=christophe@saout.de \
    --cc=dm-devel@sistina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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