From mboxrd@z Thu Jan 1 00:00:00 1970 Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: References: <3d04f137980002699fc0344922c1ce44@vitanuova.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <15C1E550-4EBF-11D9-901F-00112430C042@gmail.com> Content-Transfer-Encoding: 7bit From: jim Subject: Re: [9fans] Acme mailreader Date: Wed, 15 Dec 2004 17:30:59 +0000 To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Topicbox-Message-UUID: 17b9a22e-eace-11e9-9e20-41e7f4b1d025 On 15 Dec 2004, at 17:07, Russ Cox wrote: > > 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. > *jim tabs over to drawterm. *jim pokes around. Oh wow. That's really nice. I want it. > 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. > Ah I see. So, this magic 9p socket(s) lets acme talk to upas/fs in order to get the (nicely decoded) emails? Very good. So, upas/fs maintains some kind of internal representation of the /mnt/fs/mbox? Or is it generated on-the-fly by grabbing messages? I promise I'll go away and read the source now... Thanks for your help, jim