From: Tom McNeal <trmcneal@attbi.com>
To: Tina Arora <tinaarora@hotmail.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: kernel version problem
Date: Fri, 15 Mar 2002 07:55:07 -0800 [thread overview]
Message-ID: <3C92195B.BE165F9E@attbi.com> (raw)
In-Reply-To: DAV20GvQ3C3unebhJHa0000ed31@hotmail.com
2.2.16 is an adequate base to start from, but if you're able
to make bigger changes, and want the best nfs platform for
2.2, then go to 2.2.19.
For 2.2.16, Go to http://nfs.sourceforge.net/ and follow the
link to the download page (containing both the nfs-utils tar
balls and the kernel patches).
You need to apply the kernel-nfs-dhiggen_merge-3.0.tar.gz
download to 2.2.16.
Apply the latest nfs utils download (nfs-utils-0.3.3.tar.gz)
Both have readme files; they'll give you the requirements and
tell you what to do.
Tom McNeal
> 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
--
------------------------------------------------------------
Tom McNeal trmcneal@attbi.com (650)906-0761 (cell)
------------------------------------------------------------
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2002-03-15 15:54 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
2002-03-15 15:55 ` Tom McNeal [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=3C92195B.BE165F9E@attbi.com \
--to=trmcneal@attbi.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