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.
Great to see so many interesting updates to the Slackware-current!
I had to update glade3 from the Slackware-current 3.8.5 to 3.18.3 that
now includes 'libgladeui', which is requested (to build) recent versions of anjuta,
gtksourceview3, libgda, libpeas, ...
Besides, I'd add devhelp (an API documentation browser for GTK+ and GNOME),
which is helpful ;-) for various GTK+ programs.
I had to update glade3 from the Slackware-current 3.8.5 to 3.18.3 that
now includes 'libgladeui', which is requested (to build) recent versions of anjuta,
gtksourceview3, libgda, libpeas, ...
the build scripts for all of these version bumps should be already available on my personal (and unofficial) repository for current.
BTW, small OT: nice photos you got on flickr, igor!
Eudev-3.1.5 works good. As a matter of fact, I've been using eudev for some time now without issue.
I haven't had the libudev.so.1 versus libudev.so.0 issue oddly, though in my Slackworks build I did link libudev.so to so.1 and so.0 equally, but nothing hiccupped.
With the standard rc scripts there is a little extra output, but nothing bad. OpenRC from SBo doesn't have any issues either.
If suggestions are still open, I suggest giving consideration to one further issue, namely whether to package as elilo-x86_64.efi not the pre-compiled binary supplied by the author of lilo, but the one compiled but discarded by elilo.SlackBuild. I realise why this is currently done - because elilo-ia32.efi cannot conveniently be compiled on a 64-bit machine - but the elilo package can provide the author's precompiled elilo-ia32.efi and the slackware compiled elilo-x86_64.efi. This would enable elilo-x86_64.efi to be signed. The pre-compiled one has been compiled by the author against too old a version of gnu-efi to enable it to be signed.
I agree this is of marginal utility given that slackware does not support secure boot out of the box, but providing for secure boot for slackware is relatively trivial for a user, and this would make it just a little easier.
proftpd 1.3.5a bugfix-release is out since a few months, disabling sslv3 among others.
Please consider adding "mod_sftp". Sftp is covered also by openssh, but with proftpd there would be the advantage of maintaining users in a file/db, instead of being forced to add system-users.
Wow, that is the most green I've seen on distrowatch in a long time (it's still a great reference to see how bleeding edge Slackware is, even if the metrics for measuring a distro's popularity based on page hits is questionable). There were two that stood out that look like they'd be problem-free updates (just based on the relatively small version change numbers).
Wow, that is the most green I've seen on distrowatch in a long time (it's still a great reference to see how bleeding edge Slackware is, even if the metrics for measuring a distro's popularity based on page hits is questionable). There were two that stood out that look like they'd be problem-free updates (just based on the relatively small version change numbers).
dhcpcd 4.3.2 -> 4.3.3
php 5.6.14 -> 5.6.15
The others, just for reference, are:
bash 4.3 -> 4.3.30
Everything else is green
I've reported the error in the bash version description to DistroWatch since -current now uses bash 4.3.042 which is the latest version/patch level.
I've reported the error in the bash version description to DistroWatch since -current now uses bash 4.3.042 which is the latest version/patch level.
That did seem a little strange to me considering all the bash updates we've had over the past year or so, but I didn't bother to do any digging. Thanks for the update!
EDIT: I'll shoot an email to them as well. Maybe multiple squeaks will get the wheel fixed.
Last edited by bassmadrigal; 11-16-2015 at 09:38 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.