From: "Gabriel Diaz" <gabidiaz@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] faces and the plumb messages received by cpu connections
Date: Fri, 16 Mar 2007 19:07:54 +0100 [thread overview]
Message-ID: <82c890d00703161107h3c44210cj35627940a18ba85a@mail.gmail.com> (raw)
In-Reply-To: <ee9e417a0703160857u31ae33dp53cdb7e55e991503@mail.gmail.com>
hello
thanks all for the comments.
i suppose an rc script is enough to add
the cpu'ed mailbox to the local one without
having a pre-configured script, to get faces and
upasfs working with cpued hosts.
gabi
On 3/16/07, Russ Cox <rsc@swtch.com> wrote:
> Plumber is working fine. You simply asked it to connect
> two programs inappropriately -- an upas/nedmail running
> in one name space with an upas/fs running in a different
> name space.
>
> If, on the other hand, you were also running acme Mail
> in the cpu window, then everything would have worked out
> fine, even though plumber and faces are on different
> machines from upas/fs and Mail.
>
> Embedding machine names in messages attacks the
> generality and power of the system.
>
> Plan 9 relies heavily on its conventions. If you break the
> conventions, sometimes the system doesn't work as well
> (bind /net/tcp /proc && ps).
>
> But being able to break the conventions is important and
> powerful, because if you break them just a little, sometimes
> the system works even better (import helix /proc && acid 123;
> sshnet; snapfs; bind /mnt/term/net/tcp /net/tcp && ssh; etc.).
>
> Russ
>
prev parent reply other threads:[~2007-03-16 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 9:15 Gabriel Díaz
2007-03-16 12:39 ` Steve Simon
2007-03-16 13:48 ` erik quanstrom
2007-03-16 15:57 ` Russ Cox
2007-03-16 18:07 ` Gabriel Diaz [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=82c890d00703161107h3c44210cj35627940a18ba85a@mail.gmail.com \
--to=gabidiaz@gmail.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).