In sortof agreement with what you said: this seems to be a simple case of jury nullficiation, but in the opposite direction /. seems to desire. People here like to advocate it as a way of getting someone who was arrested under an unjust law out of trouble. But the truth is, far more often it is used in a matter that results in convicting those who exhibit scummy behavior, regardless of the evidence.

More, a drunk passenger is safer than a sober driver. Pity the intercity buses in the US disallow consumption of alcohol...

This is a very good point, replying to hopefully make it more visible.

If he wanted a hip, trendy city Seattle would have worked nicely, while not as cheap as Portland it's still a better bang for the real estate $ than SF... hell, any city would be better, even NYC (outside Manhattan)...

The cost is because it is "on an airplane" meaning it needs to be certified by FAA and other alphabet soup agencies around the world. And forget about firmware updates...

You can use downforeveryoneorjustme.com, though it will use its own DNS and routing so it will still require you to figure out which of those is the problem.

The side effect of the rule is perpetuating no longer correct information. For example: a wikipedia entry states that a building is slated to be demolished, but the demolition hasn't begun, since that is what the last cited source has. However, looking out my window, I can see they have finally started demolishing it. Even if I provide a picture of the demolition, I cannot update the article and be within the rules, until the local paper is bored enough to run a story about it (which may never happen).

They once added an extra 19% discount to my bill. Remarkably, after about four bills, they fixed the error without me having to call them.

Ah well, it was nice while it lasted... and at least they never asked for the money back. That "billing errors in your favor" are honored was enough to keep me as a customer...

Since they are essentially a "New York Company" they tended to get a lot of state contracts. Because of this, it would be a big mistake for IBM to lay off too many employees within the state. Right now there are IBM consultants working in many state agencies, babysitting mainframes. Consultants are pretty much free money for IBM; if there were suddenly a huge pool of IBM trained individuals entering the local job market, it'd be easy to replace the expensive consultants with cheaper ex-IBM employees (via cheaper consulting firms, or direct hire) of comparable skill.

Bonuses are *not* taxed as capital gains; bonuses get handled the same way as overtime or other "supplemental wages". Here is one source.

No, the solution is to invalidate all the exclusivity agreements and allow anyone with a sound business plan to get a permit to run their own fiber/coax/copper/whatever (including municipal governments). The reason the market isn't sorting itself out is *because* of regulation.

The flaw in password lockout schemes that lack a timeout is that anyone can lock out anyone's account. I can imagine someone hammering every member of "Domain Admins", "Helpdesk Staff", etc with three fake attempts, and by the time anyone has realized it, it will be difficult to even find someone who can unlock the accounts.

It's possible to take this too far though. Some work accounts I have require a 30 day minimum before you are allowed to change the password, to prevent people from rotating through them at password change time. So, if you suspect your password is compromised (either by accidentally typing it in the username field or a focus-stealing chat window, or noticing a security camera pointed right at your keyboard at a coffee shop somewhere), not only are you not able to change it, but whoever has it knows you can't change it for at least a little while...

True, but that only works in environments where the bootloader is not configured to require a password to edit the kernel parameters...

While it is a strange thing to say, what is incorrect about it? If:
1. you've lost the root password
2. sudo is not configured (disappointingly common)
3. single user mode is configured to require entering the root password

The fastest way to regain root access is to blank it in /etc/shadow. A boot disk is one way to accomplish this. Others would be mounting the root partition on another server (in virtual environments) or using the backup software to restore a shadow file with a blank or known root password.