From: Christoph Hellwig <hch@caldera.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-lvm@sistina.com, Alexander Viro <viro@math.psu.edu>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org
Subject: Re: [linux-lvm] Re: [RFLART] kdev_t in ioctls
Date: Mon, 14 Jan 2002 19:45:54 +0100 [thread overview]
Message-ID: <20020114194554.A5885@caldera.de> (raw)
In-Reply-To: <20020114191342.A3731@caldera.de> <E16QCHl-0002XJ-00@the-village.bc.nu>
In-Reply-To: <E16QCHl-0002XJ-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Mon, Jan 14, 2002 at 06:56:44PM +0000
On Mon, Jan 14, 2002 at 06:56:44PM +0000, Alan Cox wrote:
> > > Glibc disagrees with you (bits/types.h):
> > >
> > > typedef __u_quad_t __dev_t; /* Type of device numbers. */
> > >
> > > We'd have to use __kernel_dev_t instead which again pulls kernel
> > > headers in..
> >
> > Argg. That's also non-funny:
>
> glibc is meant to disagree. glibc provides a virtualised dev_t to user space
> so that the kernel one can be expanded in future without application
> breakage.
I know - still it makes Linus' suggestion not work on ~90% of the
systems.
next prev parent reply other threads:[~2002-01-14 18:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 17:56 [RFLART] kdev_t in ioctls Alexander Viro
2002-01-14 18:01 ` Linus Torvalds
2002-01-13 17:17 ` [linux-lvm] " Joe Thornber
2002-01-14 18:08 ` Christoph Hellwig
2002-01-14 18:13 ` Christoph Hellwig
2002-01-14 18:56 ` Alan Cox
2002-01-14 18:45 ` Christoph Hellwig [this message]
2002-01-14 18:50 ` Linus Torvalds
2002-01-14 18:20 ` Alexander Viro
-- strict thread matches above, loose matches on Subject: below --
2002-01-15 20:44 [linux-lvm] " Andries.Brouwer
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=20020114194554.A5885@caldera.de \
--to=hch@caldera.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lvm@sistina.com \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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