Stellar said:Well, since you're doing this for educational and theoretical purposes, why don't you actually use a conventional, practical name for your machines instead of a random cliché name.
I second that.
The focus is on the eval of the server and what it can do. It'll appear more professional with a conventional name, and thus the focus will be on it's performance and not what the observer thinks of the name. Also, it sucks to have to waste moments of life explaining why you chose a particular name for a server to someone. Telling your boss that the files he needs have been temporarily moved to \\UberWanker\Corporate_Financial_Statements\ could be kinda akward. ... I guess if your environment is informal enough then that doesn't hold as much weight.
It can also help with organization and referenceability (is that a word?). It's easier to know that LnxWeb01 is the first linux server in a series that houses your web applications instead of trying to remember what all you had running on the Taco server. Also, it's easier to grow your network as you'll run out of food items before you do numbers.