From: Boaz Harrosh <bharrosh@panasas.com>
To: Steve Dickson <steved@redhat.com>, NFS list <linux-nfs@vger.kernel.org>
Subject: Regarding the Fedora 15 nfs-utils--pnfs RPM
Date: Thu, 3 Nov 2011 11:31:51 -0700 [thread overview]
Message-ID: <4EB2DE17.7030005@panasas.com> (raw)
Hi Steve
On your pnfs site here:
http://steved.fedorapeople.org/repos/pnfs/15/x86_64/rpms/
You have this RPM:
nfs-utils-1.2.3-10.pnfs.fc15.x86_64.rpm
It was all well and on any live system we could just do:
yum localinstall nfs-utils-1.2.3-10.pnfs.fc15.x86_64.rpm
(Or even better put it on our Cobbler server)
But recently Fedora 15 updated to:
nfs-utils-1.2.4-1.fc15.x86_64.rpm
And the above localinstall no longer works (Version math)
The nfs-utils-1.2.4-1 needs to be removed and the nfs-utils-1.2.3-10.pnfs
installed, but on every update it wants to be replaced.
Could you please bump up the pnfs RPM version so it will be higher
then FC15's ?
On a side note. Can we put the pNFSD-server supporting bits in nfs-utils
even though the pNFSD-server is not yet in Kernel. Like parse the pnfs
option in /etc/exports but ignore if not supported by Kernel?
I mean what will we do in the future when a new nfs-utils boots with an old
Kernel? can we do the same now?
Thanks
Boaz
reply other threads:[~2011-11-03 18:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4EB2DE17.7030005@panasas.com \
--to=bharrosh@panasas.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.