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.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,126
Original Poster
Rep:
Quote:
Originally Posted by ZhaoLin1457
Is there a reason why DUSK does not ship also packages for the 4.20 kernels?
TBH, I would like to try the well made DUSK kernels on 4.20 versions.
Eventually, if someone here can suggest me a good config for the 4.20 kernels, would be greatly appreciated.
Well, board member 55020 has been providing non-LTS kernels out of the kindness of his heart, so I would imagine he is either on a well deserved vacation or he just hasn't had the time to add 4.20.x to his repository.
Last edited by cwizardone; 01-23-2019 at 10:59 PM.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,011
Rep:
Quote:
Originally Posted by ZhaoLin1457
Is there a reason why DUSK does not ship also packages for the 4.20 kernels?
TBH, I would like to try the well made DUSK kernels on 4.20 versions.
Eventually, if someone here can suggest me a good config for the 4.20 kernels, would be greatly appreciated.
Making a new kernel is not that difficult or risky. Just remember to add your new kernel under different name than the last kernel that succesfully loaded your system so if your new kernel fails to boot, you can always select from grub/lilo last kernel that worked.
The Stable NVidia Blob(s) will not compile against Linux Kernel 4.4.168 - 4.4.172 due to a change in get_user_pages() that was introduced in linux 4.4.168.
All is not lost ( but YMMV ) ...
NVidia 418.30 Beta DOES build and run fine with the NVidia 970M on my Laptop
I am running NVidia 418.30 now but I had to revert to 4.4.167 because vmware won't build against 4.4.172 !!!
Linux 5.0-rc5
From: Linus Torvalds
Date: Sun Feb 03 2019 - 17:03:29 EST
I'm happy to report that things seem to be calming down nicely, and
rc5 is noticeably smaller than previous rc's. Let's hope the trend
continues.
About a third of the changes are to drivers (networking, rdma, scsi,
block, misc), with the rest being spread out all over (tooling,
networking, filesystems, arch updates, core kernel..)
Nothing looks particularly worrisome, so assuming the trend holds, we
look to be on track for a fairly normal release cycle despite the
early hiccups due to the holidays.
Go out there and test in between the commercial breaks,
Distribution: slackware 15.0 64bit, 14.2 64 and 32bit and arm, ubuntu and rasbian
Posts: 495
Rep:
it is worth mentioning that default cifs in recent kernel does not try smb1 so fails to mount smb1 shares unless you use vers=1.0 in the options of the mount command. I discovered this as my main file server holding slack and updates is running on 13.1, and after kernel upgradeon a new pc, it could not connect until I applied the "fix".
CVE-2018-16880
A flaw was found in the Linux kernel's handle_rx() function in the [vhost_net] driver. A malicious virtual guest, under specific conditions, can trigger an out-of-bounds write in a kmalloc-8 slab on a virtual host which may lead to a kernel memory corruption and a system panic. Due to the nature of the flaw, privilege escalation cannot be fully ruled out. Versions from v4.16 and newer are vulnerable.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.