From: James Pearson <james-p@moving-picture.com>
To: Tina Arora <tinaarora@hotmail.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: kernel version problem
Date: Fri, 15 Mar 2002 10:17:01 +0000 [thread overview]
Message-ID: <3C91CA1D.9F779A29@moving-picture.com> (raw)
In-Reply-To: DAV20GvQ3C3unebhJHa0000ed31@hotmail.com
> Tina Arora wrote:
>
> hi,
> nfs.soureforge.net talks of kernel version atleast 2.2.18 to use nfs
> version 3 .My system shows
> "Red Hat Linux release 7.0(Guinness)
> Kernel 2.2.16-22 on i686"
> Nebody ne clues what this -22 means and also will i be able to use nfs
> (3) on this system of mine..
> thanx
> Tina
If you don't want to build your own kernel, then there are a couple of
things you could do:
Upgrade to RedHat 7.2 - which has a 2.4.X kernel plus everything else
you need to use NFSv3.
If you can't upgrade to RedHat 7.2, then the latest RedHat update kernel
for RedHat 7.0 is 2.2.19-7.0.15. I have no idea if this kernel does
support NFSv3, but I guess it does. (RedHat make a number of
additions/modifications to a standard kernel - the number after the '-'
is added by RedHat and probably means something like the 15th build of a
RH kernel based on 2.2.19 for RH 7.0). Download from:
ftp://updates.redhat.com/7.0/en/os/i686/
The RedHat support site should have instructions on how to upgrade a RH
kernel.
You will probably still have to update the nfs-utils (and mount?) as per
the FAQ.
James Pearson
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-03-15 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 11:08 kernel version problem Tina Arora
2002-03-15 10:17 ` James Pearson [this message]
2002-03-15 15:55 ` Tom McNeal
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=3C91CA1D.9F779A29@moving-picture.com \
--to=james-p@moving-picture.com \
--cc=nfs@lists.sourceforge.net \
--cc=tinaarora@hotmail.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