LinuxQuestions.org - Requests for -current (14.2-->15.0)

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Requests for -current (14.2-->15.0) (https://www.linuxquestions.org/questions/slackware-14/requests-for-current-14-2-15-0-a-4175620463/)

Could to be useful the setup installer provides an option to change the resolution on high-dpi screens.
On 3840x2160 native resolution screen the installing process it's a bit painful.

Quote:

Originally Posted by simotrone (Post 5876549)

Could to be useful the setup installer provides an option to change the resolution on high-dpi screens.
On 3840x2160 native resolution screen the installing process it's a bit painful.

I had done something like that for the installer of Slint 14.1.

To try, get this old installer here:
http://slint.fr/installers/
File: http://slint.fr/installers/slint64-14.1.iso
md5sum: http://slint.fr/installers/slint64-14.1.iso.md5

Better try with EFI enabled.

Technically, the display is done in a framebuffer that the insaller sets to fit the screens dimensions in pixels, using fbterm. I assume that kmscon or mlterm could also be used but didn't try. If there is an interest I can help modifying the Slackware installer in a similar fashion.

PS the installer probes the hardware's ability for a proper display using this method and it this test fails uses the legacy display method with a fixed size font, thanks to Sébastien Ballet.

Thunderbird-52.9.1

A bug fix.

Tarball, https://ftp.mozilla.org/pub/thunderb....source.tar.xz

Apache and Lua:

If it would make it better, we could compile mod_lua as static, then there'd be no need to install lua at all.

In the slackbuild, before you configure apache:

Code:

tar xf lua-5.3.5.tar.gz -C /tmp/

( cd /tmp/lua-5.3.5; make linux local MYCFLAGS=-fPIC )



Add this to apache configure: --enable-lua=static --with-lua=/tmp/lua-5.3.5/install



make apache



clean up at end:

rm -rf /tmp/lua-5.3.5

Would that make it more acceptable?

bind-9.12.2 is released with security fixes.

Quote:

Security Fixes

When recursion is enabled but the allow-recursion and allow-query-cache ACLs are not specified, they should be limited to local networks, but they were inadvertently set to match the default allow-query, thus allowing remote queries. This flaw is disclosed in CVE-2018-5738. [GL #309]

The serve-stale feature could cause an assertion failure in rbtdb.c even when stale-answer-enable was false. The simultaneous use of stale cache records and NSEC aggressive negative caching could trigger a recursion loop in the named process. This flaw is disclosed in CVE-2018-5737. [GL #185]

A bug in zone database reference counting could lead to a crash when multiple versions of a slave zone were transferred from a master in close succession. This flaw is disclosed in CVE-2018-5736. [GL #134]

--purge option in removepkg

Sometimes it is convenient to get rid of the *.new" files when removing a package:

Code:

--- removepkg.orig        2018-07-10 08:56:00.000000000 +0000

+++ removepkg        2018-07-11 13:14:57.721975028 +0000

@@ -342,6 +342,21 @@

    fi

    sed -n "/$TRIGGER/,/^$/p" < $ADM_DIR/packages/$PKGNAME | \

    fgrep -v "FILE LIST:" | sort -u > $TMP/delete_list$$

+  if [ "$PURGE" = true ]; then

+    if grep "\.new$" $TMP/delete_list$$ > $TMP/new_files_list$$ 2> /dev/null ; then

+    for NF in $(cat $TMP/new_files_list$$) ; do

+      CF="$(dirname "$NF")/$(basename "$NF" .new)"

+      if [ -r "$ROOT/$CF" ] ; then

+      grep -q "$NF" $ADM_DIR/scripts/$PKGNAME 2> /dev/null && echo "$CF" >> $TMP/cfg_files_list$$

+      fi

+    done

+    if [ -r $TMP/cfg_files_list$$ ] ; then

+      mv $TMP/delete_list$$ $TMP/delete_list$$.$$

+      cat $TMP/delete_list$$.$$ $TMP/cfg_files_list$$ | sort -u > $TMP/delete_list$$

+      rm -f $TMP/delete_list$$.$$ $TMP/cfg_files_list$$ $TMP/new_files_list$$

+    fi

+    fi

+  fi

    # Pat's new-new && improved pre-removal routine.

    cat_except $ADM_DIR/packages $PKGNAME | sort -u > $TMP/required_list$$

    if [ -r $ADM_DIR/scripts/$PKGNAME ]; then

@@ -415,7 +430,8 @@

  -preserve | --preserve) PRESERVE=true; shift;;

  -terse | --terse) TERSE=0; shift;;

  -warn | --warn) WARN=true; shift;;

-  -* | --*) echo "Usage: $(basename $0) [-copy] [-keep] [-preserve] [-warn] packagename ..."; exit 1;;

+  -purge | --purge) PURGE=true; shift;;

+  -* | --*) echo "Usage: $(basename $0) [-copy] [-keep] [-preserve] [-warn] [-purge] packagename ..."; exit 1;;

  *) break

  esac

 done

Cheers

Useless post, sorry.

Hi,

I'm just curious to know why an unstable/developpement bind version is now included in current instead of last stable 9.12.2 or last LTS stable 9.11.4 (see attachment).

Quote:

Thu Jul 12 01:50:07 UTC 2018
(…)
n/bind-9.13.2-x86_64-1.txz: Upgraded.
This update fixes security issues:
Fixed a bug where extraordinarily large zone transfers caused several
problems, with possible outcomes including corrupted journal files or
server exit due to assertion failure.
Don't permit recursive query service to unauthorized clients.
For more information, see:
https://cve.mitre.org/cgi-bin/cvenam...=CVE-2018-5738
(* Security fix *)

Is there a good reason I missed ?

I'm pretty sure that by the time Slackware 15.0 gets released, next stable will be used and 9.12.x branch will be close to EOL or even EOL'ed