kak@hico2.UUCP (Kris A. Kugel) (02/16/91)
I've posted two articles, one to ONLY comp.sys.3b1, and the other ONLY to unix-pc.general. These two articles are <1068@hico2.UUCP> and <1069@hico2.UUCP> . If aliasing is working correctly, somewhere the unix-pc.general article will start appearing in the comp.sys.3b1 group. I'm figuring that the comp.sys.3b1 article will be useful if anybody else wants to run the same kind of analysis. I appologize for posting it in these informational groups, but sites may have already aliased unix-pc.test to misc.test, and I think that this is important enough to do this NOW. Meanwhile, I've run a quick benchmark looking for systems that articles posted to JUST comp.sys.3b1, and compared them to the accumulated articles posted to JUST unix-pc.*. For each of the articles on these lists, I got the path of the article, produced a list of which machines the article had passed through, and then sorted the list to remove duplicates. I don't know how aliasing will have affected this, it may have some false negatives. The only way I can remove false positives is if more people post articles to ONLY comp.sys.3b1, which is evidently a good way to keep many people from getting your article. (*sigh*) I'll try to post a script for doing this when I can. (I have 4 higher-priority projects going on right now) I note with interest that tsdiag and westmark, my major feeds, (who get most of their mail from att), haven't forwarded ANY of the articles posted to just comp.sys.3b1 here. Both system administrators have said that they have changed their news sys file to do so. (*sigh* again.) I suspect their feeds from att. This measure is not completely scientific, because it depends on which machines are posting messages, which machines are most efficent at passing news, etc. But still . . . . SUMMARY FOLLOWS =============== (all articles considered were posted to ONE newsgroup) Systems that I haven't seen comp.sys.3b1 articles come through, that I have seen unix-pc.* articles come through: acorn agate alice andante attcan bagend balilly.UUCP beartrk blilly.UUCP bluemoon boulder bu.edu casbah.acns.nwu.edu cbnews cbnewsh crackers cs.umn.edu csn csusac cup.portal.com das13 daver ddsw1 decwrl ditka drutx druwa eci emory fbits fernwood fmsrl7 hayes.ims.alaska.edu hoswjc hpftc hsdndev iguana ispd-newsserver kodak laidbak lavaca.uh.edu lectroid limbic lll-winken lobster longbow lsuc magnus.ircc.ohio-state.edu masscomp math.lsa.umich.edu maytag mcdchg mcsun menudo.uh.edu mgweed milton mips morwyn msi.umn.edu n8emr ncar ncrcan news-server.csri.toronto.edu news.cs.indiana.edu nyet obdient ocpt pacbell pacbell.com portal problem proton proxima psuvax1 psuvm quest ramecs sactoh0 scocan sharkey shelby skeeve skypod slammer sonyd1.Broadcast.Sony.COM spies spool.mu.edu spool2.mu.edu stiatl sun-barr swbatl teemc telly terminator trac2000 transfer trux tsdiag ttank tut.cis.ohio-state.edu ucbvax ucsd ukc umich uncle unify utgpu utzoo uunet uupsi vmp wa8tzg watserv1 westmark xenitec yclept yonder zephyr.ens.tek.com zinn Machines I've gotten comp.sys.3b1 articles from, (but don't have a record of unix-pc articles going through) bronze bucket convex copper cornell dsl.pitt.edu duke egsner gatech haven jarthur mcnc mtek mtek.com nntp-server.caltech.edu ogicse parsely pdxgate pt.cs.cmu.edu purdue rochester sci.ccny.cuny.edu swrinde texrex uflorida umbc3 umbc4.umbc.edu Machines that I've gotten unix-pc and comp.sys.3b1 articles through over the last month: ames apple att caen cbnewsk cbnewsl cs.utexas.edu dali.cs.montana.edu elroy.jpl.nasa.gov hico2 julius.cs.uiuc.edu linac mit-eddie paperboy rex rpi samsung sdd.hp.com snorkelwacker.mit.edu sol.ctr.columbia.edu think.com uakari.primate.wisc.edu ukma usc uw-beaver uwm.edu vsi1 wuarchive zaphod.mps.ohio-state.edu zorch
wwm@wa8tzg.mi.org (Bill Meahan) (02/17/91)
In article <1071@hico2.UUCP> kak@hico2.UUCP (Kris A. Kugel) writes: >I've posted two articles, one to ONLY comp.sys.3b1, >and the other ONLY to unix-pc.general. >These two articles are <1068@hico2.UUCP> and <1069@hico2.UUCP> . >If aliasing is working correctly, somewhere the unix-pc.general >article will start appearing in the comp.sys.3b1 group. > [...] > >SUMMARY FOLLOWS >=============== >(all articles considered were posted to ONE newsgroup) > >Systems that I haven't seen comp.sys.3b1 articles come through, >that I have seen unix-pc.* articles come through: > [...] >sharkey [...] >umich [...] >wa8tzg Hmmmm. Here at wa8tzg I get fed from sharkey which is happily feeding me BOTH unix-pc.* AND comp.{sys | sources}.3b1. umich also feeds pmsmam (my machine at work) BOTH groups. I know I'M running Cnews (15-Dec-1990) with the unix-pc.* aliased to comp.{sys|sources}.3b1. I think sharkey is also a Cnews site. This MAY be munging up your statistics. -- Bill Meahan (WA8TZG) | Programming is simple: wwm@wa8tzg.mi.org OR | uunet!mailrus!sharkey!wa8tzg!wwm | All you have to do is put the right "Home for Cybernetic Orphans" | numbers in the right memory locations!
dnichols@ceilidh.beartrack.com (DoN Nichols) (02/17/91)
In article <1071@hico2.UUCP> kak@hico2.UUCP (Kris A. Kugel) writes: >I've posted two articles, one to ONLY comp.sys.3b1, >and the other ONLY to unix-pc.general. >These two articles are <1068@hico2.UUCP> and <1069@hico2.UUCP> . >If aliasing is working correctly, somewhere the unix-pc.general >article will start appearing in the comp.sys.3b1 group. [ ... text deleted ... ] Here's the distribution line from this posting )Newsgroups: comp.sys.3b1,unix-pc.general,comp.sys.att > >SUMMARY FOLLOWS >=============== >(all articles considered were posted to ONE newsgroup) > >Systems that I haven't seen comp.sys.3b1 articles come through, >that I have seen unix-pc.* articles come through: > [... systems deleted ...] >beartrk Interesting! This is my feed, and I am most definately getting 'comp.sys.3b1'. There may be some Bnews system between him and you which is doing a reverse alias of 'comp.sys.3b1' back to 'unix-pc.general'. His feed is uunet.uu.net. I'm not sure whether he has other non-leaf nodes out there, or is just feeding lots of leafs (leaves? which is the plural when refering to nodes? I know about trees.). Home this gets cleaned up. I'm getting LOTS of comp.sys.3b1 items. Good Luck DoN. -- Donald Nichols (DoN.) | Voice (Days): (703) 664-1585 D&D Data | Voice (Eves): (703) 938-4564 Disclaimer: from here - None | Email: <dnichols@ceilidh.beartrack.com> --- Black Holes are where God is dividing by zero ---
thad@public.BTR.COM (Thaddeus P. Floryan) (02/19/91)
wwm@wa8tzg.mi.org (Bill Meahan) in <1991Feb16.223633.893@wa8tzg.mi.org> writes: In article <1071@hico2.UUCP> kak@hico2.UUCP (Kris A. Kugel) writes: >>I've posted two articles, one to ONLY comp.sys.3b1, >>and the other ONLY to unix-pc.general. >[...] >>Systems that I haven't seen comp.sys.3b1 articles come through, >>that I have seen unix-pc.* articles come through: >> > [...] >>sharkey > [...] >>umich > [...] >>wa8tzg > >Hmmmm. Here at wa8tzg I get fed from sharkey which is happily ... >This MAY be munging up your statistics. BTR.COM is getting a ton of comp.*.3b1 and unix-pc.* material and is fed by only decwrl, mips and fernwood ... systems which Kris indicated are NOT feeding 3B1 properly. PORTAL isn't getting diddly-squirt, but that's their problem. :-) OK, so WHERE or HOW are all the 3b1 postings arriving at BTR? Via some magical "ether" net on which one uses Philosopher's Stone transceivers and crystal terminators with little winged faeries twiddling the bits? :-) In case anyone's interested, I have archived EVERYTHING appearing in the comp.*.3b1 newsgroups. The compressed tar file is already approaching 1MB, so please do NOT ask me to email it to you. I plan to make it available at the users' group meeting this month and perhaps something can be worked out by US Mail for anyone interested. Thad Floryan [ thad@btr.com (OR) {decwrl, mips, fernwood}!btr!thad ]
ebd@fang.ATT.COM (Elliot B Dierksen) (02/23/91)
From article <1118@hico2.UUCP>, by kak@hico2.UUCP (Kris A. Kugel): | In article <1839@public.BTR.COM>, thad@public.BTR.COM (Thaddeus P. Floryan) writes: |> wwm@wa8tzg.mi.org (Bill Meahan) in <1991Feb16.223633.893@wa8tzg.mi.org> writes: |> |> In article <1071@hico2.UUCP> kak@hico2.UUCP (Kris A. Kugel) writes: |> >>Systems that I haven't seen comp.sys.3b1 articles come through, |> >>that I have seen unix-pc.* articles come through: |> >This MAY be munging up your statistics. |> |> BTR.COM is getting a ton of comp.*.3b1 and unix-pc.* material and is fed by |> only decwrl, mips and fernwood ... systems which Kris indicated are NOT |> feeding 3B1 properly. [Some info deleted] | Anyhow, the whole thing is probably meaningless, 'cause | some of the articles I saw as posted to only comp.sys.3b1 | could have started life as unix-pc.general, and then | become transformed to comp.sys.3b1 by B news aliasing | somewhere along the way. There WERE interesting things | in the data, like NO articles in "just" comp.sys.3b1 | from my main feeds. That's why I'm still wondering | whether att is carrying/forwarding comp.sys.3b1 as such. I don't know if this helps, but my main feed is att and I see comp.sys.3b1 only articles. I'll do some further checking to verify this, but I am 99.99% sure that they are passing comp.*.3b1. EBD -- Elliot Dierksen "It's such a fine line between clever and stupid." -- "This is Spinal Tap" Work) ebd@fang.att.com (407) 660-3377 Home) elliot@alfred.UUCP (407) 290-9744