If you are looking for some job, any job, this attitude may make some sense. Say, because you are unemployed or because you are truly miserable in your current position. Even with a pretty crummy employment market at the moment, this is not most people.

If you are looking for a next position, say because you have a big life change coming, want career advancement, or just plain feel like it's time for a change, this doesn't make sense at all. Spewing uncountable copies of your resume to the four winds and hoping might land you a job. If so, my guess is at some company you have no connection to, no passion for, and likely no reason but the pay check to keep going. This is not a recipe for happiness OR success in the new job.

I frankly can't imagine being willing to leave my current position for another one unless it was more than sufficiently exciting to justify customizing a resume and cover letter. Heck, the last time I did that it was for an internal transfer. Probably the next time, too. Red Hat is an excellent fit for me. Of course, I also find the whole idea of finding jobs through any form of job add rather improbable. I've literally never been hired for a job that I had seen an add for before I had talked with the hiring manager. Do people really get jobs that way in statistically significant numbers?

Different indeed. With solid-state drives, wear leveling makes it reasonably likely that the sector got swapped, rather than merely impossible to be sure it didn't.

There is one other case where disk encryption on a server could be useful, though it is not widely applicable: if you have a need to be able to rapidly destroy data, say in the event of a physical security breach. Having data stored on encrypted storage devices can mean that to render the data on the drives unrecoverable only requires wiping the header region of the encrypted block device. That, in turn, means wiping at most a few KB instead of several GB, and thus the difference between many passes in mere seconds and hours for a single pass.

Having said that, this is probably primarily of significance to military, intelligence, and criminal organizations. Few others are likely to be faced with the need to destroy large volumes of data on very short notice.

(If you care about why, this is because most/all disk encryption systems use a randomly-generated master key to encrypt the data on the disk. A copy of that master key is then stored in a header, encrypted with the password or passwords known by the user. No plaintext copy of the master key exists, so to access the data you have to provide the user-known password and use it to decrypt the master key. Changing the password can then be done simply by re-encrypting the master password, rather than by re-encrypting the entire drive. If the encrypted copy of the master key is destroyed, then it doesn't matter how many people you torture to get the password, it's still useless for decrypting the data on the disk.)

Comcast6.net IPv6 Information Center

Does that count as moving in the right direction? I'm hardly going to claim these guys are perfect, but it looks like something.

Looks like PHP 5.3.1, plus some patches ;)

2.0 is still supported in several Linux distros, including Red Hat Enterprise Linux 4, which is still in support. If you truly need 2.0.x, Red Hat (and I assume other distro maintainers) can be expected to continue providing basic security fix updates to the 2.0 series as long as RHEL4 is still in support. I don't see much reason to expect an upstream project like Apache.org to do that.

[Yes, I work for Red Hat. But I only represent myself, not my employer nor my colleagues.]

If you're bringing a laptop, forget the transformer and just bring a plug adapter - they cost only a couple bucks, and they're small. Then charge everything else off the USB ports. Heck, I do this for my regular domestic travel, too, just without the plug adapter. Works for everything I need on my perpetual business trips except the iron and the coffee/tea equipment, and any decent hotel provides those.