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.
No wireless connection after 5.4.0 upgrade, no unbound working, Thunar takes forever and a day to open. Back to 5.3.11 with no problems. We need to give it some time to grow.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Original Poster
Rep:
Just in time for the holiday weekend, another round of kernel updates has been scheduled for release on Friday evening, 29 November 2019, at approximately 20:00, GMT.
If no problems are found while testing the release candidates, they might be available early Friday morning (depending on your time zone).
There will be 66 patches in the 5.4.1 kernel update, 95 in 5.3.14, 306 in 4.19.87, 211 in 4.14.157, 151 in 4.9.204 and, finally, 132 patches in the 4.4.204 update.
They've been telling people not to use it for long enough.
man 2 sysctl:
Quote:
Glibc does not provide a wrapper for this system call; call it using
syscall(2). Or rather... don't call it: use of this system call has
long been discouraged, and it is so unloved that it is likely to disap‐
pear in a future kernel version. Since Linux 2.6.24, uses of this sys‐
tem call result in warnings in the kernel log. Remove it from your
programs now; use the /proc/sys interface instead.
Yes. All Slackware scripts that execute sysctl do it only if /etc/sysctl.conf exists, and it doesn't by default. There are other ways to read/write to/from /proc/sys anyway. Maybe some sysadmins will have to adapt their custom scripts but hey that's life.
PS GazL beat me to it.
PS2 wrong interpretation from me, due to my misunderstanding. Please disregard this answer, thanks GazL for the heads-up.
Last edited by Didier Spaier; 11-28-2019 at 07:41 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.