From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Drawterm or VMWare terminal?
Date: Thu, 27 Feb 2003 10:11:15 -0500 [thread overview]
Message-ID: <200302271511.h1RFBFM21109@augusta.math.psu.edu> (raw)
In-Reply-To: Your message of "Thu, 27 Feb 2003 09:54:03 EST." <a1055cd9c2f1159d1bf87ea6f5ee5d81@plan9.bell-labs.com>
> > Just out of curiousity; why isn't this built into the kernel by
> > default? It strikes me as useful for phasing out il.
>
> since we're not there yet, it hasn't been necessary for us.
> we have not switched the main bell labs file server to
> fossil yet.
Granted, but it wouldn't hurt to add it now, would it? It strikes me
that it'd be useful for, e.g., people trying to talk to fileservers
through firewalls or trampolining through CPU servers.
- Dan C.
next prev parent reply other threads:[~2003-02-27 15:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 9:35 Robby
2003-02-27 14:42 ` Russ Cox
2003-02-27 14:49 ` Dan Cross
2003-02-27 14:54 ` Russ Cox
2003-02-27 15:11 ` Dan Cross [this message]
2003-02-27 15:19 ` Russ Cox
2003-02-27 15:49 ` Dan Cross
2003-02-27 15:57 ` rob pike, esq.
2003-02-27 15:59 ` Dan Cross
2003-02-27 16:04 ` Boyd Roberts
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=200302271511.h1RFBFM21109@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--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).