Slashdot Mirror


Suitable Naming Conventions For Workstations?

spectre_240sx writes "We've discussed server naming a fair amount in the past, but I haven't seen much about workstations. Where I currently work, we embed a lot of information in our workstation names: site, warranty end date, machine type, etc. I'm of the opinion that this is too much information to overload in the machine name when it can more suitably be stored in the computer description. I'd love to hear how others are naming their workstations and some pros and cons for different naming schemes. Should computers be logically tied to the person that they're currently assigned to, or does that just cause unnecessary work when a machine changes hands? Do the management tools in use make a difference in how workstations are named?"

1 of 688 comments (clear)

  1. Re:University of Michigan model by bennomatic · · Score: 0, Offtopic

    I remember at the Open Computing Facility at UCB we had a naming convention of "natural disasters". Tsunami, Flood, Hailstorm, Sandstorm, Blizzard, Locusts... and a few more, but I'm starting to confuse it with the Passover story, since I don't think that Blood, Frogs and Darkness were part of the network.

    --
    The CB App. What's your 20?