Xref: utzoo news.admin:14677 comp.mail.uucp:6710 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!apple!mauxci!problem!skypod!scott From: scott@skypod.guild.org (Scott Campbell) Newsgroups: news.admin,comp.mail.uucp Subject: Re: BITFTP Message-ID: <1991May26.144128.29432@skypod.guild.org> Date: 26 May 91 14:41:28 GMT References: <1991May18.204257.9520@iguana.uucp> <1991May25.202516.12961@zorch.SF-Bay.ORG> Followup-To: news.admin Organization: Skypod Communications Inc., Toronto, Ontario Lines: 55 In article <1991May25.202516.12961@zorch.SF-Bay.ORG> xanthian@zorch.SF-Bay.ORG (Kent Paul Dolan) writes: [comments on how uucico is broken and needs to be fixed] >The solution would have to be like Henry's; install >a new uucico that is _deliberately_ incompatible >with the old one, and bring it up (after suitable >testing) everywhere with a breathing sysadmin at >once to a schedule, and let the rest of the sites go >isolate until their sysadmins have been kickstarted >by the resulting incompatibility into fixing their >sites, too. The problem is, of course, that most of us do not have source for uucico. If you want to write an entirely new version of uucico that does not include any AT&T code, maybe I will try it after I have seen lots of other people running for several months. However, I talk to sites with several different mail/news/operating systems so any new uucico you write must work on SUN OS, waffle, minix, System V R3, System V R2 and FSUUCP for me to install it (Those are just my neighbours -- I am sure some of you out there talk to other systems). If my uucico won't talk to all of these sites than I won't use it. The uucico I have has its problems but everyone out there is pretty compatible with it and that is what counts. As long as no one sends huge files (ala BITFTP) through my site I can get by pretty well. Sure - I drop news on the floor sometimes -- but is your new uucico going to check my news spool to see that there is room before it accepts news and check the mail spool before it accepts mail and checks the uucppublic spool before it accepts uucp traffic? All this and handle whatever equivalents the DOS versions use? I think making a new uucico for all of the various versions of unix out there (and DOS and whatever else talks UUCP - VMS? VM? Multics? Ultrix?) would be relatively less trivial than you would think... Maybe I am wrong. Someone want to whip off a new version of uucico this weekend? I don't want to pay you for it by the way. scott p.s. on the BITFTP issue: I think that if UUNET and UUPSI set up FTP servers for their customers, then most of the valid complaints would go away. In fact, any site that provides UUCP links off of the internet should provide their own method of providing UUCP-FTP services. If the site upstream from you doesn't offer it then too bad. Any agreement for mail forwarding you have is usually with them and them alone. (ie. paying PSI for mail does not necessarily mean that you are paying for BITFTP access - how much of the money paid to PSI got passed along to Princeton?) -- Scott J.M. Campbell scott@skypod.guild.org Skypod Communications Inc. ..!gatech!dscatl!daysinns!skypod!scott 1001 Bay Street, Suite 1210 ..!uunet!utai!lsuc!becker!skypod!scott Toronto, Ont. (416) 924-4059 ..!epas.utoronto.ca!nyama!skypod!scott