From: Telford002@aol.com
To: <linux-kernel@vger.kernel.org>
Subject: [NFS] Incompatibility with Solaris?
Date: Wed, 30 Jan 2002 16:33:06 EST [thread overview]
Message-ID: <193.1d5ab9f.2989c093@aol.com> (raw)
I installed Suse 7.3 on my workstation and then exported the file
system to a Solaris 2.6 x86 development station.
I executed a build/make script on the Solaris workstation in
a directory tree on the NFS exported file system.
The build/make script creates some symbolic links during
the build process. I notice that the paths to the real
file are sometimes trash. I suspect some sort of RPC
problem with symbolic links. Build/make procedures
that create no symbolic links have no problems.
The Suse 7.3 distribution uses a 2.4.10 kernel.
I tried a 2.4.17 kernel. I received a message
on the Solaris console that the RPC version in
2.4.17 was incompatible.
I have a work around, but it might be worthwhile
to check out.
Note that not every symbolic link created on the
NFS file system during the build procedure is bad,
just a few of them.
Joachim Martillo
next reply other threads:[~2002-01-30 21:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 21:33 Telford002 [this message]
2002-01-30 22:01 ` [NFS] Incompatibility with Solaris? Neil Brown
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=193.1d5ab9f.2989c093@aol.com \
--to=telford002@aol.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