From: "H. Peter Anvin" <hpa@zytor.com>
To: Greg KH <greg@kroah.com>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
linux-raid@vger.kernel.org, klibc list <klibc@zytor.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [klibc] Exporting which partitions to md-configure
Date: Mon, 30 Jan 2006 19:53:42 -0800 [thread overview]
Message-ID: <43DEDF46.2060505@zytor.com> (raw)
In-Reply-To: <20060131032133.GA8920@kroah.com>
Greg KH wrote:
>
> What are you looking for exactly? udev has a great helper program,
> volume_id, that identifies any type of filesystem that Linux knows about
> (it was based on the ext2 lib code, but smaller, and much more sane, and
> works better.)
>
> Would that help out here?
>
It might, but it's also rather ugly to have two pieces of code,
especially in the presence of very dynamic partitions. In other words,
if the kernel deals with partitions, you want to be able to get at the
kernel's view of partitions, not necessarily the actual set of
partitions on disk, which can be quite different.
-hpa
prev parent reply other threads:[~2006-01-31 3:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 0:52 Exporting which partitions to md-configure H. Peter Anvin
2006-01-31 1:10 ` 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 [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=43DEDF46.2060505@zytor.com \
--to=hpa@zytor.com \
--cc=greg@kroah.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).