From: Chris Wedgwood <cw@f00f.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: David Woodhouse <dwmw2@infradead.org>,
"David S. Miller" <davem@redhat.com>,
Andrea Arcangeli <andrea@suse.de>,
Mauelshagen@sistina.com, linux-kernel@vger.kernel.org,
mge@sistina.com, hch@caldera.de
Subject: Re: LVM 1.0 release decision
Date: Mon, 14 May 2001 11:17:39 +1200 [thread overview]
Message-ID: <20010514111739.A11330@metastasis.f00f.org> (raw)
In-Reply-To: <23605.989775371@redhat.com> <E14z0mG-0006og-00@the-village.bc.nu>
In-Reply-To: <E14z0mG-0006og-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Sun, May 13, 2001 at 07:39:36PM +0100
On Sun, May 13, 2001 at 07:39:36PM +0100, Alan Cox wrote:
Or the 32bit libc shipped with the 64bit box. Lets face it, there
is no reason you can't have a 32bit glibc 2.2 built to use 64bit
calling conventions..
It doesn't work with binary compatability form other sources (e.g.
trying to run SunOS binaries under ultralinux and such like (I assume
this is possible?)). Then again, should SunOS binaries really be
making such ioctls?
--cw
next prev parent reply other threads:[~2001-05-13 23:18 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 [this message]
2001-05-13 19:25 ` Christoph Hellwig
2001-05-11 15:42 ` H. Peter Anvin
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=20010514111739.A11330@metastasis.f00f.org \
--to=cw@f00f.org \
--cc=Mauelshagen@sistina.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrea@suse.de \
--cc=davem@redhat.com \
--cc=dwmw2@infradead.org \
--cc=hch@caldera.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mge@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