From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <ee9e417a0703160857u31ae33dp53cdb7e55e991503@mail.gmail.com>
Date: Fri, 16 Mar 2007 11:57:07 -0400
From: "Russ Cox" <rsc@swtch.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
In-Reply-To: <011701c767ab$980d3760$c827a620$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <011701c767ab$980d3760$c827a620$@com>
Topicbox-Message-UUID: 2692e946-ead2-11e9-9d60-3106f5b1d025

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