Xref: utzoo comp.mail.uucp:5451 comp.dcom.modems:7310 Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!julius.cs.uiuc.edu!usc!samsung!uunet!zephyr.ens.tek.com!tektronix!nosun!qiclab!m2xenix!quagga!ctk1!olsa99!mje From: mje@olsa99.UUCP (Mark J Elkins) Newsgroups: comp.mail.uucp,comp.dcom.modems Subject: Re: What should a new UUCP protocol do? Message-ID: <2525@olsa99.UUCP> Date: 12 Nov 90 15:47:08 GMT References: <1990Nov07.155516.17815@ism.isc.com> <1889.2739aa0d@dcs.simpact.com> <+2m8g2.lb1@smurf.sub.org> <1898.273bd977@dcs.simpact.com> Reply-To: mje@olsa99.UUCP (Root) Followup-To: mje@olsa99.UUCP Organization: Unix Commercial - Olivetti Africa Lines: 48 In article <1898.273bd977@dcs.simpact.com> jeh@dcs.simpact.com writes: >In article <+2m8g2.lb1@smurf.sub.org>, urlichs@smurf.sub.org >(Matthias Urlichs) writes: >> In comp.dcom.modems, article <1889.2739aa0d@dcs.simpact.com>, >> jeh@dcs.simpact.com writes: >> < [uucp g negotiates packet and window size] >> < yourself to that. So a 'g' that handles 4Kx7 can still talk to one that >> < only does 64x3. >THis I have not seen -- I have tested a 7x4k g through a TB+ and it works fine, .... >exactly what happened in my tests, confirmed both by debug output and by line >analyzer. Apart from using a line analyser (I assume you mean Data-Scope) (what do you look for??), how can you tell what a particular machines version of uucp is using?? I've been hacking some uucico source (adding other protocols - etc) but the negotiation that 'G' does leaves me cold - so again - how can you tell both the buffer and window sizes? (Where is it in the Source code [at+t V Rel 3.2])??? >> Actually, it might be sufficient to NAK packets if there's an error ... >Sounds like zmodem. Which is not intended as a pejorative statement -- just an >observation. I had heard that Sys V Rel 4.0 was ment to use something like this - or at least, uucp would have the ability to start up a file transfere from were it had been cut off - just like Z-modem! >> Hmmmm ... Thinking some about this ... you could possibly fake it by ... >Someone actually hacked this together a year or so ago. As I recall he never >did get it working perfectly but I am sure this was just an implementation bug >and not a real flaw in the design; the design looked fine. Given the oppertunity to add to the wish list, 1 - Plug-in protocols (eg 'e', 'f', 'h', 'x'....) (so you don't need source code) 2 - Plug in Dialers... somewhat in the way that SCO does, ie - you could add 'connectors' for ethernet, built-in X25, funny modems.... etc -- . . ___. .__ Olivetti Systems & Networks, Unix Support - Africa /| /| / /__ UUCP: {uunet,olgb1,olnl1}!olsa99!mje (Mark Elkins) / |/ |ARK \_/ /__ LKINS mje@olsa99.UUCP (Postmaster) Tel: +27 11 339 9093