Path: utzoo!yunexus!ists!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!fletcher From: fletcher@cs.utexas.edu (Fletcher Mattox) Newsgroups: news.config Subject: Re: bu name change and smail patch Message-ID: <7230@cs.utexas.edu> Date: 18 Nov 89 18:49:19 GMT Article-I.D.: cs.7230 References: <3115@husc6.harvard.edu> <42617@bu-cs.BU.EDU> <1989Nov15.173522.7002@b-tech.ann-arbor.mi.us> <14919@bfmny0.UU.NET> Organization: U. Texas CS Dept., Austin, Texas Lines: 22 In article <14919@bfmny0.UU.NET> tneff@bfmny0.UU.NET (Tom Neff) writes: >Also, while I could sympathize with a desperation patch to deal with >some old dinosaur of a pre-existing node with a dot in its name, >creating a NEW node in this day and age with a dot in the name is >LUDICROUS! Use another delimiter, or be prepared to spend hour after >hour dealing with net problems. Says here, life's too short... I've spent very little time "dealing with net problems" in the 18 months of existence of cs.utexas.edu as a UUCP host. Most of that time involved handing out the smail2.5 patch. And that was more than recovered in the time I *used* to spend explaining to users why we needed two different hostnames for the same machine depending on which email transport layer was used. Personally, I'm quite pleased with the results. If any of our 74 UUCP peers have been greatly inconvenienced by our dotted UUCP name, they were too polite to mention it to me. (The original author of the smail2.5 patch is one of our peers. He, no doubt, was a little frustrated 18 months ago. No longer.) cs.utexas.edu!fletcher