Linux NFS development
 help / color / mirror / Atom feed
From: James Pearson <james-p@moving-picture.com>
To: Tom McNeal <trmcneal@attbi.com>
Cc: NFS maillist <nfs@lists.sourceforge.net>
Subject: Re: Linux release of nfs-utils version 1.0.1
Date: Wed, 24 Jul 2002 17:49:57 +0100	[thread overview]
Message-ID: <3D3EDAB5.9721CEAE@moving-picture.com> (raw)
In-Reply-To: 3D38AD37.640212C9@attbi.com

I notice that the NFS HOW-TO at LDP has now been updated - any chance
the version at http://nfs.sourceforge.net/nfs-howto be updated as well?

James Pearson

Tom McNeal wrote:
> 
> Hi -
> 
> The latest release of the nfs utils package has just been posted
> on https://sourceforge.net/projects/nfs/
> 
> The last version of the package was posted last September, so there
> are quite a few fixes in it.  The one which you may notice right
> away is that synchronous IO is now a default export characteristic,
> falling in line with all other vendors of NFS.  In order to ease
> the transition, a warning will be posted if you do not specify either
> "sync" or "async" in the export list.  This removes a possible
> source of undetected data corruption, as detailed in the NFS howtos.
> 
> Speaking of the howtos, the latest versions of them have been sent
> to the LDP, so they should be posted sometime next week.
> 
> Finally, if you are interested, I have published the client based
> test package I used for testing the utils, which contains a GUI
> interface, and includes Connectathon, FSX, Bonnie++, and IOzone,
> among other things.  The package was originally developed by
> Bruce Blinn and Adrian Drzewiecki at the Mission Critical Linux
> West Coast Office.  I received permission from the owners of the
> assets of MCLX to post the package, after removing all parts
> related to the MCLX cluster software.  You can find it at
> https://sourceforge.net/projects/nfstestmatrix
> 
> One final note - I was not the only tester; Engineers at Red Hat
> and IBM, among others, were involved in the testing, so my Intel
> based UP machines were not the only ones exercising it.
> 
> Regards -
> 
> Tom McNeal
> 
> --
> ------------------------------------------------------------
> Tom McNeal       trmcneal@attbi.com     (650)906-0761 (cell)
> ------------------------------------------------------------
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> NFS maillist  -  NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

       reply	other threads:[~2002-07-24 16:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3D38AD37.640212C9@attbi.com>
2002-07-24 16:49 ` James Pearson [this message]
2002-07-31 17:41   ` Linux release of nfs-utils version 1.0.1 Tom McNeal
2002-07-20  0:22 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=3D3EDAB5.9721CEAE@moving-picture.com \
    --to=james-p@moving-picture.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=trmcneal@attbi.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