From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Schmidt, Kenneth P" <kenneth.schmidt@pnl.gov>
Cc: Jan Dittmer <jdi@l4x.org>, Al Viro <viro@ftp.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: FW: [patch 01/02] vfs: variant symlinks
Date: Sat, 29 Sep 2007 17:59:25 -0400 [thread overview]
Message-ID: <1191103165.6655.8.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <C323F837.4E04%kenneth.schmidt@pnl.gov>
On Sat, 2007-09-29 at 12:40 -0700, Schmidt, Kenneth P wrote:
> The best example of how this can be useful is to allow a heterogeneous
> environment which uses a common filesystem. For example, both x86_64 and
> power systems could mount a root nfs share and execute with a common set of
> configurations and data, but the binary directories (bin and lib) could
> point to architecture specific directories.
That would hardly be a portable NFS environment. Boot a Solaris, or
older Linux kernel, and watch your applications barf...
This sort of stuff belongs in the automounter, not the kernel.
Trond
prev parent reply other threads:[~2007-09-29 21:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C323F762.4E00%kenneth.schmidt@pnl.gov>
2007-09-29 19:40 ` Schmidt, Kenneth P
2007-09-29 20:33 ` Al Viro
2007-09-29 21:59 ` Trond Myklebust [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=1191103165.6655.8.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=jdi@l4x.org \
--cc=kenneth.schmidt@pnl.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/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
all inboxes | Powered by JetHome®