Subj : Remember
To   : Dale Ross
From : mark lewis
Date : Sun Aug 26 2001 05:01 pm

 RC>>> Why was Foxy chastized for hatching her file
 RC>>> into BACKBONE, despite maintaining the practice
 RC>>> of her predecessor, yet its ok for the Z1B?
>>
>> If Foxy had hatched a routing file into BACKBONE while
>> I was here I wouldn't have cared.  Can't speak for
>> anyone else.

 DR> The issue was that Foxy was NOT a member of ANY distribution
 DR> system and by definition did not have hatching privileges in
 DR> that area.

uh... WRONG!!! =I= started that particular "what's up with this" thing... why 
did i start it and bring it to light? because my system wasn't using the latest 
files that had been hatched... why had my system failed to use the latest 
files? because the files had been moved to another area... in some 10 years of 
running the same configuration, there was no reason for it to fail unless 
something outside had influenced it... i looked around, saw that the files were 
being hatched into another area and inquired (maybe a bit harshly and if so, i 
apologise) as to why the change... i was told that it was a mistake and that it 
would be corrected... it was corrected at the very next hatching...

 DR> Further, as I recall her uplink never consulted
 DR> with anyone on that issue. IRNROUTE is not hatched by the
 DR> Routing Committee into BACKBONE because they do not have
 DR> hatching privileges in that area.

 DR> There are some very distinct differences between the two
 DR> situations:

not the first of which is that it is two extremely DIFFERENT causes and 
situations and since i pointed out the problem in the first place, well...

)\/(ark

 
* Origin: (1:3634/12)

.