From: "Lyndon Nerenberg (VE6BBM/VE7TFX)" <lyndon@orthanc.ca>
To: 9fans@9fans.net
Subject: Re: [9fans] exec permission on plan9
Date: Fri, 26 Feb 2010 12:17:49 -0700 [thread overview]
Message-ID: <a79717810fe21c7f1829248786d5b572@yyc.orthanc.ca> (raw)
In-Reply-To: <32d987d51002261105t2242b381u7b8d4f533709d078@mail.gmail.com>
> well, you can make it explicit.. path=(/bin)
Which really should be the default, or at least path=(/bin .).
Putting '.' at the front means that wherever you're cd'ed into a
remote directory, every command you run is 9Peeing off to the remote
host looking for a command that's most likely not going to be there.
When your RTTs get into the 100ms+ range, things quickly get very
painful.
Fixing path= in /rc/lib/rcmain will make your life a lot happier if you
work with a lot of remote 9P mounts.
--lyndon
prev parent reply other threads:[~2010-02-26 19:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 17:28 Steve Simon
2010-02-26 17:43 ` erik quanstrom
2010-02-26 18:28 ` Russ Cox
2010-02-26 18:50 ` Steve Simon
2010-02-26 18:55 ` erik quanstrom
2010-02-26 19:19 ` Steve Simon
2010-02-26 19:05 ` Federico G. Benavento
2010-02-26 19:17 ` Lyndon Nerenberg (VE6BBM/VE7TFX) [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=a79717810fe21c7f1829248786d5b572@yyc.orthanc.ca \
--to=lyndon@orthanc.ca \
--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).