From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 21 Nov 2008 00:12:03 +0000 From: Eris Discordia To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Re: [9fans] Do we have a catalog of 9P servers? Topicbox-Message-UUID: 4dbf5bec-ead4-11e9-9d60-3106f5b1d025 >> "hey, 9P is all text [...] > > wrong. Upon reading this: > Each message consists of a sequence of bytes. Two=E2=80=93, = four=E2=80=93, and > eight=E2=80=93byte fields hold unsigned integers represented in = little=E2=80=93endian > order (least significant byte first). Data items of larger or variable > lengths are represented by a two=E2=80=93byte field specifying a count, = n, > followed by n bytes of data. -- 0intro(5) I see that you are correct (how could you not be?). I apologize and supply=20 this correction: 9P is _not_ all text, but it consists of a well-defined=20 set of messages. The idea, anyway, is the same. ----------------------------------------------------------------------------= ---- >> That's wrong (or maybe I'm wrong). Whatever "network glue" /net uses to >> get the host represented on the network lies _entirely_ outside of 9P's >> domain. > > this is a tautology; 9p does not define semantics. equivalently, > everything telnet does is outside of the domain of tcp/ip. or, the > vehicle i use to get to work has no bearing on what i do at work. In what way is an informative statement a tautology? Specifically=20 "everything telnet does is outside of the domain of tcp/ip" which you have=20 used in comparison is very much informative indeed and not a tautology. The = meaning it conveys is something akin to "since things telnet does is=20 outside the domain of TCP/IP one can say, a. telnet can exist independent=20 of TCP/IP, and b. TCP/IP can't possibly be relying on telnet to work."=20 Likewise my remark conveys a meaning akin to "since things /net does lie=20 outside the domain of 9P one can say, a. 9P can exist independent of /net=20 (and it probably does, I guess your Plan 9 kernel uses it to talk to local=20 file servers, or do you always need a loopback for that purpose?), and b.=20 /net can't possibly be relying on 9P to work." SUMMARY: /net is an interface to which programs talk in 9P but which does=20 not talk 9P to the layers beneath it because the layers beneath don't=20 _understand_ 9P. They are implementations of transport protocol X which is=20 an existence unrelated to 9P. ----------------------------------------------------------------------------= ---- >> Erik Quanstrom has put this in 9speak in his response to your posting. >> Please check it out. >> >> --On Thursday, November 20, 2008 10:30 AM -0800 >> akumar@sounine.nanosouffle.net wrote: >> [...] > > i wrote none of the quoted material. That's not "quoted material." It's the posting I was replying to, naturally = occurring after my reply. I suggested that akumar read what you had posted=20 before this one. --On Thursday, November 20, 2008 5:42 PM -0500 erik quanstrom=20 wrote: >> "hey, 9P is all text [...] > > wrong. > >> That's wrong (or maybe I'm wrong). Whatever "network glue" /net uses to >> get the host represented on the network lies _entirely_ outside of 9P's >> domain. > > this is a tautology; 9p does not define semantics. equivalently, > everything telnet does is outside of the domain of tcp/ip. or, the > vehicle i use to get to work has no bearing on what i do at work. > >> Erik Quanstrom has put this in 9speak in his response to your posting. >> Please check it out. >> >> --On Thursday, November 20, 2008 10:30 AM -0800 >> akumar@sounine.nanosouffle.net wrote: >> [...] > > i wrote none of the quoted material. > > - erik > >