Whoever, under color of any law, statute, ordinance, regulation, or custom, willfully subjects any person in any State, Territory, Commonwealth, Possession, or District to the deprivation of any rights, privileges, or immunities secured or protected by the Constitution or laws of the United States, or to different punishments, pains, or penalties, on account of such person being an alien, or by reason of his color, or race, than are prescribed for the punishment of citizens, shall be fined under this title or imprisoned not more than one year, or both; and if bodily injury results from the acts committed in violation of this section or if such acts include the use, attempted use, or threatened use of a dangerous weapon, explosives, or fire, shall be fined under this title or imprisoned not more than ten years, or both; and if death results from the acts committed in violation of this section or if such acts include kidnapping or an attempt to kidnap, aggravated sexual abuse, or an attempt to commit aggravated sexual abuse, or an attempt to kill, shall be fined under this title, or imprisoned for any term of years or for life, or both, or may be sentenced to death. http://www.law.cornell.edu/uscode/18/usc_sec_18_00000242----000-.html

As for the store loyalty cards, in my experience you can put whatever information you like into the application form. Nobody checks or confirms the information in it. I love being thanked as Mr. Smith whenever I shop at Safeway. His address is 1 Matrix Like City, Cyberspace, USA.

We allowed our developers to have local admin access. In exchange, their machines were located on a separate VLAN and all communication routed through an internal firewall. This allowed these uncontrolled machines to do what the developers wanted, but allowed us to easily shut them down in an outbreak. It also gave the developers easy access to logging their traffic and understanding exactly what would be required to have applications run in a restricted environment.

For production systems, the developers had separate admin accounts that would be granted the required access to a system with a logged change request, time limited.

It works reasonably well. Of course the developers could just plug into a non-restricted port, but of course, this is better managed through policy than technology.

Are you aware that getting the seasonal flu vaccine increased your chances of getting H1N1?

I agree that in your situation you should be taking every precaution, mind you. You've got a particularly at risk child at home, it's a good thing to get the vaccine for yourself and your wife. It doesn't have to be some scary pandemic, it's just what you should do given it's almost flu season.

Most of the people here, however, are knee-jerk idiots reacting to the latest thing the teevee told them to be scared of; and I've been saying so since the H1N1 hysteria first started back when there was still snow on the ground from the LAST flu season. If not for them, there wouldn't be a risk of supply shortage, in my view.

Apple wasn't the first to use a "wheel"... See: http://en.wikipedia.org/wiki/Rio_PMP300 (Dunno if it was the first, but it was def before Apple)

You should travel on the trains on the east coast. Every man in a suit I see going to work in NY in the morning is either reading a Kindle or busy working/reading on his laptop.
A kindle only makes sense for a terrestrial traveler (WiFi download of books/news) who also uses it regularly. On a plane you can't get WiFi, nor are you going to travel to work daily by flight. So it makes no sense to use a Kindle there.
Now this market might not be very large. But it is extremely rich (hedge funds, Wallstreeters or the average beautician in NY) and will last a while -- people have been commuting for work to NY for years and they won't start driving anytime soon.

So you would rather have it behave exactly like a real book?
As soon as you loan it to a friend, it will be wiped from your eBook reader?
Really?

PDF support? Check.
WiFi? Check
eInk? Check
SD reader? Check
Battery life? 10 days

I'm not seeing a downside yet.

syslogd on every modern unix is capable of routing to a specific log file for a specific app. If the basic syslogd isn't enough, your loghost can run syslog-ng or any of the other more powerful syslog daemons. You only have to replace the one on the server, the other clients should just be forwarding EVERYTHING to it.

Of course at this sort of level, you'd probably save yourself a metric assload of trouble if you implemented a proper network monitoring/management server.

Myself, having only 15 or so hosts to deal with, most of which aren't chattery just use ssh + a colorizer script I wrote for my purposes. I typically leave it running on a spare monitor all the time.

You complete misunderstand. This addition is something completely different from some hare-brained hacked-up "desktop" scheduler. Deadline scheduling a new kind of scheduling which the current scheduler implementation is being extended to support. It's the difference between a new image format and a new image viewer.

Do it all in Open Office and stick with that. You'll be just fine. No duplication needed.

The problem with mexican flu (that's the name btw.) is not that the disease in itself is particularly deadly. The problem is that it's a H1N1 virus.

H1N1 are the proteins found on the mantle of the virus. The problem is that no human can develop an immune response to either H1 or N1 (as that would be deadly). If a virus were to infect a cell, and the mexican flu would infect the same cell, there is some chance that the mantle of flu would be copied around the much more dangerous virus, which would beat any immunity or vaccine we currently have, would react differently to most treatments and be capable of spreading through open air (through coughing).

If such an event were to take place, that event has a good chance of making the 1917 flu pandemic look like a tiny issue. That disease literally blocked the world economy for over 2 months, making millions of victims.

The problem is not the flu in the H1N1 form. The problem is that pneumonia might "be infected" and transform into an H1N1 virus. The problem is, in essence, the evolution that it might cause in other viruses. Cases of gene transfer between viruses are well-studied, and the current consensus is that it's commonplace.

How many mainframes does Google run? How is their data throughput doing?

this

Your virus is broken. Here, I fixed it:

Revised step 1. Open your email and send this virus, uh important message, to everyone you know.

There, that should do it.

Frightens me to think how far this would propagate, if sent from the right source, to a suitable target (corporate system to all from the Administrator). I've certainly seem lots of users who would do it.