From mboxrd@z Thu Jan 1 00:00:00 1970 Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <3d04f137980002699fc0344922c1ce44@vitanuova.com> References: <3d04f137980002699fc0344922c1ce44@vitanuova.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: jim Subject: Re: [9fans] Acme mailreader Date: Wed, 15 Dec 2004 16:31:25 +0000 To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Topicbox-Message-UUID: 17a9287c-eace-11e9-9e20-41e7f4b1d025 On 15 Dec 2004, at 16:24, C H Forsyth wrote: >>> Very nice ;-). Are upas/fs as yet unported for some technical reason, > > it serves the mbox name space using the 9p protocol. > most other systems can't directly act as clients (well), without > non-trivial system-specific implementations of 9p client code; > there is most of one for linux, but not (i think) macosx. > i suppose applications that wanted to access it could just > use the 9p client libraries, but that restricts it a bit. > Yeah, that could be a problem... My head is swimming with namespaces ;-) 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... Cheers, jim