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.
This is only a problem if you use deduping, which must be run manually anyway, its only used by a tiny precentage of people so is not earth shattering to the masses
resumming ...thats the new good way , and no need nothing more.
Please see the attached diff.
The issue is obviously the choice to have CONFIG_DEBUG_INFO=y in the kernel's config file for the genuine Slackware kernel-modules-5.18.5 package. Without that the the code snippet that you mentioned (applied by default as there is also STRIP_DEBUG=${STRIP_DEBUG:-YES} in the last version of the SlackBuild) is not necessary. I assume that these settings are chosen by Patrick to allow power users to get the debug symbols after recompiling only the kernel modules, while regular users get a smaller package out of the box. As an aside, with zstd compression my package's size is 94M while the genuine one's size (with stripping applied, I assume) is 398 M. You may consider that this does not make a huge difference in space on a big disk, but this allows me to ship a complete kernel-modules package in an installer's initramfs, saving the time that I previously needed to cherry pick the modules to include in it. I will keep my settings.
Oh, and the INSTALL_MOD_STRIP setting is nothing new, it has been provided since 2009
And this topic is not new either, it has been discussed long ago elsewhere, for instance here.
Last edited by Didier Spaier; 06-18-2022 at 01:29 AM.
The issue is obviously the choice to have CONFIG_DEBUG_INFO=y in the kernel's config file for the genuine Slackware kernel-modules-3.18.5 package. Without that the the code snippet that you mentioned (applied by default as there is also STRIP_DEBUG=${STRIP_DEBUG:-YES} in the last version of the SlackBuild) is not necessary. I assume that these settings are chosen by Patrick to allow power users to get the debug symbols after recompiling only the kernel modules, while regular users get a smaller package out of the box. As an aside, with zstd compression my package's size is 94M while the genuine one's size (with stripping applied, I assume) is 398 M. You may consider that this does not make a huge difference in space on a big disk, but this allows me to ship a complete kernel-modules package in an installer's initramfs, saving the time that I previously needed to cherry pick the modules to include in it. I will keep my settings.
Of, and the INSTALL_MOD_STRIP setting is nothing new, it has been provided since 2009
And this topic is not new either, it has been discussed long ago elsewhere, for instance here.
A friend of mine ended being locked out of his system, after trying to build the -current's kernel on Slackware 15.0
I helped him to recover his system with booting from my Slackware-on-SD-card. He used a 30GB root partition, which was fully filled by the kernel build, resulting in a crash and successively a malfunctioning system. I do not think that Mr. Volkerding considered with this debug config that an usual recommendation on the Slackware community is to have a 25-30 GB root partition and the rest of hard drive for /home.
I think that there should be a extra big warning about the current debug config generating a very large storage space consumption and why this happen.
Last edited by ZhaoLin1457; 06-17-2022 at 02:12 PM.
1 - never see the MOD_STRIP option , i miss since years and its a good one.
2 - debug config change on branch 5.18.x
In my opinion is not my bad in point 2 , cause thats an old option changed but not reflected on changelogs.
Thats didier to this acalaration.
But afetr all , the start of my request , is the bas idea , to use "find" "".ko files , its more easy and clean play with
NSTALL_MOD_STRIP0 install debug modules with debug NSTALL_MOD_STRIP1 install modules without debug
Because the find code from patrick fails when people enable some of the compress modules on the config , and modules ends not in *.KO extension.
The correct way is MOD_STRIP after all.
I cant imagine why need lost time to build more large process to remove debug later , cause the PKG is provided without debug and if need , a rebuild is required , then why no revert that and return to more fast builds , and use debug when something fails ?¿
In my side a revert that change on config , thanks didier to point me this change.
----------------------
Quote:
STRIP_DEBUG=${STRIP_DEBUG:-1}
NSTALL_MOD_STRIP=$STRIP_DEBUG
Quote:
make INSTALL_MOD_PATH=$PKG INSTALL_MOD_STRIP=$STRIP_DEBUG modules_install || exit 1
More easy ,More clean More elegant , and no fail if we use compressmodules XZ/ZSTD
Last edited by USUARIONUEVO; 06-17-2022 at 03:36 PM.
The bugfixes are typically small but important and include:
- Kcms/fonts: Fix font hinting preview. Commit. Fixes bug #413673
- Upower: Prevent integer overflow during new brightness computation. Commit. Fixes bug #454161
- Fix dragging especially by touch. Commit. Fixes bug #455268
Not sure is this is the best forum to request it, but for us sendmail diehards, whoever maintains sendmail in extra, please build a sendmail-8.17.1-noarch-4.txz with this fix
And while I am thinking of it (and I probably should know this)
where can I find the source patches which our slackware sendmail guy has applied to the sendmail-8.17.1 distribution to build noarch-3?
And while I am thinking of it (and I probably should know this)
where can I find the source patches which our slackware sendmail guy has applied to the sendmail-8.17.1 distribution to build noarch-3?
cd <source directory>
make DESTDIR=/tmp/lxc-5 install
cd /tmp/lxc-5/
makepkg -l y -c n ~/lxc-5.0.0-x86_84-1.txz
installpkg /root/lxc-5.0.0-x86_84-1.txz
Create the file /etc/sysconfig/lxc-net and add the following line:
Code:
USE_LXC_BRIDGE="true"
After this, I can run all my installed containers.
Last edited by alex14641; 06-22-2022 at 07:33 AM.
Reason: Add patch instructions
Thanks Drumz, I see. The most recent change was on 11 April , which must have been the cause of the uptick in the arch-n modification to 3.
I don't see any maintainer information anywhere in that directory, (nor a change history). Who maintains this package? Is it Patrick himself or someone else? Well, I don't really care who it is, but will whoever it is see this thread and apply the fix? Or is there some more formal way of requesting it? Of course I can build it myself but would like to be sure it is also in the next rebuild on the repo.
By the way, I should have explained that this bug hits only slackers running current, not stable 15.0. Occurrence of the problem was triggered by current applying upgrade of Cyrus Sasl from 2.1.27 to 2.1.28, but the bug is in sendmail, not sasl, as explained in the bug description.
Please add mount -a -t nfs4 into rc.inet2. Thank you
This should be handled by the below entry in rc.M, which occurs directly after running rc.inet2:
Code:
# Mount any additional filesystem types that haven't already been mounted:
mount -a -v 2> /dev/null | grep -v -e "already mounted" -e "ignored" | cut -f 1 -d : | tr -d ' ' | while read dev ; do mount | grep "${dev} " ; done
It will mount any final filesystems listed in /etc/fstab not already mounted and display the mount output for each newly mounted mount.
Is there a reason the command in rc.M that is ran after rc.inet2 doesn't cover your situation?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.