From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <023801c38e04$db6f3e60$c901a8c0@cc77109e>
From: "Bruce Ellis" <brucee@chunder.com>
To: <9fans@cse.psu.edu>
References: <49d88ae4feaba4506f44c00cc1ec5fe6@collyer.net>
Subject: Re: [9fans] 'wall' messages
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Date: Thu,  9 Oct 2003 11:29:48 +1000
Topicbox-Message-UUID: 68b8155e-eacc-11e9-9e20-41e7f4b1d025

Geoff, you spoil all the fun.  I was waiting for screeds and
screeds of kernel code that scrummages around in everyones
namespace looking for places to write, and trying real hard
to only write to each place once.  And of course causing a
horrible mess to every window running anything but just rc.

Anyhow your code is shorter than Jim's speculations.

brucee
----- Original Message -----
From: "Geoff Collyer" <geoff@collyer.net>
To: <9fans@cse.psu.edu>
Sent: Thursday, October 09, 2003 10:31 AM
Subject: Re: [9fans] 'wall' messages


> Okay, here are implementations of write and wall in under 100 lines.
> I haven't used this code heavily but it worked when I last did.  You
> run `postwrite' in its own cpu-server window, which makes you
> reachable via write or wall by others on that cpu server.

etc