Linux LVM users
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@ns.caldera.de>
To: Andreas Dilger <adilger@turbolinux.com>
Cc: bluca@comedia.it, linux-lvm@msede.com
Subject: Re: [linux-lvm] Re: more LVM 0.8 patches
Date: Tue, 24 Oct 2000 18:25:02 +0200	[thread overview]
Message-ID: <20001024182502.A17195@caldera.de> (raw)
In-Reply-To: <200010231800.e9NI01U21435@webber.adilger.net>; from adilger@turbolinux.com on Mon, Oct 23, 2000 at 12:00:01PM -0600

On Mon, Oct 23, 2000 at 12:00:01PM -0600, Andreas Dilger wrote:
> Luca Berra writes:
> > hello here are more lvm patches.
> > they apply over patches in lvm-0.8final-3.3.src.rpm
> > 1st chunk is needed to compile on my system
> 
> Actually, this is a bit of a problem.  In my 2.2 kernel patch, I include an
> lvm.h that can be used for both user and kernel compiles, so that you are
> sure you have the same IOP version, struct sizes, etc.  However, this lvm.h
> doesn't exist on 2.4.

IMHO this is the wrong thing. Userlevel tools should not include kernel headers.
IOP version mismatches are detected at run time.
In my RPMs I keep including the userlevel header and it works fine for Linux 2.2
and 2.4. The RPMs do also include most fixes by Andreas and from this list
(Luca's have just been added). If anyone is interested, they can be found on
	
  ftp.openlinux.org:/pub/people/hch/lvm/lvm-tools-0.8final-5.src.rpm
  ftp.openlinux.org:/pub/people/hch/lvm/lvm-tools-0.8final-5.i386.rpm (Glibc 2.1.94)


	Christoph

-- 
Always remember that you are unique.  Just like everyone else.

  reply	other threads:[~2000-10-24 16:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-22 14:22 [linux-lvm] more LVM 0.8 patches Luca Berra
2000-10-23 13:08 ` Paul Jakma
2000-10-23 18:00 ` [linux-lvm] " Andreas Dilger
2000-10-24 16:25   ` Christoph Hellwig [this message]
2000-10-24 18:47     ` Andreas Dilger
2000-10-31  7:36   ` Luca Berra

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=20001024182502.A17195@caldera.de \
    --to=hch@ns.caldera.de \
    --cc=adilger@turbolinux.com \
    --cc=bluca@comedia.it \
    --cc=linux-lvm@msede.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