home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: alt.sources
- Path: sparky!uunet!mcsun!sun4nl!tedux!htbrug!herman
- From: herman@htbrug.hobby.nl (HAJ ten Brugge)
- Subject: prototol 'G' added in Taylor-UUCP
- Message-ID: <1992Dec28.175925.520@htbrug.hobby.nl>
- Organization: Home Office
- X-Newsreader: TIN [version 1.1 PL7]
- Date: Mon, 28 Dec 1992 17:59:25 GMT
- Lines: 105
-
- History:
-
- I am a new news user and used UUCP from SVR3 and SVR3 for a few years
- to copy files to a friend. I always used to 'G' protocol for this transfers
- because it is the fastest way to get the job done.
- When I joined news my forwarder had Taylor-UUCP running which allowed
- only protocol 'g' with a windowsize of 7 and a packetsize of '64'. I
- asked him if he could use the uucico program which came with his UNIX
- version because then I could use protocol 'g' with a windowsize of '7'
- and a packetsize of '128'.
- A few days ago I got the sources of Taylor-UUCP and saw that is easy
- to modify it to allow the 'G' protocol to be used (see patch below).
-
- This was measured on newspackets with a size of approx. 250000 bytes and
- an 14.4K modem.
-
- protocol used windowsize packetsize transferrate
- --------------------------------------------------------------
- 'g' 7 64 1485 bytes/sec
- 'g' 7 128 1614 bytes/sec
- 'G' 7 512 1666 bytes/sec
-
- The following patches have to be applied to Taylor-UUCP to use the 'G'
- protocol from BNU (Basic Networking Utilities).
- The first patch is there to make an extra entry in the allowable protocols.
- The second patch modifies protg.c to send always packages of the same
- size if protocol 'G' is selected. I alse increased the minimum value of
- the packet size into 128 because BNU can handle this packet size when
- protocol 'g' is selected.
- I made this patch on release 1.03 of Taylor UUCP. I know there is a newer
- version and hope that this patch will also work on that version
-
-
- -------------------- CUT HERE -------------------------------
- *** uucico.c.org Mon Dec 21 18:15:28 1992
- --- uucico.c Sat Dec 26 10:01:46 1992
- ***************
- *** 334,339 ****
- --- 334,342 ----
- { 'g', FALSE, RELIABLE_EIGHT,
- asGproto_params, fgstart, fgshutdown, fgsendcmd, zggetspace,
- fgsenddata, fgprocess, fgwait, NULL },
- + { 'G', FALSE, RELIABLE_EIGHT,
- + asGproto_params, fgstart, fgshutdown, fgsendcmd, zggetspace,
- + fgsenddata, fgprocess, fgwait, NULL },
- { 'f', FALSE, RELIABLE_RELIABLE,
- asFproto_params, ffstart, ffshutdown, ffsendcmd, zfgetspace,
- ffsenddata, ffprocess, ffwait, fffile },
- *** protg.c.org Mon Dec 21 18:15:25 1992
- --- protg.c Sat Dec 26 21:48:37 1992
- ***************
- *** 763,774 ****
- {
- int csize;
-
- ! /* If the remote packet size is larger than 64 (the default,
- which may indicate an older UUCP package), try to fit
- this command into a smaller packet. We still always send
- a complete packet, though. */
-
- ! if (iGremote_packsize <= 64)
- csize = iGremote_packsize;
- else
- {
- --- 763,774 ----
- {
- int csize;
-
- ! /* If the remote packet size is larger than 128 (the default,
- which may indicate an older UUCP package), try to fit
- this command into a smaller packet. We still always send
- a complete packet, though. */
-
- ! if (iGremote_packsize <= 128 || qProto->bname == 'G')
- csize = iGremote_packsize;
- else
- {
- ***************
- *** 876,885 ****
-
- if (cdata < iGremote_packsize)
- {
- ! /* If the remote packet size is larger than 64, the default, we
- can assume they can handle a smaller packet as well, which
- will be more efficient to send. */
- ! if (iGremote_packsize > 64)
- {
- /* The packet size is 1 << (iseg + 4). */
- iseg = 1;
- --- 876,885 ----
-
- if (cdata < iGremote_packsize)
- {
- ! /* If the remote packet size is larger than 128, the default, we
- can assume they can handle a smaller packet as well, which
- will be more efficient to send. */
- ! if (iGremote_packsize > 128 && qProto->bname != 'G')
- {
- /* The packet size is 1 << (iseg + 4). */
- iseg = 1;
-
- --
- ---------------------------------------------
- | Herman ten Brugge herman@htbrug.hobby.nl |
- ---------------------------------------------
-