Slashdot Mirror
Linux Kernel 4.5 Officially Released
prisoninmate writes: Yes, you're reading it right, after being in development for the past two months, Linux kernel 4.5 is finally here in its final production version. It is internally dubbed "Blurry Fish Butt" and received a total of seven RC builds since January 25, 2016. Prominent features of Linux kernel 4.5 include the implementation of initial support for the AMD PowerPlay power management technology, bringing high performance to the AMDGPU open-source driver for Radeon GPUs, scalability improvements in the free space handling of the Btrfs file system, and better epoll multithreaded scalability. The sources are now available for download from kernel.org.
Update: 03/14 13:24 GMT by T : Reader diegocg lists some other notable features (a new copy_file_range() system call that allows to make copies of files without transferring data through userspace; support GCC's Undefined Behavior Sanitizer (-fsanitize=undefined); Forwarded Error Correction support in the device-mapper's verity target; support for the MADV_FREE flag in madvise(); the new cgroup unified hierarchy is considered stable; scalability improvements for SO_REUSEPORT UDP sockets; scalability improvements for epoll, and better memory accounting of sockets in the memory controller), and links to an explanation of the changes at Kernel Newbies.
Linux does not come with stable driver interface, so drivers supplied by vendors would rot quickly. It's more practical to just bundle everything with the kernel, update the driver interfaces there, and recompile. However this has the additional benefit that one does not have to hunt drivers around Internet, so if you have the most recent kernel, you also have all the most recent drivers.
no mention of living submerged was in the pamphlet? synthetic oxygen sucks? free the innocent stem cells,,, cease fire..
General issues are everybody's problem. Issues with one particular piece of hardware is:
a) Not really the problem of anybody else
b) Not something most people can reproduce
c) Not anybody's job
If Dell delivers laptops with Linux preinstalled, then it's their problem, they got the hardware to reproduce it and they got paid people working on it. If $random_user installs $random_distro on $random_laptop, well the manufacturer doesn't care. And while there's always a few people working to make Linux run on everything, they're few and they can't go around buying laptops just because and there's new models all the time. Red Hat will work on supporting the servers that RHEL runs on, they won't generally work on random hardware. And the kernel is mostly driven by paid development, other hardware is very much in the "you want support for that? great, submit a patch and we'll review it" mode.
Some might say that it's because OEMs do not "support ACPI spec properly", but in practice most PCs don't... It could be more practical to just find the patterns that Windows uses, and imitate them.
Says no person who has tried imitating an undocumented binary blob ever. Basically manufacturers just bang the code until it stops crashing, unless you can replicate it exactly which is hopeless in practice you're going to run into random issues. And random issues here aren't just glitches, they're usually crash/hang bugs. I'm sure a lot could be done if you brought the right people together with the right hardware and gave them some money to work on that. But I don't really see who'd do that, because it's not just free time and there's no profit in it.
Live today, because you never know what tomorrow brings
It is internally dubbed "Blurry Fish Butt"
Rumor has it that the next kernel will be named "Lennart's buttery balloon knot".
Oh dear, I definitely feel old age sneaking up on me; I just don't find these names funny any more. If ever I did. I'm all for having a sense of humour, but it would be refreshing if it wasn't always stuck up our own backsides. Can't we raise the level a bit? (Groan, I shouldn't have said that - now it's going to be about tits instead, isn't it?)
People fight about SystemD, various open source licenses, differences between DEs, filesystems, but at the same time there's these fundamental problems which should get way more attention. Sometimes it feels like we are in a house arguing what kind of wallpapers bring the best experience, while that same wall is infested with mold inside.
You're setting up a false dichotomy, there: the fact that some people are designing filesystems or DEs or Systemd or such isn't necessarily away from progress on the ACPI-stuff and the likes. Not everyone knows enough about ACPI, for example, to be able to contribute anything useful, so them working on something else doesn't hinder the progress on the ACPI-stuff in the least.
Also, not everyone agrees with your priorities, like e.g. a lot of people deem work on filesystems more important than getting ACPI totally right -- not everyone needs working suspend, not everyone is running Linux on a broken laptop, but filesystems? Improvements in them are likely to have a much wider area of effect.
If your hardware has problems, what are you contibuting to fix the problem? whining? *tumbleweeds*
Ahh .. victim blaming at its finest.
I am Slashdot. Are you Slashdot as well?
I don't think Lennart's got tits. But, he does have nipples. Lennart's Nubian Third Nipple...
Hmm... Nope, still not funny. Maybe they'll aim higher?
"So long and thanks for all the fish."
e.g. a lot of people deem work on filesystems more important than getting ACPI totally right
And this is why Linux on desktop will never come. We spend a disproportionate amount of time fine-tuning the already spectacular, while the mindbogglingly stupid usability issues stay in the too hard basket.
no doubt you've been testing the next LTS version in the mean time, you can move to that
"The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)