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.
Do I understand correctly that I can't use 4.19 from current-Slackware on 14.2 if I need the virtualbox modules? (For 4.14 this was possible.)
I don't use VB and if this is the only issue, I'll keep using current and not spend countless hours compiling a kernel while holding up my main machine.
Do I understand correctly that I can't use 4.19 from current-Slackware on 14.2 if I need the virtualbox modules? (For 4.14 this was possible.)
I've only seen this mentioned by two people on the forum and haven't tested it myself. I've never had an issue in the past, but I haven't tried since the newer GCC as I've always made a few minor modifications to the kernels or wasn't on the same version as -current.
Just build 4.19.12 on 14.2-x64 standard install system. Everything appears to be working correctly after reboot. More testing to follow. I don't use any virtual machines at this time. Just an FYI.
Do I understand correctly that I can't use 4.19 from current-Slackware on 14.2 if I need the virtualbox modules? (For 4.14 this was possible.)
Quote:
Originally Posted by Didier Spaier
Thats what I am doing (on a derivative of Slackware version 14.2, same base libs). uname -r says: 4.19.2
No issue so far.
PS And I have the VirtualBox modules (using the VB installer) that auto-upgrade themselves whenever I upgrade the kernel.
So, it works, but based on other replies I should not be surprised if it will fail one day. Sounds like one more reason to migrate to kvm. I thank everybody who replied!
It's official I can now build and install new kernels in Slackware64-14.2 / UEFI with my eyes closed and one hand tied behind my back.
MERRY CHRISTMAS TO ALL
john
Yes, me too !
But 55020 seems to be able to get-r-dunn on DUSK with both hands tied behind his back
Linux 4.20 released..
From: Linus Torvalds
Date: Sun Dec 23 2018 - 19:27:30 EST
Let's face it, last week wasn't quite as quiet as I would have hoped
for, but there really doesn't seem to be any point to delay 4.20
because everybody is already taking a break.
And it's not like there are any known issues, it's just that the
shortlog below is a bit longer than I would have wished for. Nothing
screams "oh, that's scary", though.
And as part of the "everybody is already taking a break", I can
happily report that I already have quite a few early pull requests in
my inbox. I encouraged people to get it over and done with, so that
people can just relax over the year-end holidays. In fact, I probably
won't start pulling for a couple of days, but otherwise let's just try
to keep to the normal merge window schedule, even if most people
hopefully won't even be back until over the merge window is over.
As to the details of this last week of 4.20 - most of it is networking
(drivers, core networking fixes, bpf). There's a few other non-network
driver updates too, and a revert series of some of the x86 inline asm
changes that were obviated by upcoming compiler support.
Details below.
Have a Merry Christmas or other holiday of your choice.
Linus
---
When he has the time, Board Member 55020 will, mostly likely, be kind enough to provide
his Dave's Unofficial Slackbuilt Kernel update for the 4.20.y series at, https://dusk.idlemoor.tk
Last edited by cwizardone; 12-23-2018 at 07:05 PM.
Linux 5.0-rc1
From: Linus Torvalds
Date: Sun Jan 06 2019 - 21:14:39 EST
So this was a fairly unusual merge window with the holidays, and as a
result I'm not even going to complain about the pull requests that
ended up coming in late. It all mostly worked out fine, I think. And
lot of people got their pull requests in early, and hopefully had a
calm holiday season. Thanks again to everybody.
The numbering change is not indicative of anything special. If you
want to have an official reason, it's that I ran out of fingers and
toes to count on, so 4.21 became 5.0. There's no nice git object
numerology this time (we're _about_ 6.5M objects in the git repo), and
there isn't any major particular feature that made for the release
numbering either. Of course, depending on your particular interests,
some people might well find a feature _they_ like so much that they
think it can do as a reason for incrementing the major number.
So go wild. Make up your own reason for why it's 5.0.
Because as usual, there's a lot of changes in there. Not because this
merge window was particularly big - but even our smaller merge windows
aren't exactly small. It's a very solid and average merge window with
just under 11k commits (or about 11.5k if you count merges).
The stats look fairly normal. About 50% is drivers, 20% is
architecture updates, 10% is tooling, and the remaining 20% is all
over (documentation, networking, filesystems, header file updates,
core kernel code..). Nothing particular stands out, although I do like
seeing how some ancient drivers are getting put out to pasture
(*cought*isdn*cough*).
As usual even the shortlog is much too big to post, so the summary
below is only a list of the pull requests I merged.
Go test. Kick the tires. Be the first kid on your block running a 5.0
pre-release kernel.
Linus
---
Last edited by cwizardone; 01-06-2019 at 08:25 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
