From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 10 Nov 2008 15:45:45 -0800 From: "Roman V. Shaposhnik" In-reply-to: <0fcba13d7a14fa2c33c5c9662ea30d30@vitanuova.com> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-id: <1226360745.17713.333.camel@goose.sun.com> MIME-version: 1.0 Content-type: text/plain Content-transfer-encoding: 7BIT References: <0fcba13d7a14fa2c33c5c9662ea30d30@vitanuova.com> Subject: Re: [9fans] Do we have a catalog of 9P servers? Topicbox-Message-UUID: 3a44a108-ead4-11e9-9d60-3106f5b1d025 On Mon, 2008-11-10 at 23:38 +0000, C H Forsyth wrote: > >And even we we stick with the "resources > >as regular files" approach on the client you're stuck with mostly POSIX > >environment + locking (+caching). POSIX means symlink(2) and mknod(2) > > no, because (unless i've misunderstood) they are accessing resources > (as regular files) on a remote server, and symbolic links and > outdated major/minor are irrelevant and not needed. Agreed. That's why I didn't include this bit in the main set of requirements. But wouldn't you agree that files kept on a remote POSIX file system is an important and common class of remotes resources for which we don't quite have a consensus on how to use 9P? We have at least three different attempts at solving that: 9P2000.u, Skip's Text/Rext and a "parallel tree" approach, but no consensus(*) Thanks, Roman.