Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!henry From: henry@utzoo.UUCP (Henry Spencer) Newsgroups: net.bugs.uucp,net.news Subject: uucp file naming conventions Message-ID: <3131@utzoo.UUCP> Date: Wed, 3-Aug-83 19:46:24 EDT Article-I.D.: utzoo.3131 Posted: Wed Aug 3 19:46:24 1983 Date-Received: Wed, 3-Aug-83 19:46:24 EDT Organization: U of Toronto Zoology Lines: 34 People talking to sites with fairly new uucps should be aware that there has been an important and subtle change in file naming. It seems to have snuck into the Berkeley stuff around 4.1c, and Peter Honeyman's latest uucp at allegra seems to do something similar, so perhaps it arrived in System N (N == 3, 4, 5, ...). The change is like this. In old uucps, data files being sent to a remote site ("remote") by my site ("sender") for use by rmail etc. have names starting with "D.remote". This does involve one slightly unfortunate possibility, in that if the remote site is receiving from two people at once, and their sequence numbers happen to be similar, collisions can happen. In the new uucps, the data files have names starting with "D.sender". This is more consistent -- all outgoing files contain the name of the sender, and since they also have sender-generated sequence numbers there is no possibility of collision -- but it is different. Moreover, there is some chance of collision when a new-uucp site sends to an old-uucp site, because old-uucp sites use names of that form for stuff that is headed the other way. This chance is fairly small if the old-uucp site has a really old uucp, because the new uucps also use the big-alphabet sequence numbers and hence usually have sequence numbers that an old uucp won't generate, but it's not zero. Beware. On the whole I think the change is an improvement, but I DO WISH IT HAD BEEN ANNOUNCED! It is really upsetting to find out about something like this by observation, and to have to spend some frantic moments convincing oneself that it isn't going to break anything. It doesn't break anything here, but other sites may not be so lucky. C'mon guys, how about letting us know what to expect? Network compatibility is not an area that benefits from surprise changes. -- Henry Spencer @ U of Toronto Zoology {allegra,ihnp4,linus,decvax}!utzoo!henry