Newsgroups: comp.os.minix Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ira.uka.de!smurf!flatlin!ptavv!ralf From: ralf@ptavv.ka.sub.org (Ralf Wenk) Subject: Re: UUCP Version 2 Message-ID: <1991Jun23.222955.00350@ptavv.ka.sub.org> Date: Sun, 23 Jun 1991 22:29:55 GMT References: <1991Jun21.121604.10637@crash.cts.com> Lines: 54 In article <1991Jun21.121604.10637@crash.cts.com> cwr@pnet01.cts.com (Will Rose) writes: > [...] > Packet drivers - only the g-protocol is available, using Housel's code > unchanged except for the small recent net patch. The uucico code will A quick look a the 'g'-driver shows that the first of my posted patches is not there. So again: *** uucico.c.ori Sun Jun 23 22:49:01 1991 --- uucico.c Sun Jun 23 22:49:09 1991 *************** *** 1871,1878 **** chanopen = 0; printmsg(M_MEDPROTO, "Sending CLOSE request..."); } else if (neednack) { ! gspack(TT_CTRL, X_RJ, (recv + 1) & 7, ! (unsigned char *)NULL, 0); neednack = 0; printmsg(M_MEDPROTO, "Sending RJ... recv=%d", recv); } else if (send != nstuff /* nonzero output queue? */ --- 1871,1881 ---- chanopen = 0; printmsg(M_MEDPROTO, "Sending CLOSE request..."); } else if (neednack) { ! /* disabled because of protocoll violation. RW 25.Nov.90 ! gspack(TT_CTRL, X_RJ, (recv + 1) & 7, ! (unsigned char *)NULL, 0); ! */ ! gspack(TT_CTRL, X_RJ, recv, (unsigned char *)NULL, 0); neednack = 0; printmsg(M_MEDPROTO, "Sending RJ... recv=%d", recv); } else if (send != nstuff /* nonzero output queue? */ This fix will prevent the driver to request the wrong packet again if the received one is bad. Please note that I am using the 1.2 11/30/89 version of the 'g' driver with my patches - may be a newer version fixes this already. Both mistakes together allowed two MINIX uucicos connected together with a noisy line to do successfull transfers but not a MINIX and a HDB uucico. > handle multiple protocols. > [...] > This is a late alpha, I guess, so if you want life to run smoothly, don't > use it. If that's your aim, wait a bit until Fred van Kempen releases his > package, which will be partly based on this code and much better set out > and documented. (I think it will also have multiple protocols installed). Yes, some months ago he was looking for f,e and t descriptions. -- -- Ralf Wenk -- ralf@ptavv.ka.sub.org