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.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

This is my first post to Slackware community, so hello to everyone and please excuse me if something goes wrong!

I'm using Slackbuild's virtualbox build on 14.2 and after upgrade to kernel 4.4.172 it has stopped working.
I've tried to rebuild virtualbox-kernel package but with no success.

Thanks to montagdude's link above and bormant's fix there I was able to fix the Slackbuild's script.
I've built successfuly Slackbuild's 5.0.40 virtualbox-kernel package on 4.4.172 kernel and I'm running it without troubles at the moment.

But this does not work with the most recent VirtualBox 6.0.4-128413. For that one I followed the hack suggested by trasherdk and that worked. But since I don't really understand the code or the kernel change, I would prefer a more authoritative solution!

This is my first post to Slackware community, so hello to everyone and please excuse me if something goes wrong!

I'm using Slackbuild's virtualbox build on 14.2 and after upgrade to kernel 4.4.172 it has stopped working.
I've tried to rebuild virtualbox-kernel package but with no success.

Thanks to montagdude's link above and bormant's fix there I was able to fix the Slackbuild's script.
I've built successfuly Slackbuild's 5.0.40 virtualbox-kernel package on 4.4.172 kernel and I'm running it without troubles at the moment.

should there not be an # endif line in the patch to close the +# if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 4, 168) line ?

No, because the #endif is already in the source file (memobj-r0drv-linux.c). The patch only includes the changes and some (default to 3) lines before and after the context. Guess that the "# endif" would be visible (in the lines after the context) in the patch if "diff" was run with --context=10.

willysr,
it has been upgraded to version with changed API. De facto minor or major kernel version have to be changed for those istead of patchlevel increment in 4.4.168+. While 4.4.172 has 4.4 version, 3rd party software uses conditional compile paths for 4.9 to conform "new 4.4" API now.
And when breaking changes is already here why not to use 4.9 or 4.14 -- for those 3rd party software knows about those API and conditional compile paths.
And if numbers is the only true target not content may be 4.14 kernel in testing/ is a good enough for now.