Subj : Question: Multiple Backbone files
To : Paul Lentz
From : Jay Talbot
Date : Mon Mar 17 2008 11:33 am
Re: Question: Multiple Backbone files
>
> 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 t
> 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 anywmor
> (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
> exist anymore. The wording kinda makes that ambigous though, because it merel
> 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
> .na or .int list unless there is some kind of special distribution to where t
> echo is still moving and available.
>
> As a case in point on this process, when you came in and requested echos a lo
> while back that were dead-ish but still on the backbone, they ended up gettin
> staged in a queue... with a hope that someday they might just see some traffi
> I finally went through and got rid of all those queued echos because they wer
> 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. :-(
>
Naw, I figured I'd try and create some traffic on some of those old echos.
Maybe I'll submit some changes to echolist or something.
Thanks,
Jay
--- Virtual Advanced Ver 2 for DOS
* Origin: K5JAT HAM Radio BBS (1:124/2700)
