From: James Pearson <james-p@moving-picture.com>
To: Matt Schillinger <mschilli@vss.fsi.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Typo in Redhat 8/9 nfs start/stop script
Date: Fri, 20 Jun 2003 15:30:23 +0100 [thread overview]
Message-ID: <3EF31A7F.10E41E79@moving-picture.com> (raw)
In-Reply-To: 1056116269.18560.5.camel@mosix
Matt Schillinger wrote:
...
> Also, 2.4.20.. would it be better for me to use that as opposed to
> 2.4.19? I use a vanilla kernel with an NFSD patch that creates a
> workaround for an IRIX < 6.5.13 CWD bug. If it is recommended to go to
> 2.4.20, does anyone know if that patch is available for 2.4.20?
> Actually, I've forgotten my source for that patch, so if anyone knows
> the address, i'd greatly appreciate recieving that info.
...
If that's the patch/hack I did - from:
ftp://ftp.moving-picture.com/private/james/linux-2.4.19-nfsfh.patch
then it should work OK with 2.4.20 and 2.4.21
James Pearson
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-06-20 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 20:50 Typo in Redhat 8/9 nfs start/stop script pwitting
2003-06-20 13:37 ` Matt Schillinger
2003-06-20 14:30 ` James Pearson [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-23 17:55 pwitting
2003-06-24 12:19 ` Steve Dickson
2003-06-20 14:39 pwitting
2003-06-19 19:27 Matt Schillinger
2003-06-21 12:51 ` Steve Dickson
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=3EF31A7F.10E41E79@moving-picture.com \
--to=james-p@moving-picture.com \
--cc=mschilli@vss.fsi.com \
--cc=nfs@lists.sourceforge.net \
/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.