WordPress site for Linux and other computernerds
Since these are not available from the official Slackware repos, I compiled these myself, using the PHP 8.1 Slackbuild script. Compiled with imap support and php-imagick.
Tested succesfully with Roundcube 1.6.x and Nextcloud 30.x.
Downloads:
Enjoy 🙂
Latest version of the MKVToolnix package for Slackware (Sbo build), build on a Slackware-current 15.0+ system. Requires Qt5.
For Slackware-current x64:
You might run into interface issues with this version: the GUI could show partially hidden interface elements, fonts, checkboxes, …
See the next link for more info (GitLab bug report): https://gitlab.com/mbunkus/mkvtoolnix/-/issues/3358
Solution is to create an ENV variable:
QT_AUTO_SCREEN_SCALE_FACTOR=0
Put it somewhere in /etc/bashrc or the user’s .bashrc. That should fix the interface issues.
Enjoy 🙂
Update for Slackware x64: latest version of MariaDB 10.0. This package was build on a Slackware 14.1 system. To build this package succesfully on a 14.1 system, you also need to install the jemalloc package.
Downloads:
1. Start by downloading the 2 packages above.
2. Transfer these packages to the server you want to upgrade.
3. First install the jemalloc package:
installpkg jemalloc-3.6.0-x86_64-1.txz
4. Stop the running mysqld service:
/etc/rc.d/rc.mysqld stop
5. backup ALL your databases (make a copy of the entire /var/lib/mysql directory).
cp -a /var/lib/mysql/ /var/lib/mysql-BACKUP
6. Uninstall the MariaDB 5.5.x package (use removepkg or pkgtool).
7. Install the new MariaDB 10.0.25 package:
installpkg mariadb-10.0.25-x86_64-1.txz
8. Make sure /etc/rc.d/rc.mysqld is updated (overwrite the old rc.mysqld with rc.mysqld.new).
9. Start the mysqld service:
/etc/rc.d/rc.mysqld start
10. Check if mysqld is running now:
ps aux | grep mysql
11. Run mysql_secure_installation. Maybe this is not really necessary, but it doesn’t hurt to start clean. While you’re at it, you can set a new mysql root password here as well.
12. Run mysql_upgrade (MUST DO):
mysql_upgrade -u root -p
10. Restart the mysql service again (just to be sure).
/etc/rc.d/rc.mysqld restart
11. Now go check your DB’s and applications.
Enjoy 🙂
EDIT 27-Oct-2019: The above procedure is also valid when upgrading from say MariaDB 10.0 to 10.2 or later versions.
A new package for Slackware 14.1 x64:
Download here:
Enjoy 😉
Lately, I stumbled upon a minor but annoying issue with Samba on one of my file servers. There are no printers installed on this server, and probably never will be. However, smbd complains to no end in the client logfiles about not being able to connect to a CUPS server:
[david@Samba ~]$ head /var/log/samba.dfpc5 ... [2013/07/23 07:49:24.869727, 0] printing/print_cups.c:109(cups_connect) Unable to connect to CUPS server localhost:631 - Connection refused [2013/07/23 07:49:24.869790, 0] printing/print_cups.c:468(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL ...
All of the client logfiles were spammed continously by Samba with these lines. While this did not seem to harm the performance of the server, I wanted to ged rid of them. After all, I never configured this Samba server to use CUPS, so why the hell is it trying to find one ?
This file server runs Slackware Linux, and the Samba package provided by Slackware, is compiled with – – enable-cups (like it is on most distros). Consequently, unless you tell it otherwise, Samba uses CUPS as the default printing system and tries to connect to a local CUPS server. And if fails to do so, it starts spamming your log files . . .
There are several solutions to this problem:
I prefer the 1st solution. Just edit your smb.conf file, and look for the line that says “printing = cups”. Pay attention to the ; character at the front, which actually commnents out this line. You must remove the ; character.
; printing = cups printing = bsd
Save the file and restart the Samba service. Those pesky CUPS lines in your logfiles should be history.
© 2026 FreeUnix.davidleemans.be
Theme by Anders Noren — Up ↑