Subj : linked
To   : Bob Short
From : mark lewis
Date : Wed Dec 11 2002 11:41 pm

BS> I just did a 30 day rescan of the echo, and was returned
BS> one message. If this is due to a pass-thru on my uplink's
BS> system, please let me know what has beed going on the
BS> last month or so (in nutshells please).

i go back to Nov 11 and yours is the 24th message... frakn vest's reply is 25
and this one will be 26... there hasn't been a whole lot going on because some
backbone distributions do not view this area as an "official" "admin-type"
"carry all the time" echo ;-( thus many systems dropped it when they removed it
for low traffic... some of us are still waiting on the "moderator" to
(re)request it to be carried... additionally, the "moderator" may want to alter
the echo's description in the echolist to make it more "official" appearing...

i use "moderator" in quotes because the "moderator of record" has traditionally
been a custodian and contact person only for the purpose of updating the elist
to avoid this very situation...

additionally, traditionally, this has been the gathering place of developers
and spec creators while the FTSC gathered here and in other places...
FTSC-PUBLIC was created by the last FTSC as a place akin to the IC, and
ZCC-PUBLIC echos... somewhere where folk could talk with the FTSC rather than
what has been taking place in there recently... IMO, since there is an election
for FTSC members, FTSC-PUBLIC should be totally about the election and nothing
else until the end of the election...

anyway, that's all that... i didn't rescan the existing messages to see what
they were about though i have read them and possibly even wrote a few of
them...

)\/(ark


* Origin: (1:3634/12)