Documentation
Jul. 29th, 2004 10:23 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
sobriqueNo documentation at all is a bad thing.
However, it FAR surpasses the evil that is INCORRECT documentation.
I've been bashing my head trying to figure out WTF is going on with a server, what's up with the CD drive, and why it has stopped responding to the network after powering it down, and starting it up again.
The reason is, that there are TWO servers with the same name. The 'old' one, I'm rebuilding. The new one, the one in production, and the one I'm logging in to across the network.
So the 'production' version of this server has been down overnight, because I shut it down (remotely, because the serial terminal didn't seem to be responding) to attach a 'known good' CD drive.
If they'd not been labeled, I'd have been a little more careful in my checking. (although in all honesty, having found a server that meets my expectations, the outcome probably wouldn't have been much different)
However, it FAR surpasses the evil that is INCORRECT documentation.
I've been bashing my head trying to figure out WTF is going on with a server, what's up with the CD drive, and why it has stopped responding to the network after powering it down, and starting it up again.
The reason is, that there are TWO servers with the same name. The 'old' one, I'm rebuilding. The new one, the one in production, and the one I'm logging in to across the network.
So the 'production' version of this server has been down overnight, because I shut it down (remotely, because the serial terminal didn't seem to be responding) to attach a 'known good' CD drive.
If they'd not been labeled, I'd have been a little more careful in my checking. (although in all honesty, having found a server that meets my expectations, the outcome probably wouldn't have been much different)
