From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Wed, 15 Dec 2004 12:07:06 -0500 From: Russ Cox To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] Acme mailreader In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <3d04f137980002699fc0344922c1ce44@vitanuova.com> Topicbox-Message-UUID: 17af35b4-eace-11e9-9e20-41e7f4b1d025 > Let me see if i understand this properly. upas/fs parses lots of the > message > format, then makes available a filesystem which contains the messages > in a > nicer format (minus mime &c.), which is the served to clients (e.g. > acme(1)) > using 9p. Right? So, acme talks to my local fs (e.g. to edit a file) > using unix > syscall &c., but it wants to talk to mail using 9p? Presumably one can > make > acme look at a local fs for the mailboxes, rather than 9p? In which > case, the > problem is to get upas/fs to parse the messages, then mount them > somewhere > for acme to see... Or, perhaps I'm fundamentally misunderstanding plan > 9... to get a feel for what upas/fs is providing, you should poke around in /mail/fs/mbox on a real plan9 machine and look at the broken out messages -- just cd around and cat things. the plan 9 ports code posts 9p services as unix domain sockets in a magic directory in /tmp. code in the know can open the sockets and speak 9p to the servers. that's how win talks to acme, for example, and how everyone talks to the plumber. you could start with /usr/local/plan9/src/cmd/9p.c and dig down from there to see what's going on. russ