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.
Already queued up here, but it's nice to see users figure out what we think is the right way to do things :-)
EDIT: Hmm, after checking what I had queued up, I see that you were *more* correct -- I'd hastily identified the 70-uaccess.rules file as the culprit and blacklisted it. Fixed now - thanks!!
I'd like to add my support for the python bindings - at the very least for python3.
According to the opencv people, it's not possible to build them separately later against an existing opencv-core (which may have been a good SBo SlackBuild). There was mention of a project producing python wheels but it seems to generate a new private version of opencv-core.
Adding the above lines for python support has worked in the SBo SlackBuild for a long time with no complaints i.e. tried & proven. Also, it is the mechanism instituted (& presumably recommended) by the opencv devs themselves. I've tried it in -current's 4.5.0 version and it works fine.
NVMe temperature monitoring from HWMON was introduced in kernel 5.5. If possible would you add NVMe hardware monitoring support in the next 5.10.x kernel. I just got done testing it and it works. However for it to work there needs to be a small change to the kernel config. I will post links to what I did to make it work
Question (possibly a request) for `slackpkg check-updates`, the man page says:
But the return value always seems to be zero (whether there are updates or not). How is it meant to be used in a script?
"slackpkg check-updates" will create file ~/.slackpkg/updated-repos.txt. This file is empty if there is no update in repo or it will contain the list of repositories with updates (it works with slackpkg+ so you can have more than one repository updated).
You can use it in crontab of your user (no need to be root) to send notification when a repository is updated.
Code:
$ crontab -l
SHELL=/bin/bash
# Check update of Slackware packages
#0 * * * * export DISPLAY=:0 && /usr/sbin/slackpkg &>/dev/null check-updates && [ -s ~/.slackpkg/updated-repos.txt ] && DBUS_SESSION_BUS_ADDRESS=$(ps -u chris e | grep -Eo 'dbus-daemon.*ADDRESS=unix:abstract=/tmp/dbus-[A-Za-z0-9]{10}' | tail -c35) /usr/bin/notify-send -i dialog-warning "[ S L A C K P K G + ]" "Available updates in repositories: $(cat ~/.slackpkg/updated-repos.txt|tr '\n' ','|sed 's/,$//' )"
0 * * * * sh $HOME/data/script/check_slackware_update.sh
The one-liner is commented out but works in all DE while the script works only with Plasma 5. The difficulty (at least for me) was to find a way to get value of DBUS_SESSION_BUS_ADDRESS (needed for notify-send) in the cron context. I found the solution looking around in various sites. It surely can be improved but it would be better to discuss that in a separate thread.
Code:
$ cat $HOME/data/script/check_slackware_update.sh
#!/bin/bash
/usr/sbin/slackpkg &>/dev/null check-updates
username=$(/usr/bin/whoami)
pid=$(pgrep -u $username kded5)
dbus=$(grep -z DBUS_SESSION_BUS_ADDRESS /proc/$pid/environ | sed 's/DBUS_SESSION_BUS_ADDRESS=//')
export DBUS_SESSION_BUS_ADDRESS=$dbus
[ -s ~/.slackpkg/updated-repos.txt ] && /usr/bin/notify-send -i dialog-warning "[ S L A C K P K G + ]" "Available updates in repositories: $(cat ~/.slackpkg/updated-repos.txt|tr '\n' ','|sed 's/,$//')"
[EDIT] file ~/.slackpkg/updated-repos.txt is part of slackpkg+ and not of the stock slackpkg. See this post
Last edited by gegechris99; 12-20-2020 at 04:36 AM.
Reason: updated-repos.txt is not part of stock slackpkg
slacktrack depends the executable-bit of a given script, e.g. to as part of the linux-docutils build.
Depending on the mirror used, executable-bits get lost when synct via rsync, e.g. from mirrors.kernel.org/slackware/slackware64-current/source/
Following does fix this:
Code:
--- slacktrack.orig 2020-12-20 10:52:10.880107851 +0100
+++ slacktrack 2020-12-20 10:52:28.386507648 +0100
@@ -674,7 +674,7 @@
if [ "${LOGGING}" = "Yes" ]; then
[ -x /usr/libexec/slacktrack/ln ] && export PATH=/usr/libexec/slacktrack:$PATH
( printf "\n\n\n[$( date "+%D %r" )] ${PROGNAME}: Executing command line '${COMMANDLINESCRIPT}'\n\n"
- ${COMMANDLINESCRIPT}
+ sh ${COMMANDLINESCRIPT}
EXIT_CODE=$?
if [ ${EXIT_CODE} -gt 0 ]; then
printf "\n\n[$( date "+%D %r" )] ${PROGNAME}: * WARNING: ${COMMANDLINESCRIPT} returned exit code ${EXIT_CODE} *\n\n"
linux-docutils.SlackBuild would need this in addition
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
