Slashdot Mirror
Linux 3.3 Released
diegocg writes "Linux 3.3 has been released. The changes include the merge of kernel code from the Android project. There is also support for a new architecture (TI C6X), much improved balancing and the ability to restripe between different RAID profiles in Btrfs, and several network improvements: a virtual switch implementation (Open vSwitch) designed for virtualization scenarios, a faster and more scalable alternative to the 'bonding' driver, a configurable limit to the transmission queue of the network devices to fight bufferbloat, a network priority control group and per-cgroup TCP buffer limits. There are also many small features and new drivers and fixes. Here's the full changelog."
The Linux kernel guys show that constant steady frequent releases are the way forwards, note to GNOME and KDE guys, you got it wrong.
Wow, I had no idea there was work in porting Linux to DSP architectures. That's quite an interesting development. I wonder what the use case is, since DSPs are typically used for very specific, real-time work, not for hosting general-purpose operating systems.
Also, it's quite surprising to me since as far as I know it's necessary to use TI's compiler to generate C6X code. I found one initiative to port GCC to it, but afaik it didn't get finished. My understanding is that it is no small job to get Linux to compile on non-supported compilers, so I'm interested in the toolchain they are using. For my own work on a C6711, I've been using the TI compiler under Wine. (Which works fine actually, although I had to generate an initial project in CodeComposer to get some of the board-specific support files.)
Fanboism? Don't be a douchebag. This is a post about a new Linux release. The people who comment on this post should naturally be expected to be Linux users, probably fans. Just as a post about a new OS X release would naturally be populated with Apple fans. It's the people who purposefully comment on threads about products they DON'T like that create a problem. Then there are people like you who just enjoy acting like a dick. Give it a rest.
You're just jealous that it'll take at least a month after Windows 8 comes out before somebody creates a Metro-style UI for X.
Two to match the colors.
Really?
Well, explain this to me:
When you have 8 servers each with 2 PCI-E Quad E1 Digium Cards, handling a total of 248 inbound calls on toll free numbers, with an average of 200 simultaneous channels per server 24/7, how do you cluster that? When you have analog CCTV cameras running into 4 servers each with 16 channels of video, well, how do you cluster that?
Not everything is HTTP over TCP/IP. Not everything is easily solved with a load-balancing reverse proxy or DNS balancing/failover. Not everything can be clustered. In those situations, and I speak from experience (those two are real-life situations I deal with), not rebooting is real fucking important. And you have two options: either you leave systems unpatched and wait for the next 5 minutes downtime window that might be a year from now, hoping nothing bad happens, or you live patch those motherfuckers.
If that wasn't enough, I can mention at least an extra 20 cases where clustering isn't an option, and neither is rebooting.
The explanation is fairly simple. Your hardware does not meet the redundancy and failover requirements for the uptime expectations you've set. Equipment designed for extensive uptimes and critical services have built-in redundancy. Take your phone "server" for example. We run several types of phone service, and the one most similar to what you describe runs as a pair of servers, each with a primary and redundant connection. If either server fails, or if the connected switches/routers fail, they can failover to the backup hardware without even interrupting a call in progress. When we need to upgrade the servers, we do them one at a time.
Rebooting always has to be an option. Always. Why? Because sooner or later you're going to have hardware failure, and you'll be rebooting whether or not you want to. Going with your 'head in the sand' approach only means your customers will feel a much greater impact from the inevitable downtime than they would if you'd properly designed your systems in the first place.
So... which part of this release actually provides a compelling reason to use Linux over any other OS?
You've been itching for something to run on that TI C6X system you built?
The fanboisim here makes me gag. Apple has nothing on you guys.
Hey Cowboy did you know that the Linux Kernel currently runs most smart tvs, bd players, and other home entertainment devices. I would be willing to bet that the number of Samsung, Sony, LG and other tvs and devices running on the Linux kernel is much greater than the number of Macs, and PC currently in use combined!
The reason for this is that any manufacturer can use OpenSource software like the Linux kernel and modify it to their own needs without sending money to Redmond for every device they sell. This is why Microsoft and Apple have failed in the embedded market with perhaps the exception of some car companies like Ford Motors. Ballmer can rant, rave and do all the paid shill crap he wants. Fact is as the kernel becomes more open to modification from companies like Google with Android optimisations and slick coding Microsoft will become irrelevant in many markets.
The post was about the most important core software released in history so go pound on your PC, and post how linux sucks somewhere where someone cares. The Linux kernel is one hell of allot more that just the base of an OS as you perceive it.
the android merge means i can play angry birds without having to use wine...
Note that playing sober raises it to another level of difficulty.
Every end has half a stick.