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.
"modules.builtin" is better in the kernel package than in the kernel-modules
Currently, the "modules.builtin" and compiled "modules.builtin.bin" files are included in the kernel-modules package reflecting all modules in the package.
However, the files are for showing all modules that are actually built into the kernel.
Thus, when installing the kernel package, the files should also be installed along the kernel to avoid the module loader's confusion.
So, how about changing the kernel packaging scripts like below ?
(Here I show patches for only -modules and -huge. -generic and other scripts also need to be patched.)
Code:
--- packaging-x86_64.orig/kernel-modules/kernel-modules.SlackBuild 2017-05-09 19:55:00.000000000 +0900
+++ packaging-x86_64/kernel-modules/kernel-modules.SlackBuild 2017-05-17 15:33:57.805705348 +0900
@@ -52,6 +52,9 @@ fi
EOF
+# Exclude modules.builtin
+( cd $PKG/lib/modules/${KERNELRELEASE}; rm -f modules.builtin modules.builtin.bin )
+
cd $PKG
/sbin/makepkg -l y -c n $TMP/kernel-modules-$(echo ${VERSION} | tr - _)-$ARCH-$BUILD.txz
--- packaging-x86_64.orig/kernel-huge/kernel-huge.SlackBuild 2017-05-09 20:04:00.000000000 +0900
+++ packaging-x86_64/kernel-huge/kernel-huge.SlackBuild 2017-05-17 15:54:00.523535664 +0900
@@ -23,6 +23,7 @@
KERNNAME=huge
VERSION=${VERSION:-4.9.27}
+KERNELRELEASE=${KERNELRELEASE:-4.9.27}
ARCH=${ARCH:-x86_64}
KARCH=${KARCH:-x86}
BUILD=${BUILD:-1}
@@ -90,6 +91,17 @@ cp $SYSMAP $PKG/boot/System.map-$KERNNAM
cp $CONFIG $PKG/boot/config-$KERNNAME-${VERSION}
( cd $PKG/boot ; ln -sf config-$KERNNAME-${VERSION} config )
+# Make modules.builtin.bin
+# Todo: Use modules.builtin from current kernel source and run depmod, is this OK ?
+cp /usr/src/linux-${VERSION}/modules.builtin /lib/modules/${KERNELRELEASE}
+depmod -a ${KERNELRELEASE}
+
+# Copy back modules.builtin and modules.builtin.bin into the package
+mkdir -p $PKG/lib/modules/${KERNELRELEASE}
+cp /lib/modules/${KERNELRELEASE}/modules.builtin $PKG/lib/modules/${KERNELRELEASE}/modules.builtin.${KERNNAME}
+( cd $PKG/lib/modules/${KERNELRELEASE}; ln -sf modules.builtin.${KERNNAME} modules.builtin )
+cp /lib/modules/${KERNELRELEASE}/modules.builtin.bin $PKG/lib/modules/${KERNELRELEASE}/modules.builtin.bin
+
mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc
It is likely that we'll see the move from KDE4 to Plasma 5 this cycle since KDE4 development has pretty much ceased except for security fixes. All major development has moved to Plasma 5. Alien Bob already has packages for Plasma 5 for -current in his ktown repo, so as soon as Pat is ready to throw the switch, it should be relatively easy to move to it.
Strongly disagreed!
So you guys talk with serenity about putting down half of the packages shipped by Slackware, and to replace them with The Thing which is glorious NOT useful, unstable, wrong by conception and with graphics made by Stevie Wonder when he was high?
Meanwhile, IF I ask for including those damned FOUR packages, which are needed for LinuxPAM, and finally, but finally finally, after hundred years, the Slackware to start to behave as a good citizen in a damned office network, you will come in my porch with guns and yelling "BOB is great!" !?!
Damn, permit me to laugh with tears!
Last edited by Darth Vader; 05-17-2017 at 01:10 PM.
Well, RH => Fedora is still considered upstream although they don't really use newt, but they did not merge (or rejected) useful Debian patches, including the bidi patch that allows to properly display bidirectional scripts in Whiptail (used in Debian text installer), rejected by Fedora long ago. So I strongly suggest to apply the patches in http://http.debian.net/debian/pool/m....debian.tar.xz accessed from https://packages.debian.org/sid/libnewt0.52 listed in debian/patches/series in the archive (I assume that other patches in debian/patches have already been applied "upstream", see debian/changelog), and at the very least the bidi patch.
Last edited by Didier Spaier; 05-18-2017 at 05:16 AM.
[...] It is likely that we'll see the move from KDE4 to Plasma 5 this cycle [...]
That would be very welcome indeed! Not that I find anything wrong with KDE4, it's a good and proven DE. But the number of applications that have shifted their development to require KDE5 or at least Frameworks 5 is growing, and there are at least three of those in my workflow.
Indeed it does, it seems, based on some preliminary testing here. The bothersome part is that I've been following the git changes, and nothing in those changes between 2.6.4 and 2.6.5 looks like it should address what I was seeing. I'm going to give it some more time before I queue this one for Pat. Thanks for keeping up with it - I appreciate the testing and heads-up!
So you guys talk with serenity about putting down half of the packages shipped by Slackware, and to replace them with The Thing which is glorious NOT useful, unstable, wrong by conception and with graphics made by Stevie Wonder when he was high?
Meanwhile, IF I ask for including those damned FOUR packages, which are needed for LinuxPAM, and finally, but finally finally, after hundred years, the Slackware to start to behave as a good citizen in a damned office network, you will come in my porch with guns and yelling "BOB is great!" !?!
Damn, permit me to laugh with tears!
I never dump on your suggestions to upgrade packages... I'm just always amazed that you're totally against anything being newer in Slackware except for programs you're interested in, like PHP.
And I didn't suggest for Pat and company to upgrade to KDE5, I just added my speculation that I think it will happen. KDE4 development is mostly done. They've all moved onto Plasma 5, so it makes sense that Pat would likely follow if he's to keep KDE in the distribution. Whether or not you like that is irrelevant to the discussion, especially because you won't be involved in that discussion, just like most of us.
And I remember hearing all these same arguments when Slackware switched from KDE3 to KDE4. Change is inevitable. Better suck it up or move on...
A regression in gcc-7.1.0 completely broke the OpenGL renderer for the emulator PCSX2 by compiling incorrect code with certain optimizations. After some effort to figure out where it broke it was reported upstream to gcc by one of the PCSX2 devs and then fixed in gcc. However gcc-7.2 won't be out till around September/October, can the gcc-7.1.0 in current be patched with the upstream fix in the meantime?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
