Linked by Nth_Man on Mon 1st Jul 2013 15:37 UTC
Linux "This release adds support for bcache, which allows to use SSD devices to cache data from other block devices; a Btrfs format improvement that makes the tree dedicated to store extent information 30-35% smaller; support for XFS metadata checksums and self-describing metadata, timer free multitasking for applications running alone in a CPU, SysV IPC and rwlock scalability improvements, the TCP Tail loss probe algorithm that reduces tail latency of short transactions, KVM virtualization support in the MIPS architecture, many new drivers and small improvements."
Permalink for comment 566228
To read all comments associated with this story, please click here.
Member since:

"That's a fib.

No it isn't. You are being a dick. If you have a el cheapo graphics card is over 6 years old you are going to have problems. I have it on my intel based Dell, so I have to run Mate instead of the newer DEs.
" [/q]

It is a fib without a doubt. I have two el cheapo graphics card is over 6 years old and I run a feature-full compositing desktop (KDE 4.10.4, the very latest version) without the slightest problem. Fast, slick, responsive, powerful, stable, and elegant. What is wrong with you? Why would you deny this?

Look I know how it works. I had to do it quite a few times back at the start of the last decade.

But lets be realistic the package manager on most distros do all the hard-work for you. Wayland isn't around yet and tbh I've seen the X server crash a handful of times over the years.

It does the hard work of installing a binary blob driver for you when it works. When it doesn't work you are in a world of pain.

You ignore another major problem:
"User-space mode setting would have needed superuser privileges for direct hardware access, so kernel-based mode setting increases security because the user-space graphics server does not need superuser privileges."

Also with regard to X-server crashes, the wikipedia article on modesetting refers to the page on "screens of death".
"A kernel panic is used primarily by Unix and Unix-like operating systems: the Unix equivalent of Microsoft's Blue Screen of Death. It is used to describe a fatal error from which the operating system cannot recover."

Without a doubt the biggest cause of kernel panics these days are binary blob drivers.

You know if you were using like a decent operating system like Windows 7 that has a stable ABi/API and could recover the driver properly when it crashes .. it wouldn't matter whether the driver was open source or not.

You know that with a decent operating system like Linux, if you use an open source driver instead of a binary blob driver, you can recover the driver properly when it crashes. All that is required is that the driver is part of the kernel, it doesn't matter whether the OS was Windows or not.

So I repeat myself for the sake of those a bit slow on the uptake: one really doesn't want to run a binary blob driver with Linux unless one really has to. Binary drivers are really, really worth avoiding.

Edited 2013-07-04 13:20 UTC

Reply Parent Score: 2