From: arnold@skeeve.com (arnold@skeeve.com)
Subject: [TUHS] Sun NFS version 2.0
Date: Fri, 24 Feb 2017 00:47:43 -0700 [thread overview]
Message-ID: <201702240747.v1O7lhVM012173@freefriends.org> (raw)
In-Reply-To: <55eca846-4c97-8bca-ec81-f5499d796ea7@kilonet.net>
It got to the list. I think you didn't get an answer because
noone here knows what to tell you.
I suggest working off-list with Warren to get him the code and
help him try to figure out if he can publish it.
Arnold
Arthur Krewat <krewat at kilonet.net> wrote:
> I've never received an answer to this, and I wonder if it was because it
> was sent another route and got choked as SPAM after the mailing list (I
> received it from the mailing list).
>
> On 2/22/2017 8:33 AM, Arthur Krewat wrote:
> > So what's the consensus at this point? Open source? Already released?
> >
> > I can't vouch that this wasn't some under-the-table exchange. It was
> > for an "educational" institution but did not necessarily wind up
> > there. Hence why I want to compare with similar releases if it exists.
> >
> > The sources all have copyright dates ranging from 1983 to 1985 for
> > Sun-generated bits that looks like this:
> >
> > static char sccsid[] = "@(#)domainname.c 1.1 85/05/30 Copyr 1984 Sun
> > Micro";
> >
> > And sccsid's like this for sources taken from BSD and altered to fit:
> >
> > df.c:static char sccsid[] = "@(#)df.c 1.1 85/05/30 SMI"; /* from
> > UCB 4.18 84/02/02 */
> >
> > Sorry for fracturing this thread already.
> >
> >
> > On 2/21/2017 8:46 PM, Clem Cole wrote:
> >>
> >> On Tue, Feb 21, 2017 at 8:35 PM, Arthur Krewat <krewat at kilonet.net
> >> <mailto:krewat at kilonet.net>> wrote:
> >>
> >> Anyone interested in this source code? I did a quick Google
> >> search and couldn't find anything relevant. If it's out there
> >> somewhere, let me know, I'd like to take a look at it.
> >>
> >> It's Network File System Sun Microsystems Release 2.0
> >>
> >> Since, the core of Solaris was made FOSS, I would hope there is(are)
> >> persons at Oracle/Sun that can officially stamp the technology has
> >> only historical value.
> >>
> >> Anyone know whom that should be so it can make it from the dark side.
> >>
> >>
> >
>
next prev parent reply other threads:[~2017-02-24 7:47 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 12:02 [TUHS] Mach for i386 / Mt Xinu or other Noel Chiappa
2017-02-21 12:24 ` Steffen Nurpmeso
2017-02-21 12:57 ` Michael Kjörling
2017-02-21 15:02 ` Clem Cole
2017-02-22 1:50 ` Dan Cross
2017-02-22 2:25 ` Steve Nickolas
2017-02-22 3:11 ` Clem Cole
2017-02-22 4:07 ` Dan Cross
2017-02-22 4:17 ` Larry McVoy
2017-02-23 15:31 ` Nemo
2017-02-23 16:00 ` Clem Cole
2017-02-23 16:50 ` Nemo
2017-02-23 22:02 ` Dave Horsfall
2017-02-24 1:30 ` Clem Cole
2017-02-24 20:54 ` Dave Horsfall
2017-02-24 1:01 ` Jason Stevens
2017-02-22 10:16 ` jsteve
2017-02-21 15:15 ` Chet Ramey
2017-02-21 16:47 ` Larry McVoy
2017-02-21 18:58 ` Clem Cole
2017-02-21 19:21 ` Larry McVoy
2017-02-21 20:17 ` Clem Cole
2017-02-21 20:28 ` Steve Nickolas
2017-02-21 20:32 ` Larry McVoy
2017-02-21 22:58 ` Wesley Parish
2017-02-22 1:19 ` Clem Cole
2017-02-22 1:35 ` [TUHS] Sun NFS version 2.0 Arthur Krewat
2017-02-22 1:46 ` Clem Cole
2017-02-22 13:33 ` Arthur Krewat
2017-02-23 23:48 ` Arthur Krewat
2017-02-24 7:47 ` arnold [this message]
2017-02-22 2:07 ` Cory Smelosky
2017-02-22 13:25 ` Arthur Krewat
2017-02-22 3:17 ` Larry McVoy
2017-02-22 8:43 ` arnold
2017-02-24 20:57 ` Warren Toomey
2017-02-24 22:09 ` Warren Toomey
2017-02-26 10:50 ` Josh Good
2017-02-22 9:00 ` [TUHS] Mach for i386 / Mt Xinu or other jsteve
2017-02-22 0:52 ` Andy Kosela
2017-02-22 1:04 ` ron minnich
2017-02-22 1:33 ` jason-tuhs
2017-02-22 3:18 ` Larry McVoy
2017-02-22 3:45 ` ron minnich
2017-02-22 4:06 ` Larry McVoy
2017-02-22 4:11 ` Larry McVoy
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=201702240747.v1O7lhVM012173@freefriends.org \
--to=arnold@skeeve.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;
as well as URLs for NNTP newsgroup(s).