Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!ssbell!mcmi!unocss!dsndata!wayne
From: wayne@dsndata.uucp (Wayne Schlitt)
Newsgroups: comp.os.os2
Subject: Re: Stop Wasting Bandwidth On Binaries
Message-ID: <WAYNE.90Jan1124719@dsndata.uucp>
Date: 1 Jan 90 18:47:20 GMT
References: <5.UUL1.3#5085@congrunt.uunet.uu.net> <5845@uhccux.uhcc.hawaii.edu>
Sender: wayne@dsndata.UUCP
Organization: Design Data
Lines: 35



as i see it, there are three advantages to getting rid of binaries
(and/or sources) from a discussion group:

1) for those who dont want to use the bandwidth, it is much easier to
   just not get comp.binaries.*

2) for those with tight disk space, you can expire the binary/source
   groups quicker

3) archive sites can be set up for the binary/source groups so that
   those who missed the goodies the first time can get them later..


as kind of a separate questions, many of the binaries that i have seen
float through comp.os.os2 have been "standard" unix programs.  (which
is fine...)  were these simply compile and run type of ports to os2,
or did you have to make a lot of changes to the sources?

if they are simple compiles, i guess i do object to the binaries being
posted.  for those who want them, it would be a lot less bandwidth to
just mail them.

if they are not simple ports, then wouldnt it be better to post the
sources and/or diffs?  that way people can fix bugs and make
improvements to the ports.  

the binary postings _have_ raised the size/article ratio for
comp.os.os2 quite a bit and has also raised the cost per reader to
number 5 in Brian Reid's lists.  comp.os.minix is also high, but most
of the large postings there are source.


-wayne