OpenJDK11 has been added to my repository

For ages, I have had Java 7 and Java 8 packages in my repository. I compile these versions of Java from the OpenJDK sources and using the icedtea framework.

People have been asking about more recent versions of Java, in particular Java 11 and Java 17 are required more and more by software projects. So far, I have been hesitant, since icedtea still only supports Java 7 and 8. Writing a new build script from scratch is a lot of work and Java gives little reward.

Eventually, I have decided to build Java 11 packages regardless, main reason being that LibreOffice seems to need it to enable functionality in Base. Therefore expect the next update of my LibreOffice packages to have been compiled against OpenJDK11.

Note that I will not be creating separate JRE (Java Runtime Environment) packages. The JDK (Java Development Kit) is what you’ll get from me. It contains everything you need to compile and run Java programs. Don’t forget to logout and login again after installing openjdk11, since it installs a profile script which is sourced during login.

Packages are on slackware.com or on my NL or US mirror.

I took some inspiration from the SBo script maintained by Lenard Spencer, to save time, but in the end my script ended up quite different. I credited Lenard in my own script though.

$ java -version
openjdk version "11.0.16" 2022-07-19
OpenJDK Runtime Environment (build 11.0.16+8)
OpenJDK 64-Bit Server VM (build 11.0.16+8, mixed mode)
$ javac -version
javac 11.0.16

Now let’s see if I can stay op top of security updates… Andrew Hughes has been doing a stellar job of informing me about the icedtea releases that prompted me to update my openjdk/openjre packages.

Libre Office 7.3.5 and updates for Chromium 103 (also -ungoogled)

LibreOffice Community Edition 7.3.5 was released last week. The Document Foundation blog has the news on it.
The 7.3.x releases are the bleeding edge of this popular office suite but nevertheless really stable software. Libre Office 7.4.0 is right along the corner (expected release is mid-august) but I might hold out on that first release.

The new package set for libreoffice-7.3.5 (for Slackware 15.0 and -current) can be downloaded from my repository.
Note that I compiled them on Slackware 15.0 so if you install them on Slackware -current you will also need to install ‘icu4c-compat‘ and boost-compat. These are other packages in my repository; they contain older versions of the icu4c and boost libraries, in particular the versions that are part of Slackware 15.0 but no longer part of -current.

Get libreoffice packages from my own Europe-based server: https://slackware.nl/people/alien/slackbuilds/libreoffice/ or my US-based server: https://us.slackware.nl/people/alien/slackbuilds/libreoffice/ ;or any mirror if you wait a day, for instance https://slackware.uk/people/alien/slackbuilds/libreoffice/ .
These servers all offer rsync access if you prefer that to http.

 

I wrestled with the Chromium 103 updates. Most frustrating program to build, ever, considering the time it takes to compile a package and the fast release cycle.
Here’s the heads-up: I have an incremental update both for regular and un-googled Chromium 103, but only after I finally gave up on compiling the 32bit chromium-ungoogled package. The compiler just keeps on segfaulting.

Google’s announcement last week of the 103.0.5060.134 release mentions a couple of vulnerabilities with a security level of ‘high’, so again it’s recommended to upgrade. This release kept my build box busy for several days but with VLC and LibreOffice packages waiting to be built and seeing the chromium-ungoogled compilation fail 4 times in a row at different stages, I had to decide skipping the 32bit chromium-ungoogled package this time. Let’s hope I have better luck next time.
The updated packages for chromium and chromium-ungoogled are available for Slackware 14.2 and newer. I will try to keep supporting Slackware 14.2 for as long as I can.

The packages can be downloaded from the usual places like http://www.slackware.com/~alien/slackbuilds/ , http://slackware.nl/people/alien/slackbuilds/ , http://us.slackware.nl/people/alien/slackbuilds/ or http://slackware.uk/people/alien/slackbuilds/ .

Enjoy – Eric

Finally a new batch of Live ISOs for Slackware-current (liveslak-1.5.3)

Updates in liveslak

Time flies. The last batch-release of Slackware Live ISO’s was almost 7 months ago.
I was burnt up by the time 2021 turned into 2022 and it took a long time for me to enjoy working on my projects again (and it’s still difficult), but I thought it might be appreciated to at least have a fresh set of ISOs for the Slackware Live Edition to play with during summer holidays.

It’s of course not entirely correct that there were no new ISOs for seven months… I have an automated process in place which re-creates a Live ISO of Slackware64-current every time there is an update to the ChangeLog.txt. It is meant to test every update and find issues to fix. There’s a European and a USA URL to download this ISO.

The various small issues that popped as a result software updates in Slackware-current, were fixed in the liveslak sources during these past months, and thanks to the people who reported to me the issues that they encountered!
These fixes went into ‘silent’ liveslak releases that were not mentioned in blog posts or other forms of communication: 1.5.1.5 to accompany the release of Slackware 15.0 (I tagged this to create the original Live ISO for Slackware 15.0) and then 1.5.2 was tagged a short while later to fix a few glaring errors in 1.5.1.5. Finally the 1.5.2 tag was meant to release a batch of ISOs in May, but I did not have the energy.

I now have tagged a liveslak-1.5.3 release with the latest updates.
Most important change in liveslak is that I decided to abandon the CDROM capacity limit (703 MB) of the XFCE ISO image size. This size limitation ensured that there would always be a version of Slackware Live Edition that you could burn to a good old CDROM medium.
What was the reason for this change of mind? When I generated a XFCE ISO last week, it was significantly larger than the 703 MB physical CDROM capacity, and I realized that I could not trim the ISO back to below 703 MB. There was simply no way to keep removing packages (read: functionality) from that ISO without penalty.
I do want the XFCE ISO to be functional and useful, so I decided on a new (somewhat arbitrary) size limitation for XFCE ISO, which is 1000 MB. It allowed me to add (back) a bunch of useful programs, most prominently Seamonkey is now gone, and it has been replaced by Firefox. If you have a need for yet more useful Slackware utilities that are missing from the XFCE ISO, leave a comment below.
If there is an interest, I may consider releasing a console-only Slackware Live ISO, which will again be a lot smaller than 700 MB and therefore able to be burnt to a CDROM. Basically this will be the standalone version of “Core OS” which you can already find in the boot menus of the DAW, LEAN and XFCE variants. Let me know your thoughts in the comments section!

The new liveslak also introduces an intermediate form of trimming the ISO content (I trim some ISOs to reduce size). Where before you’d have three increasingly severe forms of trimming “doc“, “mandoc” and “bloat“, there is now an additional form “waste” and its trimming effect lies somewhere between that of “mandoc” and “bloat“. The “waste” form of trimming is now applied to XFCE ISO instead of the old “bloat” form, and this leaves alot of libraries (dynamic and static) in the ISO image, which should make it more functional even.

The new ISOs are available for download at the usual locations (see below for download URLs). You’ll find SLACKWARE (32bit/64bit), XFCE (32bit/64bit), DAW, LEAN, CINNAMON and MATE updated images. I refreshed the ‘bonus’ section with nvidia and broadcom-sta live-modules that contain kernel drivers matching the installed kernel; I also updated the multilib and wine modules and other useful stuff.

Slackware LEAN Live

A note about ISO sizes

Over time, the functionality of the Slackware distro has been expanding. More programs were added, and package sizes have been increasing (I barely know software developers that remove functionality – everybody just keeps adding stuff) . The ISO image for the full and unmodified Slackware is almost equal to the capacity of a physical DVD. The difference is only 30 Megabytes! This means, I will soon have to start trimming the Slackware Live ISO to stay below DVD capacity limit. That is unsettling and goes against what I think does justice to the distro. On the other hand, I assume that some people’s first experience with Slackware comes from burning a Live ISO to a DVD medium and booting their computer from the DVD.
Here as well, your thoughts are welcome: should I apply trim like with the XFCE ISO, or should I be selective in the package series that I add to the Live ISO?

Download Slackware Live Edition

You can find a set of new ISOs based on liveslak on my own servers: download.liveslak.org/latest/ in the Netherlands, or the US host us.liveslak.org/latest/ .
Note: all 64bit versions support Secure Boot.

Some people report that the ISO images won’t boot when copied (using ‘cp’ or ‘dd’ for instance) to a USB stick but they all boot properly if you use the ‘iso2usb.sh‘ script provided with liveslak to transfer the ISO content to a USB stick. Of course, this will give you nice persistent storage of all your modifications with optional data encryption, ideal for a secure on-the-road Slackware environment.

Get liveslak sources

The liveslak project is hosted in git. Its browsable cgit interface is here: https://git.liveslak.org/liveslak/

A set of the liveslak scripts can also be downloaded from http://www.slackware.com/~alien/liveslak/ or https://slackware.nl/people/alien/liveslak/

Remember Secure Boot

All 64bit ISOs are able to boot on a computer with SecureBoot enabled. You’ll need to enroll the liveslak public key (a SSL certificate in DER encoding format with the filename ‘liveslak.der‘) into such a computer during the very first boot. That certificate file can be found in the EFI partition inside the ISO image or on the USB stick you produced. It can also be downloaded from https://download.liveslak.org/secureboot/liveslak.der if you want. This DER certificate does not change when new ISO’s are released, so an updated ISO should boot normally on your SecureBoot-enabled system using the stored version of the ‘liveslak.der’ certificate which you enrolled in the past.

Cheers, Eric

Chromium 103 (regular and ungoogled) available as Slackware package

Apologies for the delay, I was out of town, but i have finally uploaded my new chromium 103 packages for Slackware 14.2 and newer. Their un-googled siblings are also available. Thanks as always to Eloston and his friends for updating the patch-set for ungoogled-chromium.
Last week saw a Google Chromium update which addresses a series of vulnerabilities, which is nothing new of course, but in particular one security hole that has now been patched would allow remote attackers to take control of your computer and execute arbitrary code. See CVE-2022-2156. An update of your installed browser package seems in order.

You can find the Chromium packages (version 103.0.5060.53) at the usual places: my own repositories of course (or any mirror):

Links to the un-googled chromium:

As stated at the beginning of the article: these packages work on Slackware 14.2 and newer. You can download 32bit as well as 64bit variants.

Enjoy! Eric

Chromium 102 (regular and ungoogled) for 64bit Slackware

Google has released the sources for Chromium 102.0.5005.61. The release notes mention 32 security fixes. One of those (CVE-2022-1853) is listed as ‘critical’ and supposedly an attacker can craft a website in such a way that if you visit that URL, the attacker can compromise or take over your local computer. No clicking required.

And again it proves to be quite hard to compile 32bit packages for the new Chromium.
The Google developers create new hurdles almost every major release in their ‘assumption’ that there is no 32bit Linux out there that they should support. I am still working out what I need to fix/patch.

Therefore you can only get 64bit chromium packages here (NL mirror) or here (US mirror). Likewise the chromium-ungoogled packages (64bit only) are found here (NL mirror) or here (US mirror).

Cheers, Eric