From mboxrd@z Thu Jan 1 00:00:00 1970 Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <200412151836.iBFIaIt19740@zamenhof.cs.utwente.nl> References: <3d04f137980002699fc0344922c1ce44@vitanuova.com> <200412151836.iBFIaIt19740@zamenhof.cs.utwente.nl> 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 18:47:27 +0000 To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Topicbox-Message-UUID: 17fed63c-eace-11e9-9e20-41e7f4b1d025 On 15 Dec 2004, at 18:36, Axel Belinfante wrote: >> 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. > > might that also be a way to provice access to > files on a remote plan 9 file server? > (e.g. to edit them via acme, or whatever) > Yes, I'd assume that an acme running on a non-plan9 system could (if it could talk 9p to it) see the file on a remote plan 9 server. But, nothing else on your system (apart from plan 9 aware tools) would be able to see the mount point... > Axel. >