The distribution of source code (encryption in particular) is explicitly protected under the First Amendment:

http://en.wikipedia.org/wiki/Bernstein_v._United_States

Stop being stubborn - why not KVM in, prove it's their fault, and then make them reimburse you for it?

Sounds like you're either incapable or unwilling to fix the problem yourself, but at the same time you refuse to let them do it? What exactly would make you happy here? And don't say "moving me back to the old hardware and datacenter that I was paying for!" Be realistic.

You said yourself that it's new hardware. It's completely reasonable for them to suggest you've got a bad NIC driver in there for whatever card you were moved to.

This is almost certainly a problem on the system itself. I've seen a handful of cases where hardware load balancers in DSR mode can lead to connection pileups under certain conditions, but 99% of the time it's a problem on the server itself. In any event, tuning should be able to prevent that from knocking the box over completely, allowing you to stay logged in and see what's going on.

Also, by claiming that nothing has changed on the system, you're either lying, or you're a horrible sysadmin who doesn't apply updates. Another potential scenario I see here (obviously aside from new hardware using previously unused drivers...) is that you or your package management system installed a new kernel or NIC driver, but never rebooted. Then when the server was powered off and migrated to the new facility, it came back up with the new (and potentially problematic) driver/kernel.

Switch providers. Plenty offer remote reboot and serial console or KVM for both VMs or physical servers, which would allow you to go crazy with custom encrypted partitions etc. At the end of the day though, someone somewhere at the hosting company is still going to be able to reboot your server into a rescue environment and reset the root password. Go colocation if you're really that paranoid about it.

You also have zero chance with litigation, unless you've somehow gotten them to sign something saying they specifically won't muck around in your server.

I'd also like to know how you *know* it's a hardware or network issue outside of your server. How do you know it's not your NIC driver hanging up? Older e1000 drivers (super common card in the hosting industry) are quite flaky. What research have you done outside of your internal monitoring?

Out of curiosity, where did you go to school that you ended up calling college "University"?

Looks like you're correct. Perhaps Buster from Arrested Development was hired as their cartographer.

Zoom in a bit and it starts to look not so good.

Yes, because Linux has put Microsoft out of business.

Please let me know if it syncs with your Windows 95 PC as well. It's the one thing that's kept me from buying one on launch day.

No, you're not being dumb. There's a known bug in network-manager that prevents it from remembering a static IP after reboot.

http://www.ubuntugeek.com/how-to-set-a-static-ip-address-in-ubuntu-810-intrepid-ibex.html

I'm not sure if it still exists in 9.04.

That actually sounds more like a power issue. The 8x AGP cards were notoriously sensitive to fluctuations in one of the rails (I want to say 5v, but it's been forever...) Newer PCIe cards are better, but if you're running cool and your computer reboots for no reason (particularly during games) I'd put money on a poor quality or faulty PSU.

Yes but then you have to live in New Hampshire...

The best of the best posts (the ones where someone drops a paragraph of science that just ends the argument, or blows you away) are still here at Slashdot, but the signal to noise ratio has been fading fast lately.

Overall I find Reddit's comments are better and certainly more entertaining than Slashdot these days. The first 20 posts top level posts here are always a mixture of Off Topic, Troll, or +5 Funnies that aren't actually funny.

Have you submitted any content that's been accepted?

It's a consequence of not writing software properly. Relevant links later in the same comment thread for those who don't might otherwise miss them:

https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/317781/comments/45

https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/317781/comments/54