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 not a request, just a suggestion (well, actually two suggestions).
That Slackware 15.0 doesn't appear on the horizon makes more people complain about hardware support, like e.g. NVMe, eMMC or support of new laptops.
Maybe provide an "intermediate" stable ISO shipping part[1] of the updated scripts in the installer, a recent kernel 4.19.n, and the same packages as in 14.2, but with all updates that appeared since then in the stable ChangeLog also applied, which would avoid new users to replace a lot of packages just after having installed.
This would imply to upgrade the kernel for 14.2 to the same version shipped in the installer at the same time as releasing the ISO. I could of course miss something but I do not expect issues doing that. At least I didn't find any since releasing Slint64-14.2.1.2 nearly two months ago, shipping the kernels 4.19.30 from Slackware-current.
Just my two ¢.
[1] Not changing the location of the packages database.
Last edited by Didier Spaier; 05-16-2019 at 05:45 PM.
2019-05-14 22:26 Christos Zoulas
* release 5.37
2019-05-09 22:27 Christos Zoulas
* Make sure that continuation separators are printed
with -k within softmagic
2019-05-06 22:27 Christos Zoulas
* Change SIGPIPE saving and restoring during compression to use
sigaction(2) instead of signal(3) and cache it. (Denys Vlasenko)
* Cache stat(2) calls more to reduce number of calls (Denys Vlasenko)
2019-05-06 17:25 Christos Zoulas
* PR/77: Handle --mime-type and -k correctly.
2019-05-03 15:26 Christos Zoulas <christos@zoulas.com>
* Switch decompression code to use vfork() because
tools like rpmdiff and rpmbuild call libmagic
with large process footprints (Denys Vlasenko)
2019-04-07 14:05 Christos Zoulas
* PR/75: --enable-zlib, did not work.
2019-02-27 11:54 Christos Zoulas
* Improve regex efficiency (Michael Schroeder) by:
1. Prefixing regex searches with regular search
for keywords where possible
2. Using memmem(3) where available
Last edited by mats_b_tegner; 05-17-2019 at 05:01 AM.
The CVEs mentioned in those release notes were actually fixed in bind-9.14.1.
You're absolutely right Pat, this release-notes is regarding all 9.14 branch, the correct file for changes for this new version is this: https://ftp.isc.org/isc/bind9/9.14.2/CHANGES where there are only some bug fixes. My bad should have checked *CHANGES* file.
Quote:
--- 9.14.2 released ---
5233. [bug] Negative trust anchors did not work with "forward only;"
to validating resolvers. [GL #997]
5231. [protocol] Add support for displaying CLIENT-TAG and SERVER-TAG.
[GL #960]
5229. [protocol] Enforce known SSHFP fingerprint lengths. [GL #852]
5228. [cleanup] If trusted-keys and managed-keys are configured
simultaneously for the same name, the key cannot
be rolled automatically. This configuration now
logs a warning. [GL #868]
5224. [bug] Only test provide-ixfr on TCP streams. [GL #991]
5223. [bug] Fixed a race in the filter-aaaa plugin accessing
the hash table. [GL #1005]
5222. [bug] 'delv -t ANY' could leak memory. [GL #983]
5221. [test] Enable parallel execution of system tests on
Windows. [GL !4101]
5220. [cleanup] Refactor the isc_stat structure to take advantage
of stdatomic. [GL !1493]
5219. [bug] Fixed a race in the filter-aaaa plugin that could
trigger a crash when returning an instance object
to the memory pool. [GL #982]
5218. [bug] Conditionally include <dlfcn.h>. [GL #995]
5217. [bug] Restore key id calculation for RSAMD5. [GL #996]
5215. [bug] Change #5124 was incomplete; named could still
return FORMERR instead of SERVFAIL in some cases.
[GL #990]
5214. [bug] win32: named now removes its lock file upon shutdown.
[GL #979]
5213. [bug] win32: Eliminated a race which allowed named.exe running
as a service to be killed prematurely during shutdown.
[GL #978]
5211. [bug] Allow out-of-zone additional data to be included
in authoritative responses if recursion is allowed
and "minimal-responses" is disabled. This behavior
was inadvertently removed in change #4605. [GL #817]
5210. [bug] When dnstap is enabled and recursion is not
available, incoming queries are now logged
as "auth". Previously, this depended on whether
recursion was requested by the client, not on
whether recursion was available. [GL #963]
5209. [bug] When update-check-ksk is true, add_sigs was not
considering offline keys, leaving record sets signed
with the incorrect type key. [GL #763]
5208. [test] Run valid rdata wire encodings through totext+fromtext
and tofmttext+fromtext methods to check these methods.
[GL #899]
5207. [test] Check delv and dig TTL values. [GL #965]
5206. [bug] Delv could print out bad TTLs. [GL #965]
5205. [bug] Enforce that a DS hash exists. [GL #899]
5204. [test] Check that dns_rdata_fromtext() produces a record that
will be accepted by dns_rdata_fromwire(). [GL #852]
5203. [bug] Enforce whether key rdata exists or not in KEY,
DNSKEY, CDNSKEY and RKEY. [GL #899]
5202. [bug] <dns/ecs.h> was missing ISC_LANG_ENDDECLS. [GL #976]
5190. [bug] Ignore trust anchors using disabled algorithms.
[GL #806]
Just FYI, these are probably not going not make it in -current since they are part of the 4.13.x (odd) release. Once they reach 4.14.x (even) PV will probably upgrade them instead of just the patch level upgrades.
This is not a request, just a suggestion (well, actually two suggestions).
That Slackware 15.0 doesn't appear on the horizon makes more people complain about hardware support, like e.g. NVMe, eMMC or support of new laptops.
Maybe provide an "intermediate" stable ISO shipping part[1] of the updated scripts in the installer, a recent kernel 4.19.n, and the same packages as in 14.2, but with all updates that appeared since then in the stable ChangeLog also applied, which would avoid new users to replace a lot of packages just after having installed.
This would imply to upgrade the kernel for 14.2 to the same version shipped in the installer at the same time as releasing the ISO. I could of course miss something but I do not expect issues doing that. At least I didn't find any since releasing Slint64-14.2.1.2 nearly two months ago, shipping the kernels 4.19.30 from Slackware-current.
Just my two ¢.
[1] Not changing the location of the packages database.
would be very nice to hear an actual comment from Patrick about this.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
