From: Christophe Saout <christophe@saout.de>
To: linux-lvm@sistina.com
Cc: Andrew Morton <akpm@digeo.com>
Subject: Re: [linux-lvm] Re: 2.5.73-mm2
Date: Mon Jun 30 12:29:02 2003 [thread overview]
Message-ID: <1056994136.3782.4.camel@chtephan.cs.pocnet.net> (raw)
In-Reply-To: <20030629103226.GA661@gmx.de>
Am So, 2003-06-29 um 12.32 schrieb Wiktor Wodecki:
> > I think there's a version of devicemapper userspace which works correctly
> > with 64-bit dev_t. Perhaps the Sistina team can shed some light.
>
> would be nice if somebody else could comment on this..
Simply recompiling libdevmapper against the 2.5.7#-mm# kernel headers
helps for now.
But the plan for the future is that the dm ioctl interface will use 64
bit by default, so that it will work with any kernel version.
--
Christophe Saout <christophe@saout.de>
prev parent reply other threads:[~2003-06-30 12:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030627202130.066c183b.akpm@digeo.com>
2003-06-30 9:51 ` [linux-lvm] Re: 2.5.73-mm2 Wiktor Wodecki
2003-06-29 0:30 ` Andrew Morton
2003-06-30 9:51 ` Wiktor Wodecki
2003-06-30 10:23 ` Joe Thornber
2003-06-30 10:41 ` Wiktor Wodecki
2003-06-30 11:41 ` Heinz J . Mauelshagen
2003-06-30 12:29 ` Christophe Saout [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=1056994136.3782.4.camel@chtephan.cs.pocnet.net \
--to=christophe@saout.de \
--cc=akpm@digeo.com \
--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