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."
Thread beginning with comment 566228
To view parent comment, click here.
To read all comments associated with this story, please click here.
lemur2
Member since:
2007-02-17

"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:
http://en.wikipedia.org/wiki/Kernel_mode-setting
"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".

http://en.wikipedia.org/wiki/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

lucas_maximus Member since:
2009-08-18

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?


Because it isn't true for the majority of graphics cards which are intel based, me and you were lucky enough to get some decent in the machine.

Guess what on the same graphics card that KDE works really badly on(intel on my laptop circa 2006) , I can run a full Windows 7 desktop with buggar all problems.

Gnome 3 and KDE 4 run like arse and I am force to use MATE which is a Gnome 2 fork.

So stop trying to change the circumstances to fit your argument.

Your machine isn't the whole world you know.

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:
http://en.wikipedia.org/wiki/Kernel_mode-setting
"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".

http://en.wikipedia.org/wiki/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.


Wouldn't be a problem if the kernel had a proper stable ABI/API for drivers and then all a driver creator would need to do is respect the interface provided.

Also believe it or not, I don't care if my desktop system is really stable or not or my crappy laptop that I use for work when I am on the road.

If my machine crashes twice a week I really don't give a shit because it takes less than 30 seconds to boot.

If it was crashing every hour I might give a shit. Even if it was that much of a problem I would just run Linux in a VM and again I wouldn't give a shit.

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.


Windows doesn't need the driver to be part of the kernel because it designed properly with a well defined and documented interface.

Sorry Windows can recover properly without the driver requirement being open source, don't try to spin it to your beliefs.

If they bothered having a stable API/ABI like proper software engineers provide, it wouldn't matter if the driver was open source or not.

You will try to deny this fact because you are a zealot. But this is the truth of the matter whatever you say because it is 100% verifiable.

It has even been mention in one of the news articles on site how much better Windows 7 graphics stack is.

http://www.osnews.com/story/21999/Editorial_X_Could_Learn_a_Lot_fro...

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.


It only needs avoiding because of the stupid decision made by Greg H.

Look you can claim that I am slow and not understanding it, but every single decent software engineer knows that providing a stable and well documented interface is a good thing. Just because you don't get it and have bought into Greg H's bullshit doesn't mean you are right.

Reply Parent Score: 2

Serafean Member since:
2013-01-08

In windows the drivers are as much as part of the kernel as they are in linux (with lernel modules). The only difference is that Windows provides a stable kernel API/ABI, whereas linux only provides a stable userspace API/ABI (look at the ntfs-3g driver implemented in userspace). You can bitch all you want, that's how it is. Both approaches have their merits.

Just a reminder : the XP -> Vista transition broke that API, and drivers had to be rewritten...

I agree that binary blobs are to be avoided, 90% of all issues I encountered I traced to blobs.

Now to the radeon driver : it provides everything BFUs need right now. It works out of the box. What else do you want? Extreme performance? The devs were catching up on supporting 5 hardware generation up to today, I'd say what we have now is pretty good. A lot of the performance might be in powermanagement, and some in the shader compiler that is still WIP.

Bottom line is : I use it, and I'm happy with it.

Serafean

Reply Parent Score: 1