From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: LVM 1.0 release decision
Date: 11 May 2001 08:42:13 -0700 [thread overview]
Message-ID: <9dh18l$evk$1@cesium.transmeta.com> (raw)
In-Reply-To: <20010511162745.B18341@sistina.com> <E14yDyI-0000yE-00@the-village.bc.nu>
Followup to: <E14yDyI-0000yE-00@the-village.bc.nu>
By author: Alan Cox <alan@lxorguk.ukuu.org.uk>
In newsgroup: linux.dev.kernel
>
> A new format is fine but import old ones properly. And if you do a new format
> stop using kdev_t on disk - it will change size soon
>
Not to mention that it might end up being a pointer, or go away (to be
replaced with kchrdev_t, kblkdev_t or something like that.)
*** kdev_t does not belong in user space or on disk; it is a kernel
transient object. ***
Personally I can't believe this code went into the mainstream kernel
*at all* with this wart in it.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
next prev parent reply other threads:[~2001-05-11 15:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 16:27 LVM 1.0 release decision Heinz J. Mauelshagen
2001-05-11 14:32 ` Alan Cox
2001-05-11 15:11 ` Andrea Arcangeli
2001-05-11 20:12 ` David S. Miller
2001-05-12 1:24 ` Andrea Arcangeli
2001-05-12 1:29 ` David S. Miller
2001-05-12 2:54 ` Andrea Arcangeli
2001-05-12 5:19 ` David S. Miller
2001-05-12 13:39 ` Andrea Arcangeli
2001-05-13 17:36 ` David Woodhouse
2001-05-13 18:39 ` Alan Cox
2001-05-13 23:17 ` Chris Wedgwood
2001-05-13 19:25 ` Christoph Hellwig
2001-05-11 15:42 ` H. Peter Anvin [this message]
2001-05-11 17:02 ` Andreas Dilger
2001-05-16 15:03 ` Heinz J. Mauelshagen
2001-05-16 23:38 ` Alan Cox
2001-05-11 14:39 ` Jeff Garzik
2001-05-11 14:48 ` Mark Hahn
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='9dh18l$evk$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--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