Category Archives: Announcements
DNS Automation
Date published: March 4th, 2009
Posted in Announcements | 1 Comment »
Previously, Reverse DNS requests for our customers were checked over and entered manually by our support staff. In the last few days we’ve made some improvements to RootCP, including automation of DNS requests. Now, when you request a Reverse DNS update in RootCP, it will be updated to our DNS servers instantly. You’ll still need to wait 1-2 hours for the change to propagate.
BSD on Twitter
Date published: February 8th, 2009
Posted in Announcements | No Comments »
We joined the crowd and got on twitter. You can follow us, if thats your thing.
FreeBSD 7.1-RELEASE
Date published: January 7th, 2009
Posted in Announcements, FreeBSD | 2 Comments »
In the last few days, the FreeBSD Release Engineering Team finalized 7.1-RELEASE and it is now available for download. We are now also offering the option for 7.1-RELEASE on new VPS setups. It is listed as an option in the signup process (along with 6.3 and 7.0).
- The ULE scheduler is now the default in GENERIC kernels for amd64 and i386 architectures. The ULE scheduler significantly improves performance on multicore systems for many workloads.
- Support for using DTrace inside the kernel has been imported from OpenSolaris. DTrace is a comprehensive dynamic tracing framework.
- A new and much-improved NFS Lock Manager (NLM) client.
- Boot loader changes allow, among other things, booting from USB devices and booting from GPT-labeled devices.
- The cpuset(2) system call and cpuset(1) command have been added, providing an API for thread to CPU binding and CPU resource grouping and assignment.
- KDE updated to 3.5.10, GNOME updated to 2.22.3.
- DVD-sized media for the amd64 and i386 architectures
Connectivity Outage
Date published: December 28th, 2008
Posted in Announcements | No Comments »
Today there was a major disruption in Internet traffic affecting our network and many other sites in the USA such as Amazon S3, Facebook and more. It looks like the primary cause of the problem was with the Level(3) Internet backbone.
As of 2:45PM EST it seems that things have stabilized. If you are still having problems, please open a support ticket.