All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: klibc list <klibc@zytor.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-raid@vger.kernel.org
Subject: Exporting which partitions to md-configure
Date: Mon, 30 Jan 2006 16:52:08 -0800	[thread overview]
Message-ID: <43DEB4B8.5040607@zytor.com> (raw)

I'm putting the final touches on kinit, which is the user-space 
replacement (based on klibc) for the whole in-kernel root-mount complex. 
   Pretty much the one thing remaining -- other than lots of testing -- 
is to handle automatically mounted md devices.  In order to do that, 
without adding userspace versions of all the paritition code (which may 
be a future change, but a pretty big one) it would be good if the 
partition flag to auto-configure RAID was available in userspace, 
presumably through sysfs.

Any feeling how best to do that?  My current thinking is to export a 
"flags" entry in addition to the current ones, presumably based on 
"struct parsed_partitions->parts[].flags" (fs/partitions/check.h), which 
seems to be what causes md_autodetect_dev() to be called.

Note that this should be available even if md isn't compiled into the 
kernel, thus making it possible to load md as a module before running 
kinit, or to make the equivalent of the kernel mounting sequence from a 
totally runtime user tool.

	-hpa

             reply	other threads:[~2006-01-31  0:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-31  0:52 H. Peter Anvin [this message]
2006-01-31  1:10 ` Exporting which partitions to md-configure Neil Brown
2006-01-31  1:42   ` H. Peter Anvin
2006-01-31  2:01     ` Neil Brown
2006-01-31  2:05       ` H. Peter Anvin
2006-02-06  1:46         ` Neil Brown
2006-02-06  3:29           ` Kyle Moffett
2006-02-07  2:47           ` [klibc] " H. Peter Anvin
2006-02-07  9:03             ` Neil Brown
2006-02-07 10:43             ` Luca Berra
2006-02-07 15:46               ` H. Peter Anvin
2006-02-07 16:47                 ` Luca Berra
2006-02-07 16:55                   ` H. Peter Anvin
2006-02-07 17:03                     ` Luca Berra
2006-01-31  6:49     ` Chris Wedgwood
2006-01-31  1:43   ` Kyle Moffett
2006-01-31  1:45     ` H. Peter Anvin
2006-01-31  2:01     ` Neil Brown
2006-01-31  2:38       ` H. Peter Anvin
2006-01-31  6:42       ` Kyle Moffett
2006-01-31  3:21 ` [klibc] " Greg KH
2006-01-31  3:24   ` Greg KH
2006-01-31  6:53     ` Kyle Moffett
2006-01-31  3:53   ` H. Peter Anvin

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=43DEB4B8.5040607@zytor.com \
    --to=hpa@zytor.com \
    --cc=klibc@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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.