From: 9nut@9netics.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] New OS
Date: Fri, 14 May 2004 10:16:18 -0700 [thread overview]
Message-ID: <090eace6cd5fc3586f9e8ebf3a164b45@9netics.com> (raw)
In-Reply-To: <027513cfba487d632c4e76b32e6b1b2d@borf.com>
> By the way, is there a 9fs for XP?
drawterm.
run it on a different port and have that script on the cpu
post the fd to /srv after authenticating. then mount it.
Very It's useful.
prev parent reply other threads:[~2004-05-14 17:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 11:38 Jim Affra
2004-05-14 11:52 ` a
2004-05-14 12:35 ` viro
2004-05-14 12:52 ` boyd, rounin
2004-05-17 0:56 ` Kenji Okamoto
2004-05-17 1:00 ` boyd, rounin
2004-05-17 1:15 ` Brantley Coile
2004-05-17 1:28 ` boyd, rounin
2004-05-17 1:39 ` Brantley Coile
2004-05-17 1:42 ` boyd, rounin
2004-05-17 3:06 ` Ali Mashtizadeh
2004-05-14 14:16 ` dvd
2004-05-14 14:25 ` andrey mirtchovski
2004-05-14 14:30 ` Eric KD5UWL
2004-05-14 14:34 ` Nigel Roles
2004-05-14 15:15 ` Brantley Coile
2004-05-14 15:32 ` Steve Simon
2004-05-14 15:45 ` [9fans] ati video cards Ayan George
2004-05-14 17:00 ` andrey mirtchovski
2004-05-14 17:53 ` Ayan George
2004-05-14 17:16 ` 9nut [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=090eace6cd5fc3586f9e8ebf3a164b45@9netics.com \
--to=9nut@9netics.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).