All of lore.kernel.org
 help / color / mirror / Atom feed
From: dwight@supercomputer.org
To: Tom McNeal <trmcneal@comcast.net>
Cc: Norman Zhang <nzhang@arkon-group.com>, nfs@lists.sourceforge.net
Subject: Re: NFS history
Date: Mon, 05 Jan 2004 09:56:37 -0800	[thread overview]
Message-ID: <200401051756.i05Hube15542@supercomputer.org> (raw)
In-Reply-To: Message from Tom McNeal <trmcneal@comcast.net> of "Fri, 02 Jan 2004 17:00:01 PST." <3FF61411.7000500@comcast.net>

There was a release of NFS back around 1987 IIRC. It was sold by Lachman
Associates, and my impression was that it was their big claim to fame back 
then.
I worked with the source code myself, but my recollection of it is hazy.

Here's a usenet posting about their running it on VAXes, from 1986:

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=118%40tijc02.UUCP&rn
um=2&prev=/groups%3Fq%3Dlachman%2Bnfs%26hl%3Den%26lr%3D%26ie%3DUTF-8%26sa%3DN%2
6tab%3Dwg

Best Regards,

	-dwight-

> V1 was never released by Sun as a product, I think.  Brent may have talked
> about it in "NFS Illustrated".  We're talking about 1985-7, you know.
> 
> Regards;
> 
> Tom
> 
> Norman Zhang wrote:
> > Hi,
> > 
> > I've been googling for the difference between NFSv1 and NFSv2, but only 
> > found NFSv2 vs NFSv3. Does anyone recall some of major changes from v1 
> > to v2?
> > 
> > Regards,
> > Norman
> > 
> > 
> > 
> > -------------------------------------------------------
> > This SF.net email is sponsored by: IBM Linux Tutorials.
> > Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> > Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> > _______________________________________________
> > NFS maillist  -  NFS@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nfs
> > 
> 
> -- 
> Tom McNeal
> (650)906-0761(cell)
> (650)964-8459(fax)
> Email: trmcneal@attbi.com
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> NFS maillist  -  NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2004-01-05 17:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-02  5:15 NFS history Norman Zhang
2004-01-03  1:00 ` Tom McNeal
2004-01-05 17:56   ` dwight [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=200401051756.i05Hube15542@supercomputer.org \
    --to=dwight@supercomputer.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=nzhang@arkon-group.com \
    --cc=trmcneal@comcast.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.