TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

RFC 1178: Choosing a name for your computer (1990)

220 pointsby rdpintqogeogsaaover 4 years ago

48 comments

curtis3389over 4 years ago
I use the wordlist from Oren Tirosh’s mnemonic encoding project: <a href="http:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20090918202746&#x2F;http:&#x2F;&#x2F;tothink.com&#x2F;mnemonic&#x2F;wordlist.html" rel="nofollow">http:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20090918202746&#x2F;http:&#x2F;&#x2F;tothink.com...</a><p>I can&#x27;t find the post that linked it, but it had a very nice scheme.<p>EDIT: found it: <a href="https:&#x2F;&#x2F;mnx.io&#x2F;blog&#x2F;a-proper-server-naming-scheme&#x2F;" rel="nofollow">https:&#x2F;&#x2F;mnx.io&#x2F;blog&#x2F;a-proper-server-naming-scheme&#x2F;</a><p>EDIT2: one-liner to get a random word from the file:<p>cat wordlist.txt | tail -n +2 | sed -E &#x27;s&#x2F;\s*(\w+)\s+&#x2F;\1\n&#x2F;g&#x27; | sed -E &#x27;&#x2F;^$&#x2F;d&#x27; | shuf -n 1<p>i.e. &lt;print file&gt; | &lt;skip first line&gt; | &lt;split lines into words&gt; | &lt;remove empty lines&gt; | &lt;choose random line&gt;
评论 #26055657 未加载
评论 #26055534 未加载
评论 #26055082 未加载
评论 #26056411 未加载
评论 #26059882 未加载
评论 #26055143 未加载
mrweaselover 4 years ago
This kind of naming is fine for small projects, and personal setups. In professional settings I would suggest using descriptive names and rely more on DNS.<p>It&#x27;s not that I don&#x27;t enjoy fun and personal naming schemes, it&#x27;s just that it&#x27;s a constant annoyance when dealing with a large number of different systems.<p>We&#x27;ve been hired to deal with different companies, who picks some random naming, cars, athletes, plants, cities and so on and it&#x27;s confusing as hell. How am I suppose to remember that Ford and Volvo are your two web servers? Now I need to maintain a list mappings for your servers and look them up every time I need to change your web configuration. Just call them prod-web01.company.com and prod-web02.company.com, it&#x27;s fine and everyone will be able to guess what those servers do.<p>You can also do web01.prod.company.com and web01.test.company.com, but while it looks cleaner (and I personally prefer it) is does hide the &quot;prod&quot; or &quot;test&quot; in most shells, so you constantly need to check that you&#x27;re not messing with a production box.
评论 #26054636 未加载
评论 #26055949 未加载
评论 #26054960 未加载
评论 #26055068 未加载
rgjover 4 years ago
Best naming scheme I ever saw was at Harbinger in the late nineties. They used the periodic system. The last octet of the IP address corresponded to the atomic number, and you could use the full element name, or the abbreviation. So carbon.harbinger.com was x.x.x.6 and c.harbinger.com was a CNAME to carbon. oxygen or o was .8 etcetera.
评论 #26057547 未加载
评论 #26058017 未加载
评论 #26059309 未加载
评论 #26060192 未加载
einpoklumover 4 years ago
Brief summary of the RFC (to save you the read):<p>* Don&#x27;t overload other terms already in common use.<p>* Don&#x27;t choose a name after a project unique to that machine.<p>* Don&#x27;t use your own name.<p>* Don&#x27;t use long names.<p>* Avoid alternate spellings.<p>* Avoid domain names.<p>* Avoid domain-like names.<p>* Don&#x27;t use antagonistic or otherwise embarrassing names.<p>* Don&#x27;t use digits at the beginning of the name.<p>* Don&#x27;t use non-alphanumeric characters in a name.<p>* Don&#x27;t expect case to be preserved.<p>* Use words&#x2F;names that are rarely used.<p>* Use theme names.<p>* Use real words.<p>* Don&#x27;t worry about reusing someone else&#x27;s hostname.<p>* There is always room for an exception.
shagieover 4 years ago
One company that I worked at... while the hardware people had their boring &quot;r17s4ad&quot; type name (rack 17, shelf 4, application, development), our team used the naming scheme of Caribbean islands. This worked rather well.<p>Unfortunately, I only remember the test and production server names. The test systems were &quot;Trinidad&quot; and &quot;Tobago&quot;. The production systems where &quot;Nevis&quot; and &quot;Nassau&quot; (the app started with an &#x27;N&#x27;).<p>The thing that made this work really well was that the first syllable hinted on what the rest of the word would be and then everything beyond that reinforced that you read it right. This even was the case that foreign accents, while slightly off still reinforced the &quot;you heard this right&quot;.<p>The machines _also_ had names of &quot;test01&quot; and &quot;test02&quot; or similar... but we (as devs) never used those names because you had to listen to the end of it to be sure that you had the right machines.
cy6erlionover 4 years ago
Shameless plug, CLI for reading IETF RFCs. <a href="https:&#x2F;&#x2F;github.com&#x2F;cy6erlion&#x2F;ietf" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;cy6erlion&#x2F;ietf</a><p>You will read this RFC like this:<p>$ ietf -n 1178
评论 #26055830 未加载
评论 #26055074 未加载
indentitover 4 years ago
&gt; Nobody expects to learn much about a person by their name.<p>That&#x27;s a good point, but humans are very different to computers - machines (be they physical or virtual) are provisioned for a specific purpose (even if that is to be &quot;Fred&#x27;s PC&quot;), whereas humans need time to grow and can decide for themselves what to do as a career &#x2F; what their hobbies will be, and change it any time.<p>But realistically, yes, the RFC is right that you may end up with machines whose purpose changes or multiple machines have the same purpose etc. But when they don&#x27;t, it is much easier to have meaningful names. If you will name them differently, then please make sure all developers can access the list&#x2F;mapping document and it is kept updated. It&#x27;s frustrating if you want to investigate some production problems but end up looking at the wrong server&#x27;s logs because devops didn&#x27;t tell anyone they moved an application &#x2F;website etc.<p>I like someone else&#x27;s comment about app01 being easier to reason about and recreate than something named more specifically, and in the modern world, its easy to spin up a new docker instance or VM so there&#x27;s less need to &quot;let&#x27;s just add this small service on that machine because it has spare capacity&quot; (where capacity could be CPU&#x2F;RAM etc.)
diftrakuover 4 years ago
A long-time personal favourite naming scheme of mine has been Pokemons (and by extension, Digimons).<p>There&#x27;s a good selection, it&#x27;s pretty varied and there&#x27;s no shortage of em (assuming you don&#x27;t exceed 100-200 new systems in a 3 year period). This also has an accidental side-benefit of not being tasked to name new hosts at work, unless your really want to call the new database server Stufful, for example.<p>Another thing to keep in mind with more descriptive hostnames like `database`, is to serialize them from the start. It&#x27;s a very minor thing but after you have three hosts with one of them missing the serialization, it&#x27;s going to stand out like a sore thumb and it could be a major undertaking on changing that name where it&#x27;s used.<p>When it comes to project names, there is a certain level of permanence that name (or codename) is going to have. Once chosen, that name will be thrown around in the codebase almost universally. The same does apply to the hostnames, at least in part when it comes to configuration files (and by extension, certain hard-coded hostnames that could linger around in the code years after the host in question has been decommissioned).
评论 #26057864 未加载
hyperrailover 4 years ago
The weirdest naming scheme for computers I&#x27;ve seen is the one used some years ago by my college: It named Linux workstations after Linux kernel committers&#x27; email usernames!<p>There were the better-known folks like linus (Linus Torvalds [1]) and gregkh (Greg Kroah-Hartman [2]), but also relatively more obscure people, like shemminger (Stephen Hemminger [3]) and stelian (Stelian Pop [4]).<p>I didn&#x27;t recognize most of those names at the time, but now that I do, I wonder what those people would have thought about having a large organization&#x27;s computers named after them. A bit creeped out, I would think.<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;torvalds" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;torvalds</a><p>[2] <a href="http:&#x2F;&#x2F;www.kroah.com&#x2F;log&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.kroah.com&#x2F;log&#x2F;</a><p>[3] <a href="https:&#x2F;&#x2F;www.linkedin.com&#x2F;in&#x2F;networkplumber&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.linkedin.com&#x2F;in&#x2F;networkplumber&#x2F;</a><p>[4] <a href="https:&#x2F;&#x2F;www.popies.net" rel="nofollow">https:&#x2F;&#x2F;www.popies.net</a>
sillysaurusxover 4 years ago
We had to solve this problem for our TPU management system: <a href="https:&#x2F;&#x2F;www.tensorfork.com&#x2F;tpus" rel="nofollow">https:&#x2F;&#x2F;www.tensorfork.com&#x2F;tpus</a><p>The most sensible naming scheme for us was to distinguish them by index. But there were two important differences: TPUs have many sizes, which means some are larger than others; if you&#x27;re using a v3-256, you&#x27;re very likely the only researcher doing so. They are also distinguished by type; v3 is more powerful than v2. Finally, they are region-based; the less powerful v2&#x27;s are in the US, whereas the v3 fleet is mainly EU based.<p>That led to the convention of tpu-v3-8-euw4a-1, tpu-v2-256-usc1a-0, and so on.<p>The &quot;tpu-&quot; prefix might seem redundant, but I find it&#x27;s helpful in conversation. That&#x27;s a personal preference though, and if I had to do it again I&#x27;d probably drop the tpu- prefix entirely.<p>I found this scheme was horrible for VMs though. TPUs are often used for specific training runs, and the scheme above is easily added to bash files &#x2F; config scripts. But for VMs, you&#x27;re often SSH&#x27;ing into them all the time.<p>Ultimately we started naming the VMs after the researchers who originally needed them. Our current primary training box is song.tensorfork.com, named after researcher songpeng who it was created for. So the SSH scheme was pleasant: song@song.tensorfork.com for him, shawn@song.tnesorfork.com for me, arfa@, aydao@, etc.<p>When arfa neded a VM, I simply named it arfa.<p>All other more complicated naming schemes failed with time. No one (including me) could remember long VM names, let alone ones with numbers in them.<p>The other scheme that persisted was to use anime characters, as emersion mentioned. Tensorfork itself runs off of vegeta, which is my personal Hetzner server. &quot;goku&quot; was one of our primary workhorses at one point, due to its large VM size.<p>Our final two VMs are named &quot;test&quot; and &quot;nuck&quot;, which also seem to work quite well (much to my surprise). &quot;Is test down?&quot; is almost completely unambiguous. And it&#x27;s easy to remember which one is which: &quot;nuck&quot; is in Canada, so therefore &quot;test&quot; is the one in europe.<p>A pattern emerges here: most of our VM names are <i>short, four-letter identifiers</i>: arfa, song, test, nuck, goku, with vegeta being the standout. All other conventions failed with time.
kralljaover 4 years ago
<a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;List_of_Greek_mythological_figures" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;List_of_Greek_mythological_fig...</a> has been good for naming my workstations for decades. Dual-boot scenaria can use Roman&#x2F;Greek names for the Mac&#x2F;Windows or Win&#x2F;Linux “personalities” of the same physical machine.
评论 #26057257 未加载
thomover 4 years ago
For personal stuff (and even early machines for some companies which blurred the lines) I always chose the names of forests in the Magic: the Gathering multiverse. I try and help keep this page updated purely for that purpose:<p><a href="https:&#x2F;&#x2F;mtg.fandom.com&#x2F;wiki&#x2F;Forest" rel="nofollow">https:&#x2F;&#x2F;mtg.fandom.com&#x2F;wiki&#x2F;Forest</a><p>These days, for work, it’s just boring unambiguous stuff. I think with more cloud infrastructure and the rarity of shared unix servers with home directories for people, it’s rare that I have any emotional investment in a machine. They’re basically soulless now.
评论 #26055302 未加载
jjiceover 4 years ago
For personal machines I use fiction locations from media I enjoy. My laptop is Hyrule, my desktop is Konoha, and my Pi is MotherBase, but I spell mine all lowercase.<p>For servers I use for my roommates and I (Jellyfin and the like), we name them after the quirky students that go to our university that we appreciate.
kuterover 4 years ago
I was expecting this to be a April Fools RFC [0]. I was disappointed when I checked the date.<p>[0]<a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;April_Fools%27_Day_Request_for_Comments" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;April_Fools%27_Day_Request_for...</a>
评论 #26054157 未加载
评论 #26054537 未加载
评论 #26055458 未加载
评论 #26055484 未加载
emersionover 4 years ago
Use anime character names. That way you have an excuse to collect cute artwork for these machines.
评论 #26054538 未加载
评论 #26055233 未加载
ddtaylorover 4 years ago
Kind of weird when it lists <i>names of killers</i> as a theme name...
评论 #26060202 未加载
walrus01over 4 years ago
Based on the long response time, I think we&#x27;ve hugged the IETF httpd to death which is somewhat funny considering who runs it.
rbanffyover 4 years ago
Shameless plug: <a href="https:&#x2F;&#x2F;www.npmjs.com&#x2F;package&#x2F;nsaname" rel="nofollow">https:&#x2F;&#x2F;www.npmjs.com&#x2F;package&#x2F;nsaname</a><p>It probably needs updating. It&#x27;s been a while since the last large leak.
hopplaover 4 years ago
For some reason, when doing a fresh OS install, the hostname step is the bottleneck and takes too long to complete. Distros should really prioritize optimizing this part of the installer!
mcguireover 4 years ago
Back when I was a sysadmin at a university CS department, we always picked namespaces for machines---everything in a given namespace had related names and were identical (or nearly identical) machines. If someone mentioned toque or glenfiddich, you could tell what lab they were in and what kind of machine they were.<p>I always wanted to use &#x27;Starships from Iain M. Banks&#x27; science fiction&#x27;, which is why no one ever listened to me.<p>For personal machines, I have been using adjectives that start with &#x27;i&#x27;.
评论 #26059840 未加载
gorgoilerover 4 years ago
Computer names are like function names. The edge of your system <i>needs good names</i>.<p>The ones in the middle can quite happily be anonymous &#x2F; referred to only by their address.
IgorPartolaover 4 years ago
I use Harry Potter character names. There were hundreds of the mentioned off hand in the books, so I usually use obscure ones. They have the benefit of being easy to pronounce and spell: Mafalda Hopkirk, Silvanus Kettleburn, Irma Pince, etc.<p><a href="https:&#x2F;&#x2F;en.m.wikipedia.org&#x2F;wiki&#x2F;List_of_Harry_Potter_characters" rel="nofollow">https:&#x2F;&#x2F;en.m.wikipedia.org&#x2F;wiki&#x2F;List_of_Harry_Potter_charact...</a>
评论 #26056291 未加载
chunkyksover 4 years ago
The biggest mistake I&#x27;ve made, once myself, and once inheriting a network someone else passed on to me: Picking a theme that&#x27;s too small.<p>I inherited a couple servers &quot;jules&quot; and &quot;vincent&quot; [after the Pulp Fiction characters]. I added mia and ringo, I started finding remaining names weren&#x27;t great. Butch is a bit homoerotic. &quot;zed&quot; is one I&#x27;ve used, but I can&#x27;t wait for the day someone without a sense of humor figures that out. I&#x27;ve also used &quot;chopper&quot; now. &quot;Marsellus&quot; is too hard to spell. &quot;watch&quot; is next on my list, but that&#x27;s really dredging the bottom of the barrel.<p>The other network, we used Scooby Doo characters because there was <i>no way</i> that room would ever have more than five systems... of course the next tranche of added systems had to go with a totally different theme. So the room now has the mystery machine occupants, and ... dragons from how to train your dragon.
pawelmiover 4 years ago
Two hardest problems in IT: naming, cache invalidation and off by one.
Nvorzulaover 4 years ago
Some time ago I got into the habit of naming my home network after Pokemon that I happen to thought fit well. My Windows desktop is Charizard and it&#x27;s Ubuntu dual boot is DarkCharizard. My fileserver&#x2F;Docker box is Metagross. My wireless SSID is Raichu, my laptop is Pikachu, and my phone is Pichu. And so on.
mrlonglongover 4 years ago
At a previous employer many moons ago we had three SunOS servers named Shooty and Bangbang after these two clueless coppers in Hitchhiker&#x27;s guide to the galaxy. The third was named tartsdrawers as it was up and down all the time. Good memories.
shaftwayover 4 years ago
Periodic table entries here. Lots of ways to divide that space, but generally for me laptops were lighter elements, desktops heavier, and servers the heaviest. Virtual machines were all heavily radioactive elements (e.g. Uranium and Plutonim). Can&#x27;t remember what I used the noble elements for.<p>Now I don&#x27;t bother and just select the default. Or name it after where it&#x27;s going to be, or what it&#x27;s going to do, or when I got it. If I&#x27;m going to repurpose or move it I&#x27;ll probably just reimage it anyway.<p>The wifi is still named &quot;Periodic&quot; though and it still uses a chemical makeup as the password (e.g. c3h5n3o9).
jlgaddisover 4 years ago
At the risk of showing my age...<p>In my own private home lab -- which has grown way too large -- I like using names of the Garbage Pail Kids [0] as hostnames.<p>There&#x27;s a few benefits to this naming scheme, when dealing with physical machines at least: 1) you can usually find a name that suits the &quot;temperament&quot; of the particular host and 2) you can tape the trading card to the host (or the rack, next to it) to make finding &#x2F; identifying it easier.<p>--<p>[0]: <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Garbage_Pail_Kids" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Garbage_Pail_Kids</a>
acomjeanover 4 years ago
Like a lot of things, people can remember names of things better than numbers. Genes for example, it’s easier to remember their names lz, wnt, than their associated gene Id number. But like stars and many other things there are too many to give each a unique name.<p>Naming can make sense, our old cluster was named after orchestra parts. When you logged In you where placed on the lobby. The machines where clustered (violin01, violin02, tuba01) and grouped by function types (percussion were the web servers)<p>New cluster it’s login01,login02 , the work cluster names I don’t remember...
评论 #26056766 未加载
评论 #26054892 未加载
chewxyover 4 years ago
I have named my machines after Doctor Who planets for the last 18 ish years. All new machines start as Gallifrey (workstation) or TARDIS (laptop).<p>Then as they stop being my primary devices they get other planet &#x2F; ship names. The torrenting machine was suitably called Skaro. :p<p>Two exceptions are my PiHole and OctoPi. The old PiHole used to be called TimeLock but when I upgraded I didn&#x27;t keep the name
评论 #26072796 未加载
rphlnover 4 years ago
The naming scheme I settled on for my devices was using ship names from World War 2.<p>- Device size and computing power maps roughly to the ship size: my desktop is named after a battleship, while my Kindle is named after a destroyer.<p>- Servers are always named after carriers. It just made sense to me somehow.<p>- Like the warships, the names can eventually get reused as the devices are replaced.
sellymeover 4 years ago
Sometimes when reading documents from the infancy of the internet it&#x27;s difficult to get a sense for the online environment at the time it was written.<p>For this one that difficulty disappeared very quickly once I got to the section where the existence of a computer in Tahiti was indeterminate.
bombcarover 4 years ago
Given that it seems you don’t upgrade Linux Instalaciones between major revisions - I use short names that are unique in the first character or two and code the os&#x2F;version. Sure it doesn’t scale much but I don’t have many servers and ssh u&lt;tab&gt; gets me where I need to be.
lamontcgover 4 years ago
Over 5 years at working at Amazon (quite some time ago, I don&#x27;t know what they do now) and we happily violated &quot;no domain names&quot; without any issue for linux servers. If you don&#x27;t have linux boxes that span different networks it doesn&#x27;t cause a problem to have server have one single domain name and have the hostname be the same. Linux boxes aren&#x27;t proper security devices or router so don&#x27;t use them as that and don&#x27;t mutihome them. The routers and switches were given short names. These RFCs simply don&#x27;t capture that there are rules you can adopt (and if you&#x27;re big enough -- which is not terribly big) then you can discard some of these suggestions completely. There is not a one-size-fits-all. I ignored this RFC&#x27;s suggestion at a fairly massive scale for 5 years and never had an issue.<p>Also don&#x27;t fall into the trap of just assigning random serial numbers to servers. I later worked somewhere that did this and it makes it difficult to communicate about the servers in the middle of outages. I&#x27;ve had communication issues where I&#x27;ve been talking to another engineer and I was using the first hex digits of the server name and they were using the last as shortcuts and we thought we were logged into different servers and it was the same one. You hardly ever want humans dealing with your server names, but when humans do need to use your server names it is one of the times that really matter because shit is on fire.<p>Group them by single purpose of what the cluster does with some kind of incrementing number. The idea to use theme names and not &quot;project&quot; names is also deeply 100% wrong. When you have 100,000s of servers you run out of theme names and you&#x27;ll fail to remember the name schemes in the middle of an outage. Name them after what the servers do, and keep them more or less reflecting their purpose. Consider carefully some kind of numbering scheme to keep the short names unique across datacenters so you don&#x27;t have a dozen foo-101 servers. You may want to use incrementing serial numbers for both datacenters and cluster members or something so &quot;foo-1-101&quot; and number your datacenters (or logical cluster number if you&#x27;re really big and stamp them out 30,000 at a time or something).<p>Oh right this is the RFC from 1990. Yeah, shit has changed, this RFC needs to evolve.<p>Back in 1990 when this was written a single system admin hand managing 20-30 servers was a lot. Web didn&#x27;t exist. I can&#x27;t recall any kind of load balancing or much clustering. You might have SunOS boxes running RIP doing routing across internal subnets that were 10baseT. NAT and firewalls weren&#x27;t used much at all and servers would just sit on public IPs. This RFC is prehistoric.
评论 #26072864 未加载
评论 #26057252 未加载
pvinisover 4 years ago
I&#x27;ve had a nice scheme for naming my devices for a while. I have a list of my devices here, with explanations. <a href="https:&#x2F;&#x2F;pvin.is&#x2F;post&#x2F;my-device-naming-scheme" rel="nofollow">https:&#x2F;&#x2F;pvin.is&#x2F;post&#x2F;my-device-naming-scheme</a>
intrasightover 4 years ago
I am fondly recollecting my time as an undergraduate at CMU in the 80s. All the machines were named from cities and towns in Pennsylvania. Old-school bare-metal on-prem indeed. That time has largely passed as machines are ephemeral. Functional names make more sense now.
tyingqover 4 years ago
Resource tags, like the ones supported by Vmware, AWS, and other cloud providers would be more important to me than a server name. I suppose for old-school bare-metal on-prem, you could put tags in DNS TXT records and some database.
cogburnd02over 4 years ago
Sci-hub has the pdf of the original in Comm. of the ACM under the DOI <a href="https:&#x2F;&#x2F;doi.org&#x2F;10.1145&#x2F;68814.316006" rel="nofollow">https:&#x2F;&#x2F;doi.org&#x2F;10.1145&#x2F;68814.316006</a><p>Has a nice Far Side too.
gbolcerover 4 years ago
AT UCI, they chose Paris Metro stops. All of them were hard to spell and pronounce, so we always made up shortened aliases.
dehrmannover 4 years ago
On thing I&#x27;ve seen work well for corporate networks is use a different domain for infra than for public-facing servers.
dls2016over 4 years ago
I use Simpsons character names for VMs: FatTony, SexyFlanders, Krustofsky... never ending supply of names.
评论 #26057634 未加载
utf8over 4 years ago
Some good suggestions to name Apple devices so that the life is easier when looking at Find My.
JoeAltmaierover 4 years ago
Or your robot vacuum cleaner! My nieces have various names - Oni, Bob. Ours is named Puck.
BlueTemplarover 4 years ago
&gt; don&#x27;t use antagonistic or otherwise embarrassing names.<p>Like &quot;git&quot; ? ^^
mercoraover 4 years ago
for virtual machines i tend to use names that belong to some other entity and call the hypervisor after that. for example Saturn and its moons, Africa and its countries or some authors and their works.
BlueTemplarover 4 years ago
&gt; (&quot;earth&quot; is not yet a domain name.)<p>It is now !
KineticLensmanover 4 years ago
&gt; Certain sets are finite, such as the seven dwarfs. When you order your first seven computers, keep in mind that you will probably get more next year.<p>We ran into this years ago when we named our machines after the Marx Brothers. We started out with Harpo, Groucho and Zeppo. When two more arrived, we used Chico and Gummo. IIRC we added Karl, Deutsche, Skid, Birth and Spencer before giving in and adopting a proper &#x27;cattle not pets&#x27; convention (which, by the way, isn&#x27;t covered by TFA).
评论 #26054585 未加载
moonbugover 4 years ago
what&#x27;s tomorrow, a thread on last night&#x27;s dreams? No one cares how you name your computers.
评论 #26059908 未加载