site  contact  subhomenews

Easy Pyro version 1.2 released

August 25, 2019 — BarryK

Version 1.1.1 was supposed to be the EOL (End Of Line) for the Pyro series, superceded by the Buster series. Buster version 2.1 will be announced later today.

I am fond of the Pyro series, and have decided to keep it going, though it will likely only be the occasional maintenance release. Here is an announcement blurb for 1.2:

At the time of writing, Easy Buster 2.1 is being released. Although the Buster series is intended to receive most attention ongoing, Barry decided to keep doing maintenance releases of the Pyro series.

Although the package versions, such as gcc, glibc and libraries, are starting to get a bit "long in the tooth", Barry retains a fondness for them due to the very small size and targeted configuration. That is, the packages were compiled from source, using 'oe-qky-src', a fork of OpenEmbedded, so there are no unwanted dependencies, meaning no bloat.

Consider, the 'easy-1.2-amd64.img.gz' download file is 418MB. This includes the "kitchen sink" of applications, both GTK2, GTK3 and Qt5 based apps. On the other-hand, Buster 'easy-2.1-amd64.img.gz' is 504MB and has less apps -- Qt5 libraries and apps such as Scribus (desktop publisher) were left out, to limit the size.

Yes, Buster works, and has the advantage of access to the huge Debian package respositories (which was the main reason to go for it). However, small size, and the seamless integration off all packages, are the arguments in favour of Pyro. Pyro has a much smaller on-line app repository.

Version 1.2 has a kernel bump to 5.2.9, some bug fixes, infrastructure improvements, and the new "Copy session to RAM & disable drives" boot option.

More detailed release notes are here:

It is recommended also to read the "readme" file here:


...note, there are German, French and English builds.


Feedback is welcome, at this forum thread:

Known bugs and issues:

There is one tiny bug in the initrd, fixing of GTK theming when SFS layers change. Non-critical and will be fixed in the next release.

When testing 1.2, one of my USB Flash sticks decided to become corrupted, resulting in a failure to boot. I intend to address the situation of a faulty Flash drive, as it is not just old drives, even new very cheap sticks can be faulty. Firstly, I propose to put some testing into the EasyDD utility. 

Tags: easy