Linode uses Xen and there's nothing wrong with that. In fact, what virtualization backend is in use is probably not of real concern to most people, and just as many prefer Xen as KVM (I think that Xen is arguably better for VPS-style hosting).

Exactly what driver have you found that will run on RHEL but not on the same version of CentOS? CentOS is fully package and binary compatible with RHEL and they take great pains to make it so so I would be very surprised if there is any RHEL package or driver that won't work with CentOS just as well, or vice-versa for that matter.

There is, it's called TLS (which is the same technology that modern SSL uses, so the same encryption used by https) and is implemented by STARTTLS. It establishes a secure connection between two email servers and sends the email off secure between them and it suffers from the following pitfalls:

1. It only encrypts the data stream between two email servers that support it, or between the email server and client.
2. The email is still decrypted and stored plaintext in the queue of any given email server, and is subject to reading by the admin of any server in the chain.
3. It relies on each email server in the chain supporting TLS (most do, but there are still old ones out there that do not and the ones that do will generally fall back to unencrypted email if need be to communicate with an older server).
4. While it is possible to purchase and verify certificates between two servers no one does because a lot of servers use self-signed or invalid certificates, so verifying them would simply cause a lot of email communications to fail, thus it is susceptible to a man in the middle attack.

The best way to secure your emails has been and still is to use PGP (and before someone says it, that includes GPG), which secures the email end-to-end and so it is not subject to any snooping or attack in between with the exception that the envelope sender, recipient, and email headers still have to be sent in plain text. Of course this requires that both the originator and recipient of the email both have PGP support installed on their email clients and it requires the maintenance of PGP keys be done by the end-user, so it is more complicated than the vast majority of email users are willing to commit to.

Postfix 2.8.x for the MTA (2.8 has the new postscreen feature which is great to help with SPAM control)
Dovecot for IMAP POP3 as well as for SASL AUTH
Roudcube or Squirrlmail (take your pick) for webmail
PostgreSQL or MySQL for database backend
Spamassassin to catch what SPAM is missed by postscreen.
ClamAV to scan for viruses
Amavisd-new to interface psotfix to spamassassin and clamav
PostfixAdmin for managing your domains and accounts from the web.

Use virtual domains with postfix "virtual" for the delivery agent, use maildir format for your mailboxes (mailbox path needs to end in "/"). Make sure and use the submission port (587) for your outbound emails, not the SMTP port (25) which should only be for inbound emails. Don't use SMTPS (which works over port 465) unless you have to support a really old email client that doesn't support STARTTLS (which works over the submission and smtp ports). Stitch all the pieces together and if done right you'll have a great email system like all the pros use.

If you need help come into #postfix on freenode IRC network.

Nah, he'll just have to walk out his front door and violate his house arrest.

Actually America puts its own screening points in foreign airports for flights bound for the US. I'm not fully certain if they had this for the flight with the underwear bomber, though.

Also, while this is the case, it's usually just an additional passport check.

Really? I would think it would be more like 512GB ... or more (especially considering the 16GB USB flash memory stick I have)

No, for everything to be totally screwed, the full key held at the two secure facilities in the US would have to be lost or destroyed plus the keys held by three of the "key-holders" would have to be lost or destroyed as well.

I was thinking something similar to the way RAID6 is implemented, where you have five blocks of data plus two parity blocks so that any two block devices can be missing and all the data can still be reconstructed. This could easily be adapted on a smaller scale to work with key-sharing.

math: FAIL

In the first case you've gone from 10 to 20 mpg which means that you've gone from using 10 gallons to 5 gallons per 100 miles, saving you 5 gallons. In the second case You've gone from 33 to 50 mpg, which means you've gone from using 3 gallons to 2 gallons per 100 miles saving you only 1 gallon. That said, as much as people will get this question wrong, the important thing to know is that the 50mpg car is the best for fuel efficiency overall and hardly anyone would get that wrong.

Yes, but they actually did get the jackpot, just not in the amount that they had thought they won, so the casino did the right thing, imo, considering they could have stuck by the legal wording on the machine and just returned the bet amount.

The malfunction is going to be something along the lines of a RAM error, where a hardware component failed and caused the issue. This is not something that would or could have been picked up in a certification because the component would have been working just fine then. All the certifier can do is say that the machine is working properly "now", it says nothing of how the machine will operate tomorrow or the next day, and these machines run 24/7/365 for years. The fact that they hold up as well as they do under those conditions shows that they are well engineered to begin with.

Those would actually qualify as install scripts, see GPL Violations Source Code Release FAQ, specifically this section:

Honest answer: No.