Thursday, January 25, 2007
The verbal ticks of old tyme NetWare admins
A conversation I read recently reminded me of this one. One of the things that caused me to grind teeth at my old job was the use of the word 'dsrepair' as a catch-all for anything run inside of dsrepair. This extended to some TIDs, which made the problem more wide-spread than my little corner of NetWare-land. The problem only started abating when it became possible to do some of the dsrepair tasks without actually loading DSREPAIR.NLM.
I'd see documentation like this one (generated internally, though my treacherous memory is telling me that a very early version of the NDS Health Check TID also had the bad phrasing):
The phrase, "run dsrepair until there are no errors," showed up a lot for a few years there. The conversation I read showed a clear case of an Old Tyme NetWare Admin maintaining the sense of dark mystery around dsrepair, which caused their young apprentice to go out into the world with an incomplete understanding of what this tool really does. This is a verbal short-cut that I'm glad has died out.
I'd see documentation like this one (generated internally, though my treacherous memory is telling me that a very early version of the NDS Health Check TID also had the bad phrasing):
What am I doing in DSREPAIR? Unattended health check? Timesync-check and sych-status check? Local trustee check? Check external references? Full database repair? WHAT? DSREPAIR does a lot of things. It is not VREPAIR, where it either works or it doesn't.
- Rconsole to the console
- Run dsrepair until there are no errors
- In NWAdmin...
The phrase, "run dsrepair until there are no errors," showed up a lot for a few years there. The conversation I read showed a clear case of an Old Tyme NetWare Admin maintaining the sense of dark mystery around dsrepair, which caused their young apprentice to go out into the world with an incomplete understanding of what this tool really does. This is a verbal short-cut that I'm glad has died out.
Labels: netware
