From: "ozan s. yigit" <oz@abyss.sun.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] u9fs license?
Date: Mon, 8 Jan 2001 17:09:27 +0000 [thread overview]
Message-ID: <ya0od7dyas9c.fsf@abyss.i-have-a-misconfigured-system-so-shoot-me> (raw)
In-Reply-To: <20010106234534.EAA82199D7@mail.cse.psu.edu>
rob@plan9.bell-labs.com (rob pike) writes:
> I honestly don't remember how we used to distribute u9fs, except as
> packaged within a Plan 9 distribution.
for the longest time (since around 95, i think), it was available on its
own, like awk, sam etc. i think i first found it through netlib/research
along with andrew's conversion stuff and i'm sure i can still dig out
the copy i ftp'ed in 95. there were no attached notes, licenses etc.
oz
next prev parent reply other threads:[~2001-01-08 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-06 5:40 rob pike
2001-01-07 3:22 ` greg andruk
2001-01-07 5:11 ` Boyd Roberts
2001-01-08 17:09 ` ozan s. yigit [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-06 3:20 greg andruk
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=ya0od7dyas9c.fsf@abyss.i-have-a-misconfigured-system-so-shoot-me \
--to=oz@abyss.sun.com \
--cc=9fans@cse.psu.edu \
/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).