>but it also included all the Sun SPARCstations the CS
>department operated (which were all named after dwarves from The
>Hobbit) and maine.maine.edu.

Tangent: the names of servers is what I use, at any given place of employment, to make an initial determination about how much power the IT guys have and how chill they are.

If they're all named after characters, places, weapons, or conveyances from fantasy and science-fiction? Someone with real decision-making power is kicking it old school.

If they all have names that are bland and functional, but usefully descriptive in some way, such as using syntax that conveys the servers precise location and function in a concise and easily extendable fashion, you're dealing with people who are big on keeping their infrastructure organized and locked down. They probably take the "engineer" part of "network engineer" very seriously. Look for a guy who is clean-shaven and wearing a tie unironically.

If they all have gobbledygok alphanumeric strings, then either they are paranoid about security or you're dealing with shitty outsourcing, incompetence, a CIO whose primary qualification is that he has an MBA, or some combination of all of the above. In which case, strap in.

-Merc
Keep Rat