From: Ben <cellctl@lycos.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /sys/lib/mothra
Date: Mon, 29 Jul 2002 15:58:10 +0000 [thread overview]
Message-ID: <dd8c4466.0207181415.18488f2f@posting.google.com> (raw)
In-Reply-To: <20020718125735.3B29D1998C@mail.cse.psu.edu>
miller@hamnavoe.demon.co.uk (Richard Miller) wrote in message news:<20020718125735.3B29D1998C@mail.cse.psu.edu>...
> Sorry, I think it's been deliberately set up as an importable file system
> to be a showcase of the 4th edition Plan 9 security mechanisms.
>
> -- Richard
Is there some way I could use drawterm-win? If not, would you be so
kind as to e-mail the sources to me? Or is that illegal? (Yes, I
have 3rd & 4th edition licenses, if that means anything!) Thanks
much!
Ben
next prev parent reply other threads:[~2002-07-29 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 12:57 Richard Miller
2002-07-29 15:58 ` Ben [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-15 11:05 Richard Miller
2002-07-18 9:51 ` Ben
2002-07-12 7:57 Fco.J.Ballesteros
2002-07-15 9:30 ` Ben
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=dd8c4466.0207181415.18488f2f@posting.google.com \
--to=cellctl@lycos.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).