On Sat, 2002-10-19 at 21:28, Ron Hudson wrote: emu hen uru

tic -- -Linc Fessenden In the Beginning there was nothing, which exploded - Yeah right...

"And isn't sanity really just a one trick pony anyway? I mean, all you get is one trick, rational thinking. But when you're good and crazy, oooh, oooh oooh, the sky's the limit!" -- The Tick

At my last job, I always named servers after precious stones - too many sites I saw were using greek/roman gods or planet names.... so a partial list would be.... jade amethyst amber coral garnet ruby emerald diamond sapphire onyx opal But at the new job, we're using things associated with the grateful dead heh --- [This E-mail scanned for viruses by Declude Virus]

On Mon, 21 Oct 2002, David A. Woyciesjes wrote: For starters, you could network them all using a token ring. Bilbo, Aragorn, Legolas, Samwise, Pippin, Gimli, Galadriel, Arwen, Eowyn, Saruman, Sauron, Faramir, Theoden, etc... -brian.

At UC Berkeley: kim noVAX ernie koVAX

Well, I've seen enough and can't hold back... Back at Purdue, the machines in the main machine room were all named after Arthurian legend. Of course, the VAX8800 was Arthur. The Suns we had in the OS lab were named after trees. IIRC the ones running SunOS were named after hardwoods and the ones running XINU were named after softwoods. When I started teaching at Rhodes, I named our new network machines after intelligent computers from SciFi. They included: hal, sal, colossus, guaridan, zen, harlie, p1, mcp, joshua (ok, I forgot I really should have called it wopr), m5 and skynet I now have most of those machines here at home. The laptop I'm using now is nomad and my gateway machine is orac. Of course, my daughter insisted that I name her machine fluffy after the three-headed dog in Harry Potter. My wife's machine is called Taliesin (another Arthurian reference). Brian L. Stuart

Oolcay itay.

In message <Pine.BSF.4.44.0210220713350.75559-100000(a)grumble.deltasoft.com>om>, Ge ne Buckle writes: Not that I recall. I do remember watching the bookstores for a while looking for other books by him. Back in college, P1 was considered as a sort of unofficial prerequisite for CS majors. I really need to take time to read it again someday soon. Brian L. Stuart

I personally don't name machines by "what they are", for very good reason. Plus, no one but the admin group uses the "real" machine names, also for very good reason. Here's some illustrative examples... If you call an HP K370 "k370.somedomain.com", and then upgrade it to a K570 by just adding a few more cpu cards, do you really want to still call it K370.somedomain.com? If not, you have to retrain your user community and this is a pain, and kinda defeats the whole idea of using meaningful names so people don't need to know IP addresses. As a result, machine names generally indicate what they are used for... so a machine that processes orders might be "orders.somedomain.com". However, this can cause issues unless the second point below is heeded... If you give machines names that indicate "what they do" rather than "what they are", you can then run into problems if you do clustering, or if a machine goes down for a while (hardware issues), or more commonly, if for load reasons you need to move an application to a different machine. Thus - (IMHO), machines should have a "real" name that has nothing to do with what it is or what it does. These real hostnames are typically what admin people will use. Then, define CNAME's for the applications that the machine serves up...this is what "users" use. Here's a realworld example. A particular webserver is named "joe" (at this place, the naming scheme is baseball related, so machines get names like hank, cy, willie, mark, sandy, ozzie, etc.). It serves up images via the web for bulk email that is sent out to subscribers that has links in it back to images on "joe". However, users inside the company who put up these images via sftp go to the cname for the machine which is "image". The benefit of this is, if joe ever gets too heavily loaded, or goes down or whatever, I can easily change the "image" cname to point to a different webserver here and move the content to it (in the case of a web server cluster, the content is already there). Thus, the admin group knows "joe" is down, it doesn't respond at "joe". But the emails sent out reference http://image.somedomain.com, and that is what the users inside the company sftp to, so to them, everything still works as it did before while some other machine is doing that task. The big benefit is admins know the machines by their real name, as their job focus is machine-centric. However, we can shuffle applications and services around to other machines whilly-nilly, and we don't have to tell the users anything because they still use the other name that is "service" specific. After all, admins should be spending their time watching system resources generally. If one machine starts getting sluggish, they need to be able to move one or a few of the services that machine provides to a less loaded machine - and they should be able to do this virtually instantaneously, without the users having to do anything different or know a different machine name. Heck, most users have the "machine name" stored in their terminal emulation software, and dont even know what it's called". And half of them don't know how to change it themselves. This becomes especially important (and required) when you do clustering. The most common example is web farms, but it applies equally to any service. If you have 30 machines that ALL serve up content for the single URL http://www.bigcorp.com you certainly can't name them all the same name. And if one of the machines in the cluster dies, you also can't have a 1/30th "hole" in your services. The above paradigm addresses this nicely. To take it one step further, we use "wackamole" - a free unix program that assures certain IP addresses are always available. It will shuffle the group of addresses amongst multiple machines on the fly. If a machine goes down, it moves it's ip addresses equally among the remaining machines in the cluster. Most people accomplish "clustering" with round robin DNS, which is great, but you run into the problem of if one machine in the round robin list dies, anyone who gets the address of the down machine resolved gets nothing. wackamole solves this problem very nicely. And as you might guess, doing things like this doesn't work well if you are using machine names unique to each machine. Jay West --- [This E-mail scanned for viruses by Declude Virus]

Rumor has it that Chris Lamrock may have mentioned these words: [snippety-doo-dah...] Ah welllll... I suppose if this thread will never die, I might'swell jump in... ;-) For the computers around my place that need names for a network or something, I really don't get too inventive... the wife's machine is "maggie" (her name), mine's "zmerch" (the userid I've had for almost 20 years), the tivo is "tivo", the laptop is "zdell" (another one already had "dell" so I had to make it unique...), etc.... However, when I built my first dual-processor machine [1], and someone would know what how fast it could do something, I'd refer to it as "Goon." >> "Well, I suppose I could spark up Goon when I get home & find out..." After it fried <sniff> and I built a 1Ghz P3, I had gotten out of that habit. When that machine wasn't fast enough to transcode MPEGs (for SVCDs) and I built a dual-processor Athlon box, I started doing it again on rare occasions, but it's not like it once was... Otherwise, the *only* other things I've named that one would not normally associate with naming (like kids & pets... ;-) is my Oscilloscope (Tex - because it's a Tektronix, mainly just to shorten the name), and a hat (a Russian enlisted Army winter cap I picked up in ex-East Berlin) only because "Vlad" or "Vladimir" was shorter than "a Russian enlisted Army winter cap I picked up in ex-East Berlin" and occasionally confused the listener... Usually the stupid ones... ;-) And now back to our irregularly scheduled drivel... ;^> Laterz, Roger "Merch" Merchberger [1] a Dual P2-350, when 550 was the biggest, baddest CPU on the planet, dual 9G 10Krpm SCSI drives software raided... Faster than most people's servers, it really *was* a goon at the time... -- Roger "Merch" Merchberger -- sysadmin, Iceberg Computers zmerch(a)30below.com What do you do when Life gives you lemons, and you don't *like* lemonade?????????????

Well, seeing as we're on the subject of machine names... I asked my brother for some suggestiosn. He picked "goku", "gohan" and "goten" - all characters from the anime series "Dragonball Z". I told him that I wasn't about to use names from a cartoon series. So he half inched (stole) my admin password, logged into my server and then changed the names on all the machines remotely. To characters from the "Digimon Tamers" TV series. I told him NEVER to touch the server again, deactivated his account on my server for two hours and added his machine to the blocklist. Frankly, I'm too lazy to change the names on the machines back. My main machine's official name is Phoenix - so-called because it survived a botched BIOS flash (it's a PC running Linux). The server is known as "Defiant" - from Star Trek: Deep Space Nine, my laptop goes by the nickname "Voyager" (note the Star Trek reference). And my brother's machine? "Maggotbox". :-) One of these days I'll change the names on the machines. I also learned a few lessons. One being "Change the server admin password often", the other "Keep the Linux Quick Reference card out of reach of anklebiters and lusers"... Later. -- Phil. philpem(a)dsl.pipex.com http://www.philpem.dsl.pipex.com/

Doc Shipley wrote: My explanation, subject to correction, would be cockney rhyming slang : half-inched = pinched = stolen What I have never seen an explanation of is whether there is any rational behind the rhymes used. -- hbp

Doc Shipley wrote: I think that was the whole point originally, secret communication. A quick google threw up this from http://www.aldertons.com "The origins of Cockney Rhyming Slang are uncertain. It's not really a language since the words spoken are clearly English; on the other hand, it's not a dialect either, since the speakers of this slang are also perfectly capable of not using it! Some stories go that this slang originated in the market place so that the vendor's could communicate without the customers knowing what was being said - you wouldn't want your customers knowing that you were going to lower your prices in ten minutes so you could go home early. Other stories have it that it originated in the prisons so that inmates could talk without the guards listening in. I recently heard from Bob King that "it was born shortly after Sir Robert Peel introduced and implemented his idea for a Police force. The criminal fraternity had never been faced with such a concerted effort to thwart them, so they developed Cockney Slang, the idea of which being that, two or more criminals could hold open conversation, within earshot of a "Peeler," without fear that their plans were being overheard by the police." And Jackie says that many of the rhymes were invented by the petty thieves to rob people in the markets, allowing the thieves to talk amongst themselves without anyone knowing what they were talking about" -- hbp

On Wed, 23 Oct 2002, Huw Davies wrote: It Just F*cking Works 01? -brian.

In message &lt;4.3.2.7.2.20021023181231.0262a6b8(a)kerberos.davies.net.au&gt;au>, Huw Davi es writes: Ok, it's a long shot, but how about the first firewall between the Internet and a Janet network? Brian L. Stuart

All this talk of naming systems has made me realize just how boring the names of my machines at home are. So, I think I shall rename all mine after famous ships that have sunk: Thresher Scorpion Titanic Sultana Andrea Doria Kiangya Lady Of The Lake Estonia Kind of fitting, and hopefully not a portent, for someone who lives on a houseboat, eh? --John

My apologies, that should be "mk48_adcap". g. On Wed, 23 Oct 2002, Gene Buckle wrote:

Various naming schemes I've used in the past: * cheeses * beers * cartoon characters * candies * serial killers * famous and infamous duos (for paired servers) * automobiles * islands * dead Soviet leaders -brian.

In the early 1990s, I got a tour of one of the networking labs at Bell Labs. I noticed that all the servers were labeled with names--all characters from The Little Mermaid. --Mike Michael Nadeau Editor/Publisher Classic Tech, the Vintage Computing Resource www.classictechpub.com ----- Original Message ----- From: "Jay West" &lt;jwest(a)classiccmp.org&gt; To: &lt;cctalk(a)classiccmp.org&gt; Sent: Monday, October 21, 2002 10:49 AM Subject: Re: A Momentous Decision heh

I name all my servers after Scandinavian cities. Right now, I have stockholm (ANS 500/200), thule (Mac IIci running NetBSD) and reykjavik (Solbourne S4100/36), with oslo in the wings (POWERServer; exact model to be determined when I take possession). The unfortunate consequence of this is that people think I live in Sweden, and tell me they won't ship stuff to Europe (stockholm.ptloma.edu), ignoring the .ptloma, and the .edu. -- ----------------------------- personal page: http://www.armory.com/~spectre/ -- Cameron Kaiser, Point Loma Nazarene University * ckaiser(a)stockholm.ptloma.edu -- "I'd love to go out with you, but I'm rethreading my toothbrush bristles." -

On Tue, 22 Oct 2002, David A. Woyciesjes wrote: Ok, the whole Jared thing is bad enough. But now this? :) Sellam Ismail Vintage Computer Festival ------------------------------------------------------------------------------ International Man of Intrigue and Danger http://www.vintage.org * Old computing resources for business and academia at www.VintageTech.com *

A non-text attachment was scrubbed... Name: not available Type: text Size: 693 bytes Desc: not available Url : http://www.classiccmp.org/pipermail/cctalk/attachments/20021020/e9f7bf10/at…