EasyOS version 2.3.2, June 22, 2020

[mikeslr]

thanks L18L
I started with petget, but there are only playonlinux and winetricks packages in the package manager...

Did you try playonlinux? My recollection is that it is a robust wine management system. Once installed, playonlinux will, itself, both provide the 32-bit compatibility layer AND download wine versions. But, that could be a false memory; or one derived from Linux Mint.

Winetricks is actually a Linux application mostly for installing 'goodies' into the alien-to-Linux Wine-file-structure.

[L18L]

thanks L18L
I started with petget, but there are only playonlinux and winetricks packages in the package manager. Of course, I updated the database in the first round. Only then did I use the old files.
In the meantime, I went through what mikeslr wrote and couldn't find a 32/64 bit compatible file.
If I understand correctly, is it possible to install wine in the built-in container (racy, buster, xenial) in easyOS?
Thanks for the comments

let petget search in all repositories
select wine64 for install (and dependancies)

good luck

edit: hope you made some progress. Sorry that I cannot help more with wine, just 1 hint: executable file is under /usr/lib/wine/...

[L18L]

Some changes in /usr/share/doc/easy/welcome.sh enable some translations in TEXTDOMAIN easyhelp ...

[Rodney Byne]

To Barry,
Following your blog, in EasyOS, I tried downloading pmcputemp.pet to
first "Personal" and then "Downloads" and after two days of searching
the Home and many other directories, I can't find either of the two pets.
Can you help by telling me where they are please.
Also there is no led on that particular Cruzer Blade stick.
I am limited to buying whatever is locally available.

By comparison, finding and installing pmcputemp.pet in
EasyPup 2.3.1 was a complete success.
The tiny led stopped flashing after bootup and didn't do any writes
at all thereafter, so that stick should last a bit longer.
Thanks.

[lp-dolittle]

@ Rodney Byne

Hi Rodney,

did you try to find the 'missed' pet via pFind in the Filesystem-Menu?

This might be quite an easy way to spot it.

kind regards

EDIT:

Running EasyOS 2.3.1, I just tried to download and install the pmpcutemp-1.1-buster64.pet and was able to do so without any problems. The pet was saved to /home/downloads

hope this information is useful to you

regards

[lp-dolittle]

@ Barry,

Hi Barry,

Thank you for paying attention to 'latent' writes on drives during a computer's 'inactivity' which might reduce the durability of flash-sticks.

How necessary is pmcputemp? Does it simply display the cpu-temperature or also regulate the fan-speed?

If I recall a previous (quite long ago) post of Sage correctly, the information about the cpu-temperature in the applet-try is imprecise and possibly misleading.

So, what about getting rid of pmpcutemp or offering the option to do so for those who can do without it and prefer an increased durability of their flash-sticks?

kind regards

[Rodney Byne]

Hi to lp-dolittle.

Thanks for your help.

Yes, pFind was useful, because it also couldn't
initially find the missing pet.

However, for me at least the answer was NOT
to use a browser inside a container.

Using WWW from the top row of icons gave a
faultless download to /home/personal which is
where I wanted to store it.

When I again used pFind, the screen was filled with
locations from the original and the .pet sources,
so all is now well.
Best regards.

[BarryK]

Another one is out!

Version 2.3.2 blog announcement:

https://bkhome.org/news/202006/easyos-v ... eased.html

[hcarrega]

I’m new to easyOS but I like the concept. My question is whether there will be an easy way to compile a newer kernel for example 5.7.4
Thanks

[Sage]

gremlins asked to 'submit' - twice! It happens sometimes.

[Sage]

2.3.2 working well, thanks!

[alfons]

Barry, thanks a lot!

UPGRADE
I have upgraded from 2.3.1 to 2.3.2 and all settings have been applied - very good!

BCRYPT
The program bcrypt (Menu -> Personal -> "Bcrypt file encryption") has not been working for a long time. I don't know if this is still useful in EasyOS

IOTOP
If I start iotop after startup and do not make any entries for half an hour, I get this result, i.e. there is practically no activity on the USB-stick and the LED does not blink. This is very good!

[Terry H]

Running EasyOS 2.3 Didn't update to 2.3.1), I downloaded and manually updated the 3 entries( easy.sfs, initrd, vmlinuz) in the boot partition sdb1. I then clicked the initrd and updated successfully. On reboot it failed.

Code: Select all

Working drive speed test (lower the better): 92
mount: mounting /dev/sdb2 on mount /mnt/sdb2 failed invalid argument
ERROR: Unable to mount working partition sdb2...

On the first attempt typed "exit", which then continued to then say could not unmount sdb2, then kernel panic.

I then used easypup to run a fsck against the easyOS working partition, which corrected errors. rebooted and attempted to boot easyOS, but failed again as above.

Back in EasyPup I re-did the upgrade of the easyOS boot partition and clicked the initrd to update the boot specs.

Reboot to easyOS, still get same error. I have done this upgrade many times previously, without issue. No idea why this upgrade failed. I am able to access the partition from other installs.

How can I upgrade my USB install, preferably without loosing the earlier installs of easyOS?

Thanks in advance.

Terry

[scsijon]

I'm not sure how it's happened, but with 2.3.2 I can no longer:>

1- install by dd to a clean memory stick;
2- reboot and allow sdb2 to grow to competely fill the drive;
3- reboot on another easy, then plug in the 2.3.2 memory stick as (so it's not mounted) sdb and using gparted, shrink sdb2 to allow the addition of a third partition on sdb.

I can however add the extra partition before allowing sdb2 to grow (2 above) and it all works correctly.

As I use the extra partition for development work and backups depending on what it's being used for, it is a serious setback from my point of view.

It would also be nice to be able to limit the size of sdb2's initial growth, especially with TB portable ssd's, micro SD and USB memory sticks already out there at up to 2TB and larger ones promised by the end of this year.

[BarryK]

I tried Peasydisk Version 5.1 and received same results as above.
Added genisoimage with petget and peasydisk works fine.
Please examine this further.

I was wondering about suggesting a symlink but then I took a glance in my DpupStretch and I see that it has this little script as /usr/bin/genisoimage

Code: Select all

#!/bin/sh
# Authors: Brandon Snider.
# This script redirects genisoimage commands to mkisofs. In case of --version being passed, the script returns a specific string to
# satisfy Brasero. In case of the old options -L, -H, and -P, the script adds -legacy to the args to properly instruct mkisofs.

legacy="no" # Create variable with default status of "no"

for i in "$@" # Iterate over all of the command line options looking for the old ones.
do
    if [ "$i" = "-L" -o "$i" = "-H" -o "$i" = "-P" ] ; then
       legacy="yes" # Set the legacy variable to "yes" if one of the variables is found.
    elif [ "$i" = "--version" ] ; then
       legacy="version" # Set the variable to "legacy" to return the string expected by Brasero
    fi
done

if [ $legacy = "yes" ] ; then
    /usr/bin/mkisofs -legacy "$@"  # Pass -legacy option. 
elif [ $legacy = "no" ] ; then
    /usr/bin/mkisofs "$@" # In all other situations, pass all options to mkisofs.
elif  [ $legacy = "version" ] ; then
    echo "genisoimage 1.1.11" # Pass the version info expected by any app querying Genisoimage.
fi

This might be better than installing cdrkit in addition to the already included cdrtools or even Debian's genisoimage Buster package (Debian have split up cdrkit into separate packages as they often do).

Thanks for that, the script, slightly modified, is in easy 2.3.2

Blog post:

https://bkhome.org/news/202006/missing- ... asyos.html

[BarryK]

Some changes in /usr/share/doc/easy/welcome.sh enable some translations in TEXTDOMAIN easyhelp ...

Brilliant, this is in easy 2.3.2.

Blog post:

https://bkhome.org/news/202006/translat ... -page.html

[BarryK]

I’m new to easyOS but I like the concept. My question is whether there will be an easy way to compile a newer kernel for example 5.7.4
Thanks

Yes, you will need the "devx" SFS loaded, and get the scripts and patches here:

http://distro.ibiblio.org/easyos/source/kernel/

folder 5.4.47 only has the latest config file, go back to folder 5.4.18 for the scripts and patches.

However, you will need to get an updated aufs patch for a later kernel.

Note, I am planning to compile 5.8.1 as soon as it is released, as very interested in the new features of procfs, for use in containers.

[BarryK]

Running EasyOS 2.3 Didn't update to 2.3.1), I downloaded and manually updated the 3 entries( easy.sfs, initrd, vmlinuz) in the boot partition sdb1. I then clicked the initrd and updated successfully. On reboot it failed.

Code: Select all

Working drive speed test (lower the better): 92
mount: mounting /dev/sdb2 on mount /mnt/sdb2 failed invalid argument
ERROR: Unable to mount working partition sdb2...

On the first attempt typed "exit", which then continued to then say could not unmount sdb2, then kernel panic.

I then used easypup to run a fsck against the easyOS working partition, which corrected errors. rebooted and attempted to boot easyOS, but failed again as above.

Back in EasyPup I re-did the upgrade of the easyOS boot partition and clicked the initrd to update the boot specs.

Reboot to easyOS, still get same error. I have done this upgrade many times previously, without issue. No idea why this upgrade failed. I am able to access the partition from other installs.

How can I upgrade my USB install, preferably without loosing the earlier installs of easyOS?

Thanks in advance.

Terry

OK, give me a bit of time to think what you can do to investigate this. pressed for time right now. probably this evening will take a look at it.

EDIT:
OK, I think maybe I know where the problem is. Run easypup again, and click on the 'initrd' for your easyos installation, to open it up.

Click on the 'init' script in the initrd, to edit it. At line 616 you will see this code:

Code: Select all

 if [ "${WKG_FS}" == "ext4" ];then #200621 change journal commit interval from 5 to 30...
  #rw,relatime,data=ordered are the defaults anyway...
  mount -t ${WKG_FS} -o commit=30,rw,relatime,data=ordered /dev/$WKG_DEV /mnt/$WKG_DEV
 else
  mount -t ${WKG_FS} /dev/${WKG_DEV} /mnt/${WKG_DEV}
 fi
 [ $? -ne 0 ] && err_exit "Unable to mount working-partition ${WKG_DEV}"

It seems that in your case, the -o options above, is causing the problem. I don't know why, it worked for me.

Anyway, just delete all of "-o commit=30,rw,relatime,data=ordered", save, exit, click on 'initrd' again to update it, then see if easyos boots.

[BarryK]

I'm not sure how it's happened, but with 2.3.2 I can no longer:>

1- install by dd to a clean memory stick;
2- reboot and allow sdb2 to grow to competely fill the drive;
3- reboot on another easy, then plug in the 2.3.2 memory stick as (so it's not mounted) sdb and using gparted, shrink sdb2 to allow the addition of a third partition on sdb.

I can however add the extra partition before allowing sdb2 to grow (2 above) and it all works correctly.

As I use the extra partition for development work and backups depending on what it's being used for, it is a serious setback from my point of view.

It would also be nice to be able to limit the size of sdb2's initial growth, especially with TB portable ssd's, micro SD and USB memory sticks already out there at up to 2TB and larger ones promised by the end of this year.

I only tested 2.3.2 on one usb-stick, used easydd to write image, rebooted and the working-partition did grow to fill the drive.

Tonight I will test on more usb-sticks.

[OscarTalks]

BCRYPT
The program bcrypt (Menu -> Personal -> "Bcrypt file encryption") has not been working for a long time. I don't know if this is still useful in EasyOS

I think this is because a weakness/vulnerability in bcrypt was reported as a bug and Debian patched it to disable encryption but leave it available (with a warning) in case anyone needed it to decrypt anything.
If you want it to encrypt as well you can just compile the source and substitute the executable, bearing in mind that the "bug" exists.
This reply was posted from NetSurf 3.10 in EasyOS 2.3.2