Goodbye Ubuntu
netsplit.com
netsplit.com
> "A lot of this kind of stuff differs wildly between the distributions, especially since no two distros share the same boot code. The simple fact was that the changes were sent upstream and rejected because they didn’t apply to Red Hat, and the RH way of doing things. Likewise they don’t apply to Debian since that uses sysvinit and (I believe) udev is still optional, etc"
For a project as large and as complicated as Ubuntu, I imagine custom patches like the author's get lost periodically between release cycles, especially if they no longer apply cleanly to the latest upstream version.
I guess I also find it hard to believe that the upstream maintainers (RH?) could not be worked with to get this eventually merged in. Difficult developers/teams do exist, but the difficulties in getting the patches accepted weren't really outlined in the post (so it's hard to know what happened).
I also wonder how many alternative distros are using the unmodified upstream version of the package in question, meaning that the author may run into the same issue on other Linux distros as well.
Here is a basic unit, with a hardware encryption co-processor: http://www.synology.com/products/product.php?product_name=DS...
I have arch linux running now and while arch is not known for it's stability, I have far fewer applications crashing nowadays.
http://www.hanselman.com/blog/HowToSetUpCrashPlanCloudBackup...
Also, if for some reason, you have a desire to contribute to Ubuntu, contribute to Debian instead. Your changes will probably end up in Ubuntu, and the Debian folks care about stuff like user privacy and free software.
The realistic choice for servers today is either Debian or CentOS. This is what you'll find in pretty much any large deployment and for good reasons.
Ubuntu may be a distant third candidate due to its recent popularity, however it was never really meant for servers. Many of their policies are problematic in a server-env and most of the perceived popularity stems from inexperienced people who, by default, use on their server what they know from their desktop.
And please don't recommend SuSE. That is really just cruel.
I was on board the Fedora train until recently, but I had to get off because it was changing from RHEL beta edition to... RHEL pre-alpha edition. I have a soft spot for SuSE, but I've never been a full-time sysadmin, so you have to take my recommendations with a grain of salt.
At the same time, Canonical (makers of Ubuntu) are not very interested in the server, at least compared to Red Hat and SuSE. So you get big regressions in server-related functionality like the one described in this article.
Things not to use on a server: Ubuntu, Fedora, Gentoo Things to use on a server: CentOS, RHEL, SuSE, possibly Debian, any of the BSDs.