From: Christoph Hellwig <hch@ns.caldera.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] A Caldera related bug?
Date: Thu, 30 Aug 2001 18:11:47 +0200 [thread overview]
Message-ID: <20010830181147.A22657@caldera.de> (raw)
In-Reply-To: <20010830160347.A700@btconnect.com>; from thornber@btconnect.com on Thu, Aug 30, 2001 at 04:03:48PM +0100
On Thu, Aug 30, 2001 at 04:03:48PM +0100, Joe Thornber wrote:
> On Thu, Aug 30, 2001 at 02:16:31PM +0200, Christoph Hellwig wrote:
> > On Thu, Aug 30, 2001 at 12:09:29PM +0100, Joe Thornber wrote:
> > > On Thu, Aug 30, 2001 at 11:46:13AM +0200, Christoph Hellwig wrote:
> > > > On Thu, Aug 30, 2001 at 03:23:21AM -0600, Andreas Dilger wrote:
> > > > > In the end, what is really needed is a well-defined LVM API between
> > > > > kernel and user-space that doesn't pass this kind of stuff.
> > > >
> > > > Completly agreed.
> > >
> > > I think every one is aware of this, but we can't change the interface during
> > > the 2.4 series.
> >
> > Well, you change it all over the time..
> > IMHO replacing all these kernel types in the structures also used by the
> > tools to others that have the same size but do not depend on kernel headers
> > would be a very good thing for 1.0.2.
>
> ok, I'll look at them. I can't see how we can get rid of the kdev_t's
> though.
#ifdef __KERNEL__
#include <linux/kdev_t.h>
typedef kdev_t lvm_dev_t;
#else
typedef uint16_t lvm_dev_t;
#endif
and s/kdev_t/lvm_dev_t/g in lvm.h.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2001-08-30 16:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-29 23:04 [linux-lvm] A Caldera related bug? dan_mcmanus
2001-08-30 7:08 ` Christoph Hellwig
2001-08-30 9:23 ` Andreas Dilger
2001-08-30 9:37 ` Patrick Caulfield
2001-08-30 9:46 ` Christoph Hellwig
2001-08-30 11:09 ` Joe Thornber
2001-08-30 12:16 ` Christoph Hellwig
2001-08-30 15:03 ` Joe Thornber
2001-08-30 16:11 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-30 16:38 dan_mcmanus
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=20010830181147.A22657@caldera.de \
--to=hch@ns.caldera.de \
--cc=linux-lvm@sistina.com \
/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