From: Christoph Hellwig <hch@caldera.de>
To: Kevin Corry <corryk@us.ibm.com>
Cc: evms-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: gendisk list access (was: [Evms-devel] Unresolved symbols)
Date: Wed, 5 Dec 2001 23:38:29 +0100 [thread overview]
Message-ID: <20011205233829.A11547@caldera.de> (raw)
In-Reply-To: <OFCE7B6713.9A6E1AF1-ON85256B02.004FB1C4@raleigh.ibm.com> <01120514525902.13647@boiler> <20011205225346.A7313@caldera.de> <01120516183303.13647@boiler>
In-Reply-To: <01120516183303.13647@boiler>; from corryk@us.ibm.com on Wed, Dec 05, 2001 at 04:18:33PM -0600
On Wed, Dec 05, 2001 at 04:18:33PM -0600, Kevin Corry wrote:
> > a block device and a partition.
> >
> > Hope this helps..
>
> Sounds good. Any chance you could just leave out the partitioning stuff and
> let EVMS handle it?
You know my opinion to EVMS - so I'd rather avoid makeing it mandatory.
But if the 2.5 actually looks then like I expect it now partitioning code
will be much simpler than - all code dealing with ondisk formats will
be in early, pre-mount-root userspace, based on Andries Brouwer's partx
(part of util-linux).
> I must have missed your walk_gendisk() patch the last time (do you remember
> how long ago you posted that?).
It was on Nov, 12 - but it was in a private thread that only started on
evms-devel. So Mark was the only EVMS person that got it. Sorry for
the confusion.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2001-12-05 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OFCE7B6713.9A6E1AF1-ON85256B02.004FB1C4@raleigh.ibm.com>
[not found] ` <20011112173217.A3404@caldera.de>
2001-12-05 20:52 ` gendisk list access (was: [Evms-devel] Unresolved symbols) Kevin Corry
2001-12-05 21:53 ` Christoph Hellwig
2001-12-05 22:18 ` Kevin Corry
2001-12-05 22:38 ` Christoph Hellwig [this message]
2001-12-11 12:36 ` Andrew Clausen
2001-12-15 10:58 ` Christoph Hellwig
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=20011205233829.A11547@caldera.de \
--to=hch@caldera.de \
--cc=corryk@us.ibm.com \
--cc=evms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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