From: David Howells <dhowells@redhat.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Linux Filesystem Development <linux-fsdevel@vger.kernel.org>,
Steve Dickson <SteveD@redhat.com>
Subject: Re: NFS4 mount problem
Date: Mon, 18 Apr 2005 16:23:27 +0100 [thread overview]
Message-ID: <6311.1113837807@redhat.com> (raw)
In-Reply-To: <1113835758.10382.13.camel@lade.trondhjem.org>
Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
> Without such a library, it is pointless to contemplate "other callers".
> With such a library, you will have a single point for switching between
> 32bit and 64 bit.
"Other callers" include such as busybox, sash and uClinux. I'm not sure about
such as Perl, but Perl is hardly in the same class as the other three.
Admittedly, a library is probably the right way to do it - libmount or some
such thing.
> Then can we kill the PPC64 binary structure and substitute PPC32?
Whilst I might be happy to, I'm not sure I can speak for everyone. You can
also use i386 mount on x86_64 for instance; and possibly s390 on s390x,
sparc32 on sparc64 and mips32 on mips64.
David
next prev parent reply other threads:[~2005-04-18 15:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 11:57 NFS4 mount problem David Howells
2005-04-15 12:21 ` Stephen Rothwell
2005-04-15 19:51 ` Bryan Henderson
2005-04-15 20:22 ` David S. Miller
2005-04-15 22:07 ` Bryan Henderson
2005-04-17 13:55 ` Christoph Hellwig
2005-04-18 17:07 ` Bryan Henderson
2005-04-18 17:16 ` Al Viro
2005-04-18 17:33 ` David Howells
2005-04-18 17:43 ` Al Viro
2005-04-18 17:52 ` Bryan Henderson
2005-04-18 10:36 ` David Howells
2005-04-18 18:37 ` David S. Miller
2005-04-17 19:33 ` Trond Myklebust
2005-04-18 17:17 ` Bryan Henderson
2005-04-18 17:59 ` Trond Myklebust
2005-04-20 10:57 ` Andries Brouwer
2005-04-18 10:34 ` David Howells
2005-04-18 14:49 ` Trond Myklebust
2005-04-18 22:07 ` Bryan Henderson
2005-04-18 23:34 ` Trond Myklebust
2005-04-18 15:23 ` David Howells [this message]
2005-04-18 15:45 ` Trond Myklebust
2005-04-18 21:50 ` Bryan Henderson
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=6311.1113837807@redhat.com \
--to=dhowells@redhat.com \
--cc=SteveD@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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;
as well as URLs for NNTP newsgroup(s).