I don't think it was the loudness of the ride that killed the Concorde...but rather the cost of the tickets (and the rising cost of fuel).

Hahahahaha! Not that I really think there's any use in prolonging the inevitable with Itanium, but I just love hearing about Oracle getting fucked.

Realistically though, I have a feeling that a Thunderbolt NIC dongle costs quite a bit more than it would cost to put the NIC on the motherboard.

It's actually even better than that. The official recommendation is a /48 per end-site. As far as I have been able to tell, I think ISP's are generally following that. I had heard something about using /56 per end site for residential users. That still gives people plenty of room to have multiple subnets though.

I definitely agree with the concerns about IPv6 in the enterprise. Sure, almost everything has had some IPv6 support for years, but the feature parity with IPv4 was not there. (For example maybe something supports OSPF / BGP with IPv4 but only static routes with IPv6...or you can reference address groups from within a IPv4 ACL but not from IPv6). Even today some vendors (*cough* Juniper on their EX switches *cough*) see IPv6 routing as "extra" feature that isn't available on the basic license level. This is unacceptable, and shows a complete disconnect between vendors and enterprises / service providers with respect to what's actually needed for real world IPv6 deployments.

When the $40 point and shoot camera satisfies the needs of 98% of the market...then it's a bit different story.

It would be interesting as well to know how much of an impact this would have to people on the Martian surface. Mars's magnetic field is pretty weak compared to ours. I guess they would be a little better protected just by the planet surface itself.

Even on the Apollo missions to the moon, they recognized that a solar storm could be a significant threat to the astronauts. Given the infrequence they decided to just take their chances. But the time they spent outside of the LEO was pretty low compared to what a Mars mission would entail.

My point is that RH isn't going to make that kind of change in an existing version of RHEL.

Now upgrading from 5 -> 6, or 6 -> 7 whenever that's released. Yeah...stuff's going to change. Maybe they'll put this in RHEL 7. But I don't this significant of a change would be pushed down as a normal update within v5 / v6 even in a 6.x or 5.x update.

Have you ever used RHEL / CentOS? I hightly doubt they will push out a completely different logging system as a normal update in an existing version.

I for one would much rather control which network can access a service in one place (a centralized firewall), rather than manage it through ten different config files that use different syntaxes on a bunch of servers for every service.

Yep...I do this with Unison so writes on both sides can be replicated. Granted - I'm not replicating significant amounts of data, I've heard Unison may have problems with large volumes of data. But I think the Internet connection would be more of an issue than that.

Yes, ISP's need to be responsible and take action against spammers, and yes, ISP's who continually fail to do so on a significant scale over a long period of time are fair game to block, but in this particularly instance it sounds like Spamhaus's actions may have been abusive and rather arrogant. I use Spamhaus's blocklist myself, but organizations like Spamhaus and Cisco SenderBase need to take some responsibility to ensure that they are not unduly effecting legitimate businesses and networks. Taking large-scale blanket actions that effect many legitimate sites undermines the anti-spam industry as a whole, because it makes it more difficult for people to rely on anti-spam products/services.