What does the owner's husband being deceased have to do with anything?

This ^ . I was replying to the low-powered servers article, not anything about some technologist named Kevin. I was referring to the fact that the article synopsis misspelled the word "at", instead saying "st", hence the intentional typo in my post.

... is something that's not found st Slashdot.

Jesse Jackson say?

This is what my company's official internal wiki "Server Naming Guide" (all server name examples are real, or once real, servers; wiki links removed for posting to Slashdot) says on the topic: (I think it's pretty funny...)

System Name

• Overall names for systems should be chosen based on two criteria: choosing a bite-sized name (when visualized in terms of bites of alphabet soup) or, if the bite is too large, selecting an acronym that may or may not mean anything or communicate the purpose of the server.
  • A high-quality example of the acronym selection process can be found in otgsrvr; as the systems installed on this server have not worn the “OTG” name since purchase by EMC in 2001 (for those counting, the server was purchased in May 2007). For interpretation of this name, acronyms.thefreedictionary.com provides this handy reference:
    • OTG-On-The-Go (USB 2.0 specification)
    • OTG-Over the Glasses (goggle type)
    • OTG-On the Ground (sales)
    • OTG-Off the Ground (gaming)
    • OTG-Operations and Technology Group (Microsoft)
    • OTG-OpenTheGovernment.org
    • OTG-Oficina de Treball de la Generalitat (Catalonia)
    • OTG-Off the Grid
    • OTG-On The Green
    • OTG-Old Timers Guild
    • OTG-On The Grid
    • OTG-Originating Trunk Group
    • OTG-Officer Training Group
    • OTG-operational target graphic (US DoD)
    • OTG-Operational Tactics Guide
    • OTG-Operations Tactics Group
    • OTG-OTH (Over-the-Horizon) Targeting Gold (message format)
    • OTG-Older Than God
    • OTG-Oven Toast(er) Grill
    • OTG-Optimal Treatment Guidelines
    • OTG-Original Tool Gangster
  • Going forward, otgsrvr is to be considered in terms of toaster ovens.
• One good option for acronym selection is to select some letters that seem like a good server name, then think of something to ostensibly link the device’s purpose to those letters (ie bum)

Production

• If there is no test server, a system is in production unless marked otherwise (ie cognos)
• If there is a test server, a production system must be marked as productional (ie health-prod-app), except when it isn’t (ie crystalsrvr)
• If there is no test server, but you want to make extra sure that a server is in production, it can be marked as productional (ie gis-prod-web)
• Generally, the ‘prod’ label should be used liberally; you never know when someone will see a device named something like ‘vcsrvr’ and say, “hey it doesn’t say prod, so it should be a good place to put databases for unrelated systems!”
  • You can bet that wouldn’t happen to ‘prod-vcprodsrvr-prod-reallyprod’

Test

• Test systems should either be marked as test, not marked as test, or marked as test in a cryptic and nonstandard way. This can be determined through the roll of a standard 6-sided die;
  • 1-3: Add ‘test’ to the server name, replacing ‘srvr’ where present. Whether to add a hyphen or not before the word is discussed in Appendix B. (ie health-test-db, otgtest)
  • 4: Don’t mark the server whatsoever. (ie oraclesrvr)
  • 5-6: Select a marking style at random! (ie t-websrvr01, test-db05)

Development

• In all cases, a dev server should be marked as either production or test. The fact that it is a development server should remain a closely guarded secret.

System Function Suffixes

• A system’s purpose should be appended to the end of the system’s name, but only in the following circumstances:
  • There are multiple systems that would otherwise have the same name, and we don’t feel like using numbers (ie icris-img)
  • Names that would otherwise fall within the netbios 15 character limit, and we would rather push them over the limit and tempt fate (ie psoft9-prod-web2)
  • When we can’t think of anything better (ie so-db)
• The suffix used should be decided based on one of two factors:
  • Whether the name is descriptive of the purpose (ie real-test-db)
  • -OR-
  • Whether the vendor has some nonsense name that deceives about the server’s true behavior (ie fidlar-sec)

Appendices Appendix A: Numbering

• Servers can be numbered according to several different methods:
  • Sequential numbering based purely on server age (ie intranet2)
  • Sequential numbering based on location (ievm-weld7)
  • Sequential numbering that goes back to fill in gaps left due to decommissioning of servers (ie printsrvr01)
  • Numbering based on the version of the software installed on the server (ie banner8-prod-db)
  • Sequential numbering based on the version number for the first server, then increasing that number for additional servers despite not increasing the software version number (ie websense8)
  • Adding arbitrary numbers to the end of the server name regardless of need (ie test-db05)
• Digit count selection
  • The number of digits used should be either too low for the number of servers that may end up in a system (ie vm-weld9) or far too high to ever possibly need (ie dmzroot01)
  • When there is an established name that is having devices added to it, feel free to change the number arbitrarily (ie websrvr01->websrvr3) or substitute a lowercase “O” for one of the digits. (ie dmzrooto1)
• The number 1 is implied in a system name (ie ciscoacs4srvr) or is not implied (ie imagesrvr01) depending on the flip of a coin.
  • Heads; 1 is implied
  • Tails; 1 needs to be specifically stated

Appendix B: Hyphenation

• Hyphens should be used to separate parts of server names, especially when doing so will push a name over the 15 character netbios limit (ie psoft9-prod-web2)
• Hyphens should not be used where it would appear to make the names appear systematic and standardized – the goal is an ordered mess (ie accelatest-app)

Appendix C: “srvr”

• When a server name is too small of a bite (yes, the alphabet soup metaphor again), ‘srvr’ can be used to beef up the system name. This is not a ‘suffix’ in the terms described above (ie bannersrvr-db)
• In all cases, it will be replaced by the word ‘test’ if that (the full word, mind you; ie t-websrvr03) is added to the server name, but by itself does NOT imply that the server is production!! (ie oraclesrvr)
• When the server name ends with “s”, the first letter of ‘srvr’ may be contracted into that “s” (ie wsusrvr), or not (ie iissrvr)

Looks like someone did a global-search-and-replace on "happen" with "happy."

Reference Jonathan's answer to question five:

And question ten:

All of those should be "happen" IMHO.

Thanks for missing the point entirely. :)

... who remembers the Danny Boyle movie Sunshine?

I fear that the fate of Project Icarus has been preordained, and it's not very good...

"Any sufficiently advanced technology is indistinguishable from magic."

Give it time. Eventually, we'll have evidence in front of us that quantum mechanics, dark matter, dark energy, etc. do indeed work as predicted by science-- because we'll have the products that rely on those phenomena in front of us. Does it matter that we can't prove that they are working such-and-such way? No, not really. If the dark matter propulsion system on your space ship is propelling you across space, either you admit that you have evidence of dark matter, or you believe in magic.

Sometimes.

I was telecommuting out-of-state with no benefits for almost 4 years when I got tired of the job and the pay and found one 65 miles away, in the closest metro area to where I live for my wife's (higher-paying) engineering job. The new job actually paid almost exactly 10% (plus benefits) more than the old one, as I suspected it would, as I was pretty underpaid at my old remote job.

Even commuting 65 miles each way every day, assuming fuel prices between $3.00-3.50/gal (which it is in my area, luckily), fuel costs only soak up about 40% of the gain, giving me a net gain of about (60% * 10% = ) 6%, plus benefits. Wear and tear on my car is pretty minimal, monetarily, as I drive a 22-year-old reliable sedan, on which I perform all regular maintenance and break-fix work myself, meaning that it's pretty cheap overall. Parking at work is free, and my commute is a straight shot on two-/four-lane highways, regularly averaging 80 mph with no real traffic to speak of. I listen to books on tape while I drive, and it makes it pretty stress-free.

In addition, I actually *love* my new job, and although I am authorized to telecommute one day a week, I usually do it more like one day a month, when I have commitments (doctor/dentist appointments, etc.) near home.

Overall, I think I've come out ahead trading a 10% raise for a real commute, and I wouldn't take a 10% pay cut to telecommute full-time. I don't think I'd even take a 5% cut. I wouldn't take a 10% pay *raise* (putting my right where I am now) to go back to my old job, as I felt under-valued as a team member, and didn't have any potential for upward mobility. Here, I have awesome benefits, a decent commute (which may be shortened significantly in the next year or two, if an expected transfer and relocation with my wife's job comes through), and I feel like a part of a dynamic team with significant potential for upward mobility and regular over-COLA raises.

But I recognize that I am probably a pretty unique case...

Real geek news.

Is there going to be any real news posted today? Or just all "jokes"? Kinda ruins /. for those who actually enjoy reading real news...

Okay, sorry. Let me rephrase:

I'll let someone else address #1, #2, and #3, but #4 doesn't meet the "must be able to identify each student's vote" requirement. Better? :)

#1, #2, and #3 seem to answer the request nicely, but #4 doesn't meet the "must be able to identify each student's vote" requirement.