Subj : Question: Multiple Backbone files
To   : Jay Talbot
From : Paul Lentz
Date : Sun Mar 16 2008 10:11 pm

Jay Talbot wrote in a message to All:

JT> @MSGID: 1:124/2700 00006B96
JT> @PID: VA-VFIDO 2.10 96100117
JT> Ummmm.... Is there a way to get all the backbone in one merged file?
JT> Perhaps a .NC (C for Complete)? I've already come across some echoes
JT> that I want to carry, but can't because it's not in my upstreams
JT> echo list. 

Well... Your upstream (me! :-) ) did check and the dozen or so requests you 
tried to areafix (and got a "not found" message) and I found that they were not 
in Backbone.na or backbone.int... the other backbone lists that are still 
hanging around are for the WWB, PAO and the Z1B and not really viable anywmore 
(read *REALLY OLD*). I don't know if those BACKBONEs are still even around(???)

They are listed in the backbone.no... but of course that means they sorta don't 
exist anymore. The wording kinda makes that ambigous though, because it merely 
states that the low to non-existent traffic got them on the .no list, but it 
doesn't really say that they are no longer distributed. Most hubs will go by 
the
..na or .int list unless there is some kind of special distribution to where the 
echo is still moving and available.

As a case in point on this process, when you came in and requested echos a long 
while back that were dead-ish but still on the backbone, they ended up getting 
staged in a queue... with a hope that someday they might just see some traffic. 
I finally went through and got rid of all those queued echos because they were 
no longer listed in backbone.na and they never did see any traffic.

Have you heard of recent traffic in these echos that you were hoping to get 
hooked up to? Then, that would be a problem. :-(

*Paul*
--- timEd/386 1.10.y2k+
 * Origin: Dumb Guy's!!! (1:124/5025)

.