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.
Just something to look at, the /boot/README.initrd is using kernel version 4.4.13 instead of 4.4.14 in its examples on the 14.2 release. This was a full install with Slackware64-14.2.
Just something to look at, the /boot/README.initrd is using kernel version 4.4.13 instead of 4.4.14 in its examples on the 14.2 release. This was a full install with Slackware64-14.2.
Similarly, the glibc.Slackbuild file in the 14.2 sources directory has the ancient line
Code:
--enable-kernel=2.6.32
Something worth changing each time the kernel is upgraded?
It is a setting that is necessary to build glibc to run on modern kernels.
I see, so the Slackbuild can remain as it is. However, the LFS documentation seems to suggest that this setting is not necessary to build glibc to run on modern kernels, rather it simply disables code supporting pre-2.6.32 workarounds.
if I remember correctly the glibc compatibility with kernel 2.6.32 has been set so that you can run Slackware under that specific kernel (also above, obviously) that is the last supporting openvz: this way you can have a Slackware openvz container hosted somewhere.
EDIT: yep: from 14.1 ChangeLog.txt
Code:
Fri Oct 24 21:11:15 UTC 2014
patches/packages/glibc-2.17-x86_64-9_slack14.1.txz: Rebuilt.
Rebuilt using --enable-kernel=2.6.32 for better compatibility with
host kernels when running Slackware in a VM or container.
Thanks to Vincent Batts and Eric Hameleers.
Since we are pointing out nuances in 14.2 I found another - when booting from the ISO (both x86 & x86_64) and starting pxesetup the banner on the top of the box reads:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
