To stem the private emails I'm starting to get asking me where the latest stable kernel release signatures are at, please read about the recent changes for how we are doing kernel releases now.

Oh, and go update your kernels, there's updates out there now for everything :)

Good reading, another great find by the project zero people.

Oh, and I love comment #3 :(

Now this is how you write a changelog entry. It has it all, drama, complaining about broken hardware, crazy workarounds to keep warranties valid, extra work because we can't change other operating systems, and lots and lots of explanations of exactly what went wrong and how the author isn't giving up, no matter how many times it takes.

Great stuff.

I love it when a bottle of great whisky shows up at my doorstop with no explaination. I'm guessing someone finally decided to thank people for all of the crap they went through for the last round of security patches. Or in anticipation of whatever comes next? Who knows, either way, feel free to keep sending them on anonymous donor!

"Some providers now have something called Metal-as-a-Service, which I really think ought to mean that an '80s metal band shows up at your office, plays a gig, smashes the furniture, and urinates on the carpet, ..."

My Note 8 just updated itself from kernel version 4.4.13 to 4.4.111. Yes, the kernel is 5 months old, but it's better than being almost 2 years old!

Nice job, hopefully this continues...

This is a huge step forward for France, wonderful job done by +Laurent Joubert and many others in the French government, open source community members, other governments, and private companies as well. It was a huge collaboration effort, nice to see this get published.

I had this same type of conversation with at least 3 different groups of kernel developers in person this week:
"That's something that we should just turn an intern loose on."

Unfortunately, I don't have an intern...

So, let's try an experiment.

Wanted: semi-newbie kernel developer to do basic kernel development tasks.
Requirements: Willing to be given a stackdump and a reproducer or other type of description and can produce a working kernel patch and submit it upstream to the correct maintainers and mailing lists.
Location: Anywhere in the world, you work from home.
Time needed: whatever you can put into it.
Pay: none, but I will buy you all the free drinks of your choice at any conference where we both end up at. Odds are you can get a conference presentation talk and trip out of this as well, but I can't guarantee that.
Duration: How ever long you want, ideally at least a few months to get the hang of things.

Application process: Email me with a short description of your kernel experience, why you would be great at this, and why you want to do it.
Application deadline: May 31, 2018

And yes, this sounds a lot like "Do it for the exposure!" type of plea. You are correct, that is what it really is, but the thing is that these are tasks that wouldn't really get done otherwise as no company is putting people on them. So it's for the betterment of Linux here, which is a shared good. Also, these are not things you can just throw over the wall on a simple "here is a list of tasks to do." They require some basic hand-holding by an experienced developer to review and complete, so work on my side is going to going to be required.

Comments are locked here, email please.

Lest anyone think licensing "issues" are a new thing, here's a very fun, and long, read about the ncurses project history that I recommend for the popcorn factor alone.

Oh, and I learned that the "n" in ncurses is for "new". As a wise person once told me a long time ago when I tried to create the "hotplug-ng" project, "Don't be a fool and name your project 'new' or 'next generation', as it will just look dumb in a few years if it takes off."