From: Jason Catena <jason.catena@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] plan9port behind corporate firewall with no DNS or port access
Date: Fri, 24 Jul 2009 23:06:51 -0500 [thread overview]
Message-ID: <d50d7d460907242106vec04d47j21b6c3169b9150df@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 462 bytes --]
At work I sit behind a corporate firewall which neither knows
sources.cs.bell-labs.com nor would provide me direct access to its ports if
it did. I can get out through http proxies (eg curl). Is there any way to
mount sources through this kind of static, or should I resign myself to only
seeing sources from my home computer?
9fs sources
srv: dial tcp!sources.cs.bell-labs.com!9fs: unknown host
sources.cs.bell-labs.com
9fs: exit 1
Jason Catena
[-- Attachment #2: Type: text/html, Size: 669 bytes --]
next reply other threads:[~2009-07-25 4:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-25 4:06 Jason Catena [this message]
2009-07-25 4:35 ` andrey mirtchovski
2009-07-25 4:55 ` Jason Catena
2009-07-25 13:56 ` erik quanstrom
2009-07-25 8:12 ` Steve Simon
2009-07-25 12:43 ` Uriel
2009-07-25 16:39 ` Salman Aljammaz
2009-07-25 16:55 ` John Floren
2009-07-25 16:56 ` Iruata Souza
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=d50d7d460907242106vec04d47j21b6c3169b9150df@mail.gmail.com \
--to=jason.catena@gmail.com \
--cc=9fans@9fans.net \
/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).