Linux Kernel 4.4 LTS Officially Released 132
prisoninmate writes: January 10, 2016, will enter in the Linux history books as the day when the Linux kernel 4.4 LTS (Long-Term Support) has been officially released by Linus Torvalds and his team of hard working kernel developers. Prominent features of Linux kernel 4.4 LTS include 3D support in the virtual GPU driver, allowing for 3D hardware-accelerated graphics in virtualization guests, a leaner and faster loop device that supports Asynchronous I/O and Direct I/O, thus increasing the system's performance and saving memory, and support for Open-Channel Solid State Drives (SSDs) through LightNVM. Phoronix also took a look during the newest kernel's development cycle, and has an overview of 4.4's new features.
will it (Score:1)
Re: (Score:2)
Via Wine, yes. And it's been reported that Crytek is adding Native support. Yes, I know it was a joke...
Re: (Score:1)
Re: (Score:2)
I don't even know what Open Channel SSDs are, though.
Re: (Score:1)
I thought it was supposed to natively support upgrading without needing to reboot. :/ I should probably read the article but I have standards. To me, that's the most interesting thing. It can be done with kexec right now (I think?) but having it native and automated would be kind of nice. I might never have to reboot again! That'll save like 30 seconds every month! Or, more seriously, just let me keep doing what I'm doing without feeling an urge to reboot and load the new kernel.
For the record, I have kexec
Re: (Score:2)
You are probably talking about live-kernel patching (kGraft - Suse, kpatch - RedHat, sort of similar to ksplice - now Oracle).
Because that is all it is:
security updates without reboot.
Not: new functionality or large bugfixes.
kexec is cool, but kexec just means: faster reboot into new kernel (no waiting on the BIOS, etc.). The old kernel starts a new kernel directly.
The people from CRIU (save and restore running processes) want to combine their solution with kexec so you can do fast upgrades eventually:
"When
Re: (Score:2)
Cool, thanks. I've never compiled and used my own kernel. I've bookmarked the Ubuntu documentation page and I might just have to give that a shot. I guess I could wait patiently for it to come down the pipe. Knowing it was coming was why I've not played with kexec yet - I figured that 4.4 was going to be here and an earlier announcement had said that it would have the ability to do security patches without the reboot. That's the feature that I'm most looking forward to - it's the feature that's most likely
Re: (Score:2)
live kernel patching is not kexec.
kexec is an old feature, kexec is not new.
You can do kexec with old kernels on Ubuntu right now. You can just try it on your desktop machine.
install kexec-tools the setting to enable kexec are in /etc/default/kexec I assume on Ubuntu.
Then do a reboot, if you've done everything right, you won't see a BIOS screen, just an Ubuntu shutdown and Ubuntu start up. And it will be faster because of it.
Live kernel patching is only for security updates and you'll want to wait for your
Re: (Score:2)
Also live kernel patching also don't really help you with remote hardware.
Maybe the opposite.
Because in case live kernel patching you don't reboot with the new kernel, just keep it running the old kernel with only the security patch applied.
That could mean you did not test the normal way of booting with the new kernel.
So when the machine does reboot unexpectedly (like power failure) it might not boot normally because you didn't test booting the new kernel after installing the security update.
Re: (Score:1)
Hmm... Valid point but probably not entirely too problematic. My whole house is a UPS of sorts. I have solar and wind and use the mains as a backup but I pull from the batteries in the basement and not from the sources directly. There are also two generators with one being a bit smaller and a fail-over. (I live way out in the middle of middle of nowhere NW Maine.) Only the server in the basement is an actual server with a redundant power supply so it could still suck. Methinks I've got some learning to do.
Re: (Score:2)
People might talk about electric cars like it's something new... ;-)
But your house already works more or less like a submarine.
They however use diesel/gas to charge the batteries:
https://en.wikipedia.org/wiki/... [wikipedia.org]
Anyway, if you have a couple of hundred servers, you'd still want to reboot them after live-patching occasionally even if you have your power sources are OK (I've seen datacenters going down because of airconditioning failing). Because if to many servers fail at the same time, you'd have a long down
Re: (Score:1)
I have, now, more cars than servers. I once had the opposite but I had, eventually, professionals to manage them. I only held the roles of IT and programmer because I needed to, not because I was particularly skilled. In fact, USENET saved my bacon more often than I can count. I don't even bother to lie and pretend I was good. :( No, I actually *hated* computers at first.
Ah, one of my favorite quotes from a fairly new programmer that I'd hired. I was still "helping" then.
"Code comments go in the code, not o
Re: (Score:2)
No problem.
If you want I can send you my email address for more direct contact. Is that outlook address I see a real address ?
Re: (Score:1)
It is. I was really quite pleased to get that address. I jumped at the chance. I didn't really want a new email address but I just had to have the name - I caught the Outlook offering new email on the first day or close to it. I typed it in to see, my name was already taken, and there it was. So, I grabbed it.
Re: (Score:2)
It can be done with kexec right now (I think?) but having it native and automated
What could possibly go wrong with allowing automated patching of the running kernel...
Re: (Score:1)
Not a whole lot that's major - it's me, my home servers, and desktops. If I break something then I learn something new as I'm fixing it. I actually make it a point to try to break stuff in new and interesting ways - it's how I learn to fix it and, with fixing it, I learn new stuff. How to make this short?
I'm retired. I used Unix for quite a while. I then used Windows. During that spell, I also used Unix (Solaris) on the workstations. I poked at Linux when it came out, or not long after. I kept using Windows
Re: Story time! (Score:2)
Yeah, I didn't mean you specifically; rather the idea of this being a feature added to the mainline kernel for everybody, which sounds like a potential attack vector not unlike the ability to reflash your BIOS from software to me.
I was kind of casually messing around with Linux (LiveCDs, then within a year or two a dual-boot) since not too long after I started college (headed towards 10 years ago now? damn.), but the limit of my expertise on that front was basically googling enough to get some desktop stuff
For a more complete changelog: (Score:5, Informative)
For a more complete changelog:
http://kernelnewbies.org/Linux... [kernelnewbies.org]
Re: (Score:3)
The KernelNewbies website alive? With a changelog the day of the release rather than half a year later? Must be fake.
Re: (Score:1)
Do you have a specific issue, or are you just worried about a popularity contest?
I've been using it as my primary desktop OS for nearly 18 years now.
Re:Where do these impressive features matter? (Score:5, Informative)
They matter on my desktop.
They matter on the desktops of all these administrations over the world that deploy linux operating system.
They matter in all the cloud infrastructure that rely on virtualization for load balancing.
They matter in the data center that are moving toward SSD for I/O.
They matter in 80% of the cell phones in the world that deploy the linux kernel.
Re: (Score:2)
Re: (Score:2)
They matter in 80% of the cell phones in the world that deploy the linux kernel.
Not really, all those phones are stuck at 3.xx. You'll have to wait for quite a long time to have 80% of all phones (or even Android phones) to reach 4.4.
Re: (Score:3)
Folks, it bothers me that even with all these features, Linux [still] doesn't matter on the desktop. Where are these features really having impact?
Do you feel inadequate if you aren't using the most popular computer OS or something? I never ascribed to the idea thatm one should use Windows because it is the most "popular". I use linux on the desktop because I like it. That's all I need.
Re: (Score:1)
Linux is mostly contributed to by corporate entities, so solutions to their problems tend to get fixed first.
Of course. Each of the thousands of developers who contributed code first made sure to obtain the latest copy of those corporate entities secret agendas. There's a parameter for that when you run "git clone".
Re: (Score:2)
When you understand how Linux development works get back to us. I can assure you that every change is made based on technical merits. You can get your favourite feature added. You just need to submit extremely solid code that will withstand peer review by many of the most competent OS Engineers on t
Re: (Score:3, Insightful)
Folks, it bothers me that even with all these features, Linux [still] doesn't matter on the desktop.
Well, the thing is - "the desktop" matters less now than it ever has before.
matters on my desktop. Linux outsells Windows (Score:5, Interesting)
80% of computers sold last year were SOCs (mobiles). Another x% were servers. So the desktop market is maybe 15% of the market. More Linux systems were sold last year than Windows systems and the trend is increasing each year.
With that said, who said Linux doesn't matter on the desktop? It matters on MY desktop, and has for 15 years. For most of the last 15 years, I worked for an information security company, so Microsoft software was not allowed on the company network. All desktops and laptops were Linux, no as were some firewalls, load balancers, most servers, etc.
They don't buy Windows phones! MS spent billions (Score:2)
You may be of the opinion that the OS doesn't matter but after billions and billions of dollars MS spent on development and marketing, they don't buy phones with Windows on them.
> or Android could have easily been BSD based.
And every Dell, HP, and Compaq desktop could have easily be running Mac, had Apple chosen to allow that. Mitt Romney could have president. That's not what happened.
Re: (Score:2)
If you have problems with the prevalence of Linux on the desktop the kernel is likely the least of your concern.
So at the risk of being called a dumbass ... (Score:2)
Re: (Score:1)
Yes, compiling and installing your own kernel is very normal on a linux box. You configure all the modules you want compiled in/compiled for side loading, install it somewhere your bootloader can load it, and reboot.
Re: (Score:3, Informative)
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-wily/
Umm yes they do. Works fine on 14.04. YMMV.
Re:So at the risk of being called a dumbass ... (Score:5, Insightful)
Not a dumbass. Everyone had to learn everything they know at some point in their life.
Today is your day for kernel compilation! Yay!
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel [ubuntu.com]
Re: (Score:1)
Re: (Score:2)
Re: (Score:2)
openSUSE Tumbleweed (Score:1)
Get Tumbleweed. It's a rolling release -- it stays up to date with a reasonable week or two lag (to allow for stability testing). Currently runs kernel 4.3.3, suspect it will go to 4.4 in a few weeks. Been using it a while now and really enjoy it.
Re: (Score:3)
Search for "rolling release linux distro" on your favourite search engine.
Some popular distro's:
- Gentoo: www.gentoo.org (or Funtoo www.funtoo.org - created by the original founder of Gentoo)
- ArchLinux: www.archlinux.org
- Sabayon Linux: www.sabayon.org
- Lunar Linux: www.lunar-linux.org
Re: (Score:2)
not Windows. Start with existing config, keep old (Score:2)
You CAN use a bleeding-edge distro but you don't need to if you just want a new kernel. Unlike Windows, you can use a new kernel with an older userland or vice-versa. You can update the kernel without updating the "operating system". (Modulo fucking systemd.)
Your bootloader will let you choose the kernel when you boot, and you can set it to fallback to a known-good kernel, so there is little to no risk in trying different ones. I tend to keep the last three kernels I used, just because there is no reas
Re: (Score:2)
Debian has v4.2, but its closed binary NVIDIA driver doesn't work with it due to compilation issues. :(
Things not fixed: (Score:2)
you can't fix everything: https://www.youtube.com/watch?... [youtube.com]
I like systemd (Score:1)
I guess I'm just an old fart that happened to adapt to SMF early on. All the complaints were the same, now every last Solaris holdout will shove SMF in your face if you try to do a comparison to Linux.
Honestly, the SMF manifests are somewhat easier to understand, but systemd is more powerful. And systemd is only going to get better, as they have motivated ppl. behind the project, unlike Mr. Ellision that can't wait until Solaris meets the deuce.
Linux Kernel 4.4 LTS? (Score:2)
Linux Kernel 4.4 LTS? There is no such thing. It is Linux Kernel 4.4, and which vendors support it and for how long is up to them. Maintainer patches to a stable branch may only go on for a year or two, if that. After that it is pretty much up to various vendors.
Re: (Score:3)
Re: (Score:2)
Re: (Score:2)
I look at log files almost daily, especially when something goes wrong.
Re: (Score:1)
So it comes broken by default then?
Re: (Score:2)
Logs are for the rare occasions when something *does* go wrong. Saying "when was the last time you needed a log" is a vacuous statement unless the product is 100.00% reliable.
Re: (Score:3)
Sadly, I don't think systemd is going away anytime soon. The biggest voice behind it (Red Hat) effectively controls the "GNU/Linux" world. The kernel is on a completely different level - it is the base that everything else (including systemd) builds around, and non-GNU Linux versions (like Android) will receive these features.
Re: (Score:2)
Re: Is the systemd problem fixed yet? (Score:2, Informative)
Like doing the work of actually supporting the alternatives yourself. I have a regular day job. I spend nights and weekends packaging software for a popular GNU/Linux distribution. I'm not alone. I have better things to do than to make sure that everything works with every possible combination of systemd or non-systemd just because a few people have something against it. If you think it's so important to not use systemd then you better step up and do the work yourself.
Re: Is the systemd problem fixed yet? (Score:2, Funny)
Assuming the average nerd weighs 100 kg a metric ton is just 10 people.
Which effectively doubles the *BSD user base, of course. :-)
Re: (Score:2)
Systemd is a pain in my side as an admin, and when I do help with open source software systemd isn't a concern of mine - Linux isn't my only target when it comes to software, it's Unix compatibility in general (actually, Linux compatibility isn't my main concern anymore either).
Re: (Score:2)
It used to be that Linux was dependable for cool stuff, but the BSDs are just dependable, that's my first impression.
Re: (Score:2)
To be honest, and Unix implement is an alternative. I have systems at home running Solaris (8-10), IRIX (6.5.29), and OS X (10.4 and 10.5 on PPC, 10.6 and 10.7 on Intel); I used to use HP-UX and AIX, and I've got a bit of FreeBSD experience at this point too. It's the Linux crowd that really likes to piss off its users.
Re: (Score:2)
Re: (Score:2)
Re: (Score:1, Interesting)
As a person who just installed CentOS 7 for the first time the other day, I have to say that installation and configuration for my purposes takes much less time with CentOS 7 compared to Windows 7.
Add in all the spying shit you have to turn off (or attempt to turn off) in Windows 10, and it's clear that Linux is the option that will cost you less time.
time *IS* money (Score:2)
Time is money. So, if it doesn't save time, it isn't saving money.
Besides, Linux is meant to boot your machine and provide basic OS service---not save you time or money.
Re: (Score:2)
Re: (Score:2)
You could consider debian KFreeBSD instead, it's debian with the FreeBSD kernel - and it's not got systemd and probably never will.
Re: (Score:2)
Re: (Score:3, Insightful)
This is an article about the linux kernel. Random systemd complaints like the one you champion so are offtopic and very annoying. While systemd affects the greater GNU/Linux ecosystem, it has squat-all to do with the kernel.
I don't have mod points right now, and so didn't have to spend my mod points on -1-offtopic'ing the shrill anti-systemd crowd that try
Re: (Score:3)
Re: (Score:1)
Baseless insults that ignore reality will not make you systemd-fanatics any friends. Even though ignoring reality is how you have operated the whole time, others may actually have some real understanding of what is going on.
Re: (Score:2)
Mod GP fucking retarded! (Score:2, Insightful)
Look at the subject for fuck sake, anybody with any clue about this knows that this has absolutely nothing whatsoever to do with systemd. What do you expect the kernel developers are supposed to do about systemd? Do you understand what systemd is? Obviously not. Do you understand what Linux is? Again obviously not. Part of the reason the genuine criticism of systemd was ignored is because it was drowned out by nitwits like you who don't have a clue what you're talking about and just want so desperately to f
Re: (Score:2)
Re:We'll explain it to you step-by-step. (Score:5, Insightful)
Let me preface this by saying that I am not, by any means, a professional Linux administrator. I did, on the other hand, admin a bunch of servers as a part of my profession but those were mostly Unix and then Windows and then I hired competent professionals.
That said, I'd love to hate SystemD. I love me a good hate-fest. I keep pre-pitched torches at the ready and carry a fold-away assault pitchfork. I have various servers at home, some running on real server hardware, and a whole network of computers. (What self-respecting geek doesn't?) I have more VMs than I possibly need, doing things that I have no idea what I was thinking at the time, and am connected to my system in Maine via the most convoluted route possible. I have co-lo equipment that sits mostly idle and houses a few friend's sites and that's about it... It doesn't really do much of anything but, damn it, I have it!
You know what almost all these various computers have in common? Oh, they've got a whole host of distros on them - I'm not even sure I can quickly figure out which one is which any more. My topography looks like it was designed by a crack-addled five year old with admin privileges. I'm currently using a Live USB (Lubuntu), through a VPN, to my house, in a VM, to the 'net, through a VPN - and I'm skipping a few steps to keep it simple for you. This thing, for lack of a better word, shouldn't even run - never mind be stable. But this thing, with all these distros, has that one thing in common that I asked about. It's SystemD.
Yup. I guess they all have Linux in common but they sure as hell don't all have the same version of the kernel. So, there's that. But, they do all have SystemD (except for a few VMs - those are BSD, Minix, Indiana, and a few others but those don't actually get booted very often) for the most part. The all seem to work. Oh, I tried to hate SystemD. Yet, it's not caused me a single problem yet. I learned a few new comments, I've surely done something that should have broken it by now, and I've even read parts of the man pages.
Oh, I know it's not the Unix Way. Well, except it could be 'cause the Unix Way has exceptions. I know, it's got binary logging but - you can actually read those logs with a few different tools if you need to. I haven't needed to so I won't say that they work well but I'm told they work well enough. Yes, it does more than it needs to and it's not what we're used to. Meh, I'm okay with that - staying static is nice for some things and avoiding monolithic things is a good idea. Yet, it works. It works fine for me. I know, I am not everyone but I suspect the vast majority of the people complaining haven't actually used it. Even Hairyfeet complains and he's a Windows user - he's an ardent opponent of SystemD but he's probably never even tried a distro with it.
So, yeah, my pitchfork is starting to get rusty and needs to be sharpened again. My torches were lit but I just dunked 'em in water 'cause there didn't appear to be any monster that needed slaying. It's too bad, I had enough torches to go around. I want to hate it - I really do. It's not that I have some great skill that keeps it working - it works DESPITE my best efforts to screw things up. Oh, I screw up lots of things but it's not yet been the fault of SystemD nor has it prevented me from repairing my mistakes.
I dunno... I notice lots of lists of things people hate. I notice very few anecdotes of how it has harmed them. I've noticed even less actual compilations of data concerning it. If it's that bad then, well, we should have some data and someone would have compiled it. (The data, not systemd.) If a bumbling idiot, such as myself, can manage it - and not have a problem, then it seems only logical that smarter folks can figure it out, no? I mean, hell, I'm in a Live USB environment because I hosed GRUB again and I've not yet rebooted after fixing it. You'd think that, by now, SystemD would have been a problem for me. I kind of wish it had, then I could blame my mistakes on it.
What? I made a typo?!? It's that damned SJW SystemD's fault I tell you! Heh, seriously, all I can say is that I'm not really all that adept and it still manages to not cause me any problems. I learned to do a few things differently, I learned a few new commands, and I've had good luck so far. It's yet to be the cause of any problems and that's not for lack of trying. Hell, I've even (don't tell anyone) used some of its features to diagnose and fix a startup issue. Yup... It's got a handy feature that tells you what to blame (it's even called blame) when you've got issues with a slow startup.
Err... I think it's systemd-analyze blame by the way.
Re: (Score:2)
That's what they tell me, but of course, my Debian systems using systemd actually still seem to log the same old stuff to the same old files. :)
Re: (Score:1)
I have not yet not found a log that I was unable to read. (That's English, right?) I am downstream from you - I'm in the Ubuntu family (more often than not) but I prefer Lubuntu. At this point, and I'm a silent subscriber to all sorts of mailing lists, I have to wonder how many of those people who register their complaints here (and at a few other sites) are actually Linux users or have problems?
Now, as I said, I'm not a professional admin and I'll be the first one to mention that. That means, feel free to
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Only if you are using certain versions of one particular boot loader - which many of us never were using.
Re: (Score:1)
That and it's not root access. It's just the bootloader. It's not even a very valuable security tool to use. There are few reasons to even have used that feature and to rely on it solely seems foolhardy. I could see it in use at a kiosk but one shouldn't be allowing physical access to the computers there nor allow users to issue reboot commands from there. All-in-all, a bug but not a very important bug and overblown by people who seem to think it gave potential "root" access by itself. It's not their fault
Re: (Score:2)
Re: (Score:2)
Yes, the term is largely meaningless. It seems to me that LTS actually means that so long as you don't need to upgrade any third-party applications (that inevitably have dependencies on newer, non-LTS, libraries), then any bugs you report might get fixed - provided you're a MAJOR PLAYER in the Linux arena with clout and someone in the support team is bored enough to choose to fix bugs ... and picks on yours as being easy enough to tackle.
So it's long-term support, all right. Just so long as you don't chan