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.
Add --enable-assert configure option.
Use pkg-config to check for libraries presence.
Do not limit --secure-protocol=auto|pfs to TLSv1.0.
Add --secure-protocol=TLSv1_1|TLSv1_2 .
Full C89 source code compliance.
Select and use the most secure authentication scheme with HTTP connections.
Fix issues with turkish locales.
Handle 504 Gateway Timeout.
New option --crl-file to load Certificate Revocation Lists.
Add valgrind support to tests suite.
Fix an off-by-one problem in the progress bar (introduced in 1.16.1).
Also seems to fix an issue I had with 1.16 that couldn't find the openssl libraries on Slack64-14.1.
It'd be nice if we had both Python 2.x and 3.x available on the installation media. Yes, I know you can get 3.x from SBo (that's what I'm doing right now). Also, I know there was another thread for requests like this, but I can't find it right now.
I don't mind Python 3 staying on SBo, the maintainer is doing a good job with it. The Slackware team already has enough moving targets to tackle. Just my two cents.
Just thought of this since it was mentioned in another topic.
Edit the HPLIP Slackbuild to remove the unneeded systemd unit file and directory.
As for Python 3, I say toss a coin and call it heads or tails.
Now a good question... Driver support. I think Patrick deals with the kernel but has there been any drivers that may need to be checked and included with the kernel not currently supported that might be beneficial?
When I try to open an iso file with the slackware version of mc (4.8.10) folder and file names are missing the last letter of the filename and when I go into any of the folders they are empty.
Are you able to open ISO files with mc 4.8.10 and read or copy files within?
Are you able to open ISO files with mc 4.8.10 and read or copy files within?
Yes. Works fine here with 14.1 and mc-4.8.10. Tested with Slackware, Slint, Salix, Porteus, FreeBSD, PCBSD and Tails ISO images. I suggest you open a new thread for this problem.
It has been said in a few posts, but I also would like to see procps upgraded for procps-ng. Since procsp is packaged with psinfo and psmisc, it would be nice to see psinfo upgraded to psinfo-ng. I updated procps to procps-ng on my slackware64 machine because the newer sysctl uses /etc/sysctl.d directory in its path.
Some packages on SBo put files into /etc/sysctl.d and aren't activated unless they are put into the /etc/sysctl.conf file or manually added by setting something up in /etc/rc.d/rc.local (or update /etc/rc.d/rc.S). For example, libvirtd puts a sysctl file in /etc/sysctl.d/libvirtd.conf. Upgrading just saves me the time rather than remembering to run it manually. I also had to update /etc/rc.d/rc.S to account for this.
It has been said in a few posts, but I also would like to see procps upgraded for procps-ng. Since procsp is packaged with psinfo and psmisc, it would be nice to see psinfo upgraded to psinfo-ng. I updated procps to procps-ng on my slackware64 machine because the newer sysctl uses /etc/sysctl.d directory in its path.
Some packages on SBo put files into /etc/sysctl.d and aren't activated unless they are put into the /etc/sysctl.conf file or manually added by setting something up in /etc/rc.d/rc.local (or update /etc/rc.d/rc.S). For example, libvirtd puts a sysctl file in /etc/sysctl.d/libvirtd.conf. Upgrading just saves me the time rather than remembering to run it manually. I also had to update /etc/rc.d/rc.S to account for this.
Yes, and splitting procps and psmisc into separate packages might be good also.
When I try to open an iso file with the slackware version of mc (4.8.10) folder and file names are missing the last letter of the filename and when I go into any of the folders they are empty.
Are you able to open ISO files with mc 4.8.10 and read or copy files within?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.