On Thursday 20 December 2001 23:10, Quel Qun wrote: >If it ain't broken, it ain't Cooker. Why couldn't it be its mirrors?
What is the cahin of command for the mirroring process any way? I have thought about asking the folks that manage my mirror (wtfo.com) about the mirroring inconsitancies, but, since so many cooker-warriors are having trouble with their mirrors--and many mirrors have been mentioned--it makes me think that there are problems farther up the line than the public mirrors that most of us use. I love cooker. It's like a whole new world each day. And I enjoy contributing in any way that I can, but the truth is, I'm no code ninja (unless you count ForTran or industrial machine tool control language) so the contributions I can make are a bit limited. That being the case, I can only point out little thingsv that I come accross. However, if no other coordination between Mandrake and the mirrors exists, I'd be willing to lead a team of local area mirror coordinators. A team of Cooker-Warriors that works with the administatoars of their mirrors to help keep the mirrors in a sane state. However, I think that the automatic processes that keep the mirrors up-to-date are fine. I think there is something wrong with the servers that the local mirrors sync to. If that is not the case, then only some (one) of the mirrors that we use would be broken, but they all seem to be having trouble. I propose that there is a problem with the source from which all of mirrors are mirrored. The Object, in image parlance, seems to be unstable, and the result is that the mirrors display a faulty image to the world. What I think we need to do is to fix the object, then the mirrors will give us a good image that we can all use. -- *Chuck*