site  contact  subhomenews

Using Easy Containers page updated

September 13, 2019 — BarryK

I started this page of usage notes for Easy Containers a little while ago, today updated:

To work as documented in that web page, requires Easy Pyro 1.2.3 and Easy Buster 2.1.3, neither of which are released. I am working on a few things, and they should be released in a couple of days. 

Tags: easy

PupRadio fixed

September 12, 2019 — BarryK

Rodney reported that Pupradio (see Multimedia menu) failed to start in Easy Buster.

The problem was caused by /usr/local/bin/defaultmediaplayer having "gnomempvshell" in it. OK, fixed, and the PET is now version 0.21.

There is still a problem with Pupradio and PupTelly: some of the URIs don't work. That is something that someone will have to go through and find replacements. If you undertake that, let me know and I will put the URI fixes into the PET. 

Tags: easy

Easy Pyro 1.2.2 released

September 12, 2019 — BarryK

This is a maintenance release in the EasyOS "Pyro" series, that have version numbers 1.x. Most attention is now on the "Buster" series, version numbers 2.x, however, it is anticipated that there will be more releases of the Pyro series, mostly just updating the infrastructure.

As Easy Pyro is built with woofQ, same as for Easy Buster, all infrastructure improvements will apply to both series. So, the release notes for the latest Buster also apply to Pyro, that is, anything infrastructure-related and not package-specific:

Easy Buster version 2.1.2 will be released soon, and will have some infrastructure improvements that are in Pyro 1.2.2.

Regarding packages, relative to Pyro 1.2, the kernel has been bumped from 5.2.9 to 5.2.10, and SeaMonkey from 2.49.4 to 2.49.5.

This is the download site, and includes German and French builds:

One thing that you will notice after booting 1.2.2, is a slight change on the desktop (snapshot taken on a 1024x768 monitor):


...the label "file" at top-left is now "home", and the label for running EasyOS as a complete-desktop-in-a-container, was "easy", now "pyro".

The reason for the latter change is to avoid having two icons on the screen having the label "easy". I am planning to post some more documentation on using containers, but briefly, if you are currently running Pyro, you can also run Buster in a container -- so the Pyro icon will be labeled "pyro" and the Buster icon will be labeled "buster". 

Important upgrade notice

EDIT 20190916:
The problem described below has been fixed in EasyOS versions 1.2.3 and 2.1.3. The fix will occur automatically.

I have Easy Pyro installed on the SSD in my Mele mini-PC, and I upgraded by the simple method of replacing the three files 'vmlinuz', 'initrd' and 'easy.sfs' in the boot-partition, and of course clicking on 'initrd' to "fix" it, as described here:

I discovered that the desktop has two icons on top of each other, labelled "easy" and "pyro". This is a problem due to the name change. I could put in hack-code to fix it, however, it is a "one off" upgrade problem, and it is simpler just to give some instructions for a manual fix.

EasyOS still has a small number of users, and even smaller who have an installation that they would want to upgrade -- most users are, I think, just writing a Flash-stick with the new version and starting from scratch.

So, here is how to perform this one-off fix:

  1. Drag the icon labeled "pyro" off the other one, right-click on it and choose "Remove item".
  2. Right-click on the "easy" icon, choose "Edit item" and change "/usr/sbin/ec-chroot-easy" to "/usr/sbin/ec-chroot-pyro", and change the displayed text from "easy" to "pyro".
  3. Delete the script /usr/sbin/ec-chroot-easy
  4. Change the name of the folder '/mnt/wkg/containers/easy' to 'pyro'.
  5. Open /mnt/wkg/containers/pyro/desktop in a text editor and change "EC_LABEL=easy" to "EC_LABEL=pyro" and "EC_PATH=/usr/sbin/ec-chroot-easy" to "EC_PATH=/usr/sbin/ec-chroot-pyro".

 That's it, you are good-to-go. If you click on the "pyro" desktop icon, the complete desktop-in-container should launch. 

Note, an alternative to those five steps is simply to erase the working session. That will delete browser history, bookmarks, installed packages, etc (but won't affect containers or anything in /home). In the menu Filesystem -> Easy Version Control, click the "Erase the working session" button. 

Tags: easy

Compile system for SeaMonkey 2.49.5

September 10, 2019 — BarryK

I reported on the journey to get the latest SeaMonkey to compile:

I have successfully compiled SM for Easy Buster and Pyro, and created PETs. It is based upon the work done by Slackware developer guys.

The main reason that it wasn't compiling for me earlier, was that I was trying to use the "cairo-gtk2" backend, however, only "cairo-gtk3" works. It looks like the end of an era. No one has bothered to get the bugs out of the "cairo-gtk2" build.

The Slackware build is configured with most libraries builtin, rather than using system libraries, such as icu, jpeg, libevent, etc. I have changed to use system libraries as much as possible, except for sqlite and png -- those two need the inbuilt versions, at least that used to be the case. The end result is considerably smaller than the Slackware build.

Note, it also used to be that SM needed the inbuilt icu, otherwise it was unstable. However, I compiled with the system icu and tested on various sites and it is stable. Didn't test with non-English $LANG though.

There was a problem with the build on Easy Buster, the install step "make -f install" failed. So, I put in crude manual install code, which does not create the 'omni.ja' file. This is a zip archive that has all of the 'chrome' and 'components' folders, which is supposed to improve operation speed. I emphasize "supposed to".

Anyway, there is an install to /usr/lib/seamonkey-2.49.5, and on Puppy-like systems if you change the /usr/lib/seamonkey symlink and maybe the /usr/bin/seamonkey symlink, you are good-to-go.

Here is the build system and SM source: need to expand the 'seamonkey-build' tarball and put the SM source tarball inside it. Then run the script. 

Tags: easy

SeaMonkey 2.49.5 released

September 07, 2019 — BarryK

Yay, finally! Version 2.49.4 was released in July 2018, so this version has been a long time coming:

However, I am unable to compile it. Got configure errors when tried to use system 'nspr' and 'nss', so chose internal libs, but then got compile errors.

I will wait until the Linux From Scratch people figure it out. 

EDIT 2019-09-09:
The LFS guys have posted instructions:

However, compile still fails for me. Then I tried patches from Fedora. This shows the patches to be applied:

And the patches are available from here:

Nup, still fails for me.

Then I looked at how the Slackware guys are doing it. I downloaded everything here:

Made a couple of modifications to 'seamonkey.SlackBuild' script -- disabled rust, changed $TMP to /tmp2, as /tmp is a tmpfs and not big enough. Yay, it compiled ...but install failed.

This is a starting point, a successful compile, that I can hack on. Some of the configure options need to be changed. 

Tags: easy

Setting default path for Open and Save dialogs in Inkscape

September 07, 2019 — BarryK

In EasyOS, I want the Open|Save|Download dialog boxes to default to '/home' or some folder under '/home', not '/root'. The current directory before X starts, is set to '/home', which is good enough for most apps. But not all.

I reported on a fix for mtPaint:

Inkscape is an odd one. Even though it has a "Save to current directory" checkbox in Preferences, it is ignored, and always defaults to '/root'. Even after having saved or opened elsewhere, always defaults at '/root'.

I found a fix, it is to create /root/.config/inkscape/preferences.xml (nothing else in the folder), with this in it:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
id="exportarea" />
id="defaultxdpi" />
use_current_dir="1" />
path="/home/media" />
path="/home/media" />
scale="optimizeSpeed" />

This was not documented anywhere, I just examined 'preferences.xml' and found all of these  empty path="" entries, so put something into them. Inkscape does not seem to support a global preferences.xml under /etc.

Tags: easy

Chromium SFS uploaded

September 06, 2019 — BarryK

If you run PETget package manager (PPM), and install Chromium, it won't work. Easy has a script, /usr/local/petget/, that fixes some "difficult" packages. Chromium included, however the script is a bit old and needs updating for recent Chromiums.

I have updated the script, however, if you do install Chromium from PETget, you can perform a fix manually. Edit /usr/bin/chromium script, and alter the "exec" line to this:

     exec $LIBDIR/$APPNAME $CHROMIUM_FLAGS --test-type --no-sandbox "$@"

Then you should be good-to-go.

I have also created an SFS file. All SFSs for Easy Buster now require that you be running version 2.1.1 or later. Click "sfsget" on the desktop and you can install it, to run either in a container or on the main desktop.

So, now have some nice SFSs for Buster: Scribus, Krita and Chromium. What shall I add next?

It is not difficult to create these SFSs, except that Chromium involved a few hours work sorting out some details, such as default paths.
What I do is start with a "first bootup" situation, by erasing the session (see menu Filesystem -> Easy Version Control), then click on "petget" and install a package and it's dependencies, including any "doc" and "l10n" packages.
I then copy all of the '.session' folder somewhere, say: "cp -a /mnt/wkg/.session /mnt/sdc1/chromium_1.2.3_amd64"
I then delete all whiteout files: "find chromium_1.2.3_amd64  -mindepth 1 -type f -name '.wh.*' -delete" and some hidden files and folders at the top level.
I then go through and remove anything that isn't part of the Chromium install.
Maybe tweak a few things, such as the .desktop file, and make sure that usr/share/pixmaps/chromium.png exists, and for good measure usr/share/pixmaps/chromium48.png
I then run: "dir2sfs chromium_1.2.3_amd64"

If you want to try this for yourself, after creating the SFS, say 'myapp_1.2.3_amd64.sfs', copy it and myapp.specs and myapp.png, to /mnt/wkg/sfs/easyos/debian/buster, then click "sfsget" on the desktop and you can install it to a container ...and an icon should appear on the desktop.

One thing to be careful about, in usr/share/applications, make sure there is only one .desktop file, named appropriately, say 'myapp.desktop'. It is also highly recommended that "myapp" be the actual name of the executable. In future, I plan to support multiple .desktop files in the same SFS, but not yet.

In the future, all of the above could be automated and offered as an install option in PETget. That is, install to an SFS. 

Tags: easy

Easy Buster 2.1.1 released

September 05, 2019 — BarryK

Version 2.1.1 is a bug-fix release of 2.1, though it turned out to be more than bug fixes. Before I make even more changes, better get this version out!

Please read the announcement for version 2.1, just ten days ago:

To find out what is different, you can read this blog, or see the release notes here:

Recommended to also read this:

Download from here:

Feedback is welcome, in this thread of the Puppy Forum:

...please do not post EasyOS questions outside of this thread. 

Tags: easy