[SOLVED] A new kernel for the stable branch and for -current!
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
A new kernel for the stable branch and for -current!
Time to upgrade your stable and -current boxes. In today's changelog:
Code:
Mon Dec 12 21:25:50 UTC 2016
a/coreutils-8.26-x86_64-1.txz: Upgraded.
a/grep-2.27-x86_64-1.txz: Upgraded.
a/kernel-firmware-20161211git-noarch-1.txz: Upgraded.
a/kernel-generic-4.4.38-x86_64-1.txz: Upgraded.
This kernel fixes a security issue with a race condition in
net/packet/af_packet.c that can be exploited to gain kernel code execution
from unprivileged processes.
Thanks to Philip Pettersson for discovering the bug and providing a patch.
Be sure to upgrade your initrd after upgrading the kernel packages.
If you use lilo to boot your machine, be sure lilo.conf points to the correct
kernel and initrd and run lilo as root to update the bootloader.
If you use elilo to boot your machine, you should run eliloconfig to copy the
kernel and initrd to the EFI System Partition.
For more information, see:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=84ac7260236a49c79eede91617700174c2c19b0c
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-8655
(* Security fix *)
I wrote my own system to auto-generate new kernel Packages from the official Slackware Kernel SlackBuilds but your dusk.Slackbuild is MUCH cleaner and simpler than my hand-rolled solution.
I LIKE it !
One question about the version of makepkg on your git repo.
Does your version of makepkg replace the official slackware makepkg ?
Do I need to be careful where I install it ?
Thanks and thanks for sharing the dusk.SlackBuild !
Does your version of makepkg replace the official slackware makepkg ?
Nope, that makepkg sits in the same directory as everything else (and is invoked as $CWD/makepkg instead of /sbin/makepkg). It's all in the right place when you clone it from gitlab. Here's the makepkg diff.
This is still *experimental* / unfinished / just for fun / learning / potential disaster / borderline heresy. Like hitest, I still use Patrick's kernels and have no plans to change
Last edited by 55020; 12-13-2016 at 05:34 AM.
Reason: unfinished, and no actual published packages yet
Anyone tried 4.9 yet? I've just run through make oldconfig and got my local config file ready for a build. Surprisingly there weren't that many new options to set given how large a changeset 4.9 is.
update:
Code:
test@ws1:~$ uname -a
Linux ws1 4.9.0-local #1 SMP Tue Dec 13 14:25:08 GMT 2016 x86_64 Intel(R) Core(TM) i3-5157U CPU @ 2.50GHz GenuineIntel GNU/Linux
Well, if nothing else. It still boots. Nothing obviously untoward in the kernel log.
Anyone tried 4.9 yet? I've just run through make oldconfig and got my local config file ready for a build. Surprisingly there weren't that many new options to set given how large a changeset 4.9 is.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Rep:
So, the Security Team e-mail this morning (actually, yesterday at 6:10 PM) for PHP, mcabber, loudmounth and the 4.4.38 kernel in the mail. Downloaded all of 'em, did the updates, remembered to run lilo, rebooted the main workstation.
One strange thing (well, two): something reported two fatal errors about couldn't find /lib/something 4.4.29 (when it was shutting down from init 6).
Hm.
I think -- think -- it's something to do with VirtualBox but prowling through the logs looking for what the error actually was turned up nothing.
Hm.
But, it rebooted, everything seems to be working (including VirtualBox). No second report of the fatal error.
OK, do the laptop and the two data base servers, no runs, no drips, no errors (seems like it must actually be VirtualBox), haven't gotten around to rebuilding it yet, still checking everything that matters.
I run the huge kernel, do not fiddle with anything kernelish (I don't care if it's a little on the big side, got plenty of RAM and lots of disk, just ain't worth messing with it. I don't know if I have an initrd, but I don't think so.
+------------------------------------------------------------------------+
| To leave the slackware-security mailing list: |
+------------------------------------------------------------------------+
| Send an email to majordomo@slackware.com with this text in the body of |
| the email message: |
| |
| unsubscribe slackware-security |
| |
| You will get a confirmation message back containing instructions to |
| complete the process. Please do not reply to this email address. |
+------------------------------------------------------------------------+
-----BEGIN PGP SIGNATURE-----
Anyone tried 4.9 yet? I've just run through make oldconfig and got my local config file ready for a build. Surprisingly there weren't that many new options to set given how large a changeset 4.9 is.
update:
Code:
test@ws1:~$ uname -a
Linux ws1 4.9.0-local #1 SMP Tue Dec 13 14:25:08 GMT 2016 x86_64 Intel(R) Core(TM) i3-5157U CPU @ 2.50GHz GenuineIntel GNU/Linux
Well, if nothing else. It still boots. Nothing obviously untoward in the kernel log.
Tried both 4.8.x for a while and 4.9 now, laptop boots as usual, sleep/hibernate works, no issues at all so far.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.