gst@gnosys.svle.ma.us (Gary S. Trujillo) (02/15/91)
In <1991Feb12.072818.24706@i88.isc.com> botton@i88.isc.com (Brian D. Botton) writes: > Hi Netland Kit Builders, > This will probably be my last multiple group posting, I can't tell you how > glad I am to have the new groups, ;-)... I don't want to pick on Brian, but I selected this posting to follow up since Brian has been a regular poster for a while, and makes explicit mention of his dropping unix-pc.general from the Newsgroups line of his posting. My opinion is that not only should the unix-pc.* newsgroups be kept around for a few months, but that we should all continue to cross-post to them for this same time period (say through the end of April). Some of us are in the position of getting only a partial news feed, and having to negotiate with a busy system administrator at a net-neighbor site in order to pick up the feed of the new comp.*.3b1 newsgroups. After several weeks of poking and prodding and gentle reminders, I finally succeeded myself, but I'm sure I've missed quite a bit of traffic in the process. I thought the whole point of having a few months of keeping the unix-pc.* newsgroups around was to permit people to switch over gently and gradually, without missing anything. If people stop cross-posting to those groups, the whole scheme falls apart. Sure, it provides additional incentive to pick up the new newsgroups, but just because they're carried in the main- stream hierarchy is no guarantee that they're going to be easy for every- one to pick up, in fact, I can think of some folks who are at the end of a UNIXpc-based chain who are dependent upon net-neighbors who currently have no access themselves to the new newsgroups. So - I make an appeal: Please continue to cross-post to unix-pc.general and unix-pc.sources (I don't care so much about unix-pc.uucp and unix-pc.test) at least until the end of April. There, now I feel better! :-) Gary P.S. to people in this position - did you know that unix-pc.general has dried up to a trickle, while comp.sys.3b1 is going like gangbusters, and that there have been a number of goodies posted to the new sources newsgroup??? I'll post a list in unix-pc.general and in comp.sys.att to let you see what you're missing. -- Gary S. Trujillo gst@gnosys.svle.ma.us Somerville, Massachusetts {wjh12,bu.edu,spdcc,ima,cdp}!gnosys!gst
gst@gnosys.svle.ma.us (Gary S. Trujillo) (02/15/91)
In article <987@gnosys.svle.ma.us> gst@gnosys.svle.ma.us (Gary S. Trujillo) writes: [ my article about people having stopped posting to unix-pc.general/sources and comp.sys.att deleted ] > P.S. to people in this position - did you know that unix-pc.general has > dried up to a trickle, while comp.sys.3b1 is going like gangbusters, > and that there have been a number of goodies posted to the new > sources newsgroup??? I'll post a list in unix-pc.general and in > comp.sys.att to let you see what you're missing. Here is that list. It represents a newsfeed that's only been active a few days, so you can get some idea of what the volume actually is, and what you've been missing. (N.B. I am *not* cross-posting this message to comp.sys.3b1, so as not to bug those folks who are "in the boat.") comp.sources.3b1: v01INF1: Introduction to comp.sources.3b1 v01i001: My afio for even better floppy backups, Part0 v01i002: Kernel configuration files, version 2, Part01 comp.sys.3b1: Conferencing System ".GIF" files /etc/getty replacement 3B1 680X0 daughter boards (Posted from Thad) 3B1 bitmap screen at bootup 3b1 memory problems ALERT! Please read this message! AT&T Unix PC for Sale (possibly Trade) Anyone tried using a different keyboard on the 3B1? Combo card serial driver.... Comp.sources.3b1 traffic (was Re: ALERT! Please read th Comp.sys.3b1 volume (was Re: ".GIF" files) DWB for Unix-pc/3B1/Safari 4 Device Driver Docs Device Driver For Developers and Hackers Dial in on a 3b1. Disassembly on 68010+ Dr. [Mike] Shea's net experiment Dr. [Mike] Shea's net experiment [was: Re: Re:Thad' Graphics programs for the 3B1 HD2 shipping address verification HDB and async_main How do you change the ua 'kill' character??? Kendra login Ksh (newest) List of replacement hard drives for 3b1 Mikie and Dr. Shea OBM <--> Telebit incompatibility: SUMMARY PH broken PS command on 3b1 Paint_Power and 3B1 graphics Re:Thad's email address Return-Receipt's Rip Off from jb Technologies SMGR/Crontab Problem on 3B1 kills newsrun Screenprint queues, but doesn't print! Seeking modem pinouts Seperate HD & FD controllers? Source for WD2010's UUCP thru direct connection? Unix pc sluggishness when switching windows Unix pc sluggishness when switching windows (long) Unix-PC BOF at TCF'91 Ymodem procedures on 3B1 cnews with ksh - problems comp.sources.3b1 just showed up at copper fan, power supply questions how do I get ftp? kshs, and more kshs message for paul urie nroff with HPLJ III semi regular kit blurb su and/or ksh change history file's group and owner su and/or ksh change history file's group and ownership system backups for 7300 tape and 3b1 tty kill_char (@) problem (and how to fix it) wrastop() routines for 3b1 -- Gary S. Trujillo gst@gnosys.svle.ma.us Somerville, Massachusetts {wjh12,bu.edu,spdcc,ima,cdp}!gnosys!gst
kak@hico2.UUCP (Kris A. Kugel) (02/15/91)
In article <987@gnosys.svle.ma.us>, gst@gnosys.svle.ma.us (Gary S. Trujillo) writes: > Some of us are in > the position of getting only a partial news feed, and having to negotiate > with a busy system administrator at a net-neighbor site in order to pick up > the feed of the new comp.*.3b1 newsgroups. > . . . I'm sure I've missed quite a bit of traffic in the process. > > If people stop cross-posting to those groups, > the whole scheme falls apart. Evidently, that was happening even at hico2, where I pay real bucks to get remote feeds. Not every administrator has been swift to add the new groups to the distribution, and I think even some who wanted these changes were under the impression that our problems would be "fixed". Others put all unix-pc.test groups in their "alias" file (what happens when you have one half of a dual-posted article aliased to the other half?) In reality, I think we won't get proper distribution of comp.sys.3b1 and comp.sources.3b1 until: 1. we kick and scream 2. we figure out where the stoppages are 3. we get a couple more "create group" messages sent around 4. we get our groups into the regular "checkgroup" message > So - I make an appeal: Please continue to cross-post to unix-pc.general and > unix-pc.sources (I don't care so much about unix-pc.uucp and unix-pc.test) > at least until the end of April. > NO NO NO NO don't crosspost to unix-pc.sources - we already had that problem. [ --- but it was such a LITTLE articles. *sigh* ] I suspect that the cross-postings dissappear on systems that alias the new group. I think the solution to the comp.sources.3b1 lack-of-distribution is a proper archive (accessible by anom. uucp), so we won't miss anything. What I would have LIKED to have done, is to be able to compare which machines articles posted to unix-pc groups alone got to, and which machines comp.sys.3b1 articles got to. Then compare the lists to see which machines don't pass articles in comp.sys.3b1 (that were passing the old pc groups) to see who to talk to. Why are we aliasing unix-pc.test ANYWHERE? That would have been a good place to post copies of a test message, and there's really no purpose for the messages in the group except to test posting to the unix-pc distribution. *sigh* Well, I'll do what I can to identify the holes with the articles that are currently on hico2. If anybody has about a month's worth of articles WITH headers on their machine, maybe they can check this too. I'll come up with another script (probably with another bug :-) :-( ) that'll generate a list of machines (sort of like that I used to post the usage analysis a while ago) Meanwhile, check to make sure the machine YOU are on is carrying the new groups. If it's not, get your administrator to fix it. Kris A. Kugel ( 908 ) 842-2707 uunet!tsdiag.ccur.com!hico2!kak {daver,ditka,zorch}!hico2!kak internet: kak@hico2.westmark.com
mvadh@cbnews.att.com (andrew.d.hay) (02/18/91)
In article <1066@hico2.UUCP> kak@hico2.UUCP (Kris A. Kugel) writes:
[]
"file (what happens when you have one half of a dual-posted article
"aliased to the other half?)
you get *both* articles, and one doesn't get junked when you read the
other (at least at our site...).
--
Andrew Hay +------------------------------------------------------+
Ragged Individualist | JAAAAAAANE! |
AT&T-BL Ward Hill MA | HOW DO YOU STOP THIS CRAZY THING? |
a.d.hay@att.com +------------------------------------------------------+jeffrey@sci.ccny.cuny.edu (Jeffrey L Bromberger) (02/19/91)
In article <1991Feb18.113841.19560@cbnews.att.com> mvadh@cbnews.att.com (andrew.d.hay) writes: >In article <1066@hico2.UUCP> kak@hico2.UUCP (Kris A. Kugel) writes: >"file (what happens when you have one half of a dual-posted article >"aliased to the other half?) >you get *both* articles, and one doesn't get junked when you read the >other (at least at our site...). We're running Cnews here, and we get 2 copies of the article. There's only one on the disk (the multiple copies are linked), but it's still scary to see 100 new messages in comp.sys.3b1 (cause of crossposting to c.s.att and u-p.general)! j -- Jeffrey L. Bromberger System Operator---City College of New York---Science Computing Facility jeffrey@sci.ccny.cuny.edu jeffrey@ccnysci.BITNET Anywhere!{cmcl2,philabs,phri}!ccnysci!jeffrey