Precise-light - 17March2019 - for older hardware

[jrb]

What was changed in 5.7.2 to interfere with printing, network, X and poweroff? Presumably these all work on newer hardware.

The only thing changed was using a WoofCE build system that was 1 1/2 years newer. This supplies all the base Puppy code and often gets some major changes. I expect you are right and that the code was updated for newer hardware. I'm glad I left the Precise-light-5.7.1 accessible on Page 1. Your testing on all the old hardware shows its value.

Thanks, J

[Moose On The Loose]

The title sort of says it all.
If nobody has made a wine+mono SFS I may give it a try.

BTW:
Under wine I use
1) Analog/Linear LTSpice circuit simulation
2) ExpressPCB circuit board creation

My aim is to run those

[Mike Walsh]

@ Moose:-

Try version 2013's Wine 3.3 v2.1 - from here:-

http://www.murga-linux.com/puppy/viewto ... 240#985240

Mikeslr and I have both used this one quite a lot. I've been using an external WINE-3.3 sym-linked into multiple Puppies, with the apps started via custom Menu entries. It works fine with both Precise AND Precise light.

I use LTSpice myself, so I know it'll run it....


Mike.

[sindi]

What are the benefits of using the newer WoofCE?
The forum discussion is about Precise for 'older hardware'.
I am having problems with 5.7.2 even on a 2009 laptop where 5.7.1 and Tahr both work.
My 'older' hardware is 2001-2003, and my newer 2006-7 or even 2009.

I suspect Racy used the same newer WoofCE because it also puts the printer to sleep.

[s243a]

What was changed in 5.7.2 to interfere with printing, network, X and poweroff? Presumably these all work on newer hardware.

The only thing changed was using a WoofCE build system that was 1 1/2 years newer. This supplies all the base Puppy code and often gets some major changes. I expect you are right and that the code was updated for newer hardware. I'm glad I left the Precise-light-5.7.1 accessible on Page 1. Your testing on all the old hardware shows its value.

Thanks, J

I'm going to give 5.7.2 a try.

[Moose On The Loose]

You need to have the DEV SFS in place and then add the FreePascal one

If you ever used BorlandPascal, you will be right at home with it.
Bring up a terminal and type
fp
It brings up a text based IDE that is quite obvious to use.
The editor, compiler and built in "run the program" work.
So far no luck with debugger. I will be coming back to that later

https://drive.google.com/open?id=1Ndsp ... 6ujZCP5MX

[6502coder]

Precise-Light 572 runs just fine on my 2003 Compaq Presario 2300, 1.3 GHz Celeron noPAE with 1 GB RAM, which certainly qualifies as "older hardware." This is interesting to me because back when Precise Puppy was the current official Puppy, NONE of the Precise Puppies would power down correctly on this machine EXCEPT the very obscure Precise Puppy 5.4.93, which served me well for many years.

Before Precise, this old laptop ran Puppy 4, Puppy 5, and Wary; it currently quad-boots WinXP, DPupStretch 7.5 RC5, Precise-Light 572, and SailorE's Slacko 583.

[futwerk]

new backgrounds.

[s243a]

I'm just looking at precise light in a sandbox:

Code: Select all

bash -x ./psandbox.sh -f /mnt/home/precise/light/5.7.2/sandbox.out -o /mnt/home/sandbox.out --pdrv /mnt/home --maybe-psubdir  "precise/light/5.7.2" --no-exit

https://gitlab.com/s243a/psandbox

I notice that the DISTRO_SPECS has:

Code: Select all

DISTRO_ARCHDIR='i386-linux-gnu'

if I look in lib I see that 'i386-linux-gnu' is consistent with your DISTRO_SPECS (i.e. 'i386-linux-gnu is a symlink) but I thought that woof-CE got rid of the multi-arch symlink. Does this mean that you are doing something different than the latest woof-CE testing or was my understanding wrong that the multi-arch symlink was removed in the latest woof-CE?

[Moose On The Loose]

I am still investigating this but it appears that ROX won't go into an absolute link from an SFS file.

If I drop into a terminal the "ls" command works fine.

In ROX I get an error suggesting the thing linked to can't be accessed

[jrb]

Does this mean that you are doing something different than the latest woof-CE testing or was my understanding wrong that the multi-arch symlink was removed in the latest woof-CE?

The "17March2019" in the thread title refers to the WoofCE that I started with for Precise-light MK2. I have used that throughout. I know there were some major changes after that.

Cheers, J

[jrb]

I am still investigating this but it appears that ROX won't go into an absolute link from an SFS file.

If you are referring to a "Hard" link, they can only be used within the same filesystem, on the same partition, etc. Symlinks can be used across all filesystems, partitions, etc.

[s243a]

Does this mean that you are doing something different than the latest woof-CE testing or was my understanding wrong that the multi-arch symlink was removed in the latest woof-CE?

The "17March2019" in the thread title refers to the WoofCE that I started with for Precise-light MK2. I have used that throughout. I know there were some major changes after that.

Cheers, J

Cool. I'll consider your version the official legacy fork. May I have a link to your fork?

[jrb]

Does this mean that you are doing something different than the latest woof-CE testing or was my understanding wrong that the multi-arch symlink was removed in the latest woof-CE?

The "17March2019" in the thread title refers to the WoofCE that I started with for Precise-light MK2. I have used that throughout. I know there were some major changes after that.

Cheers, J

Cool. I'll consider your version the official legacy fork. May I have a link to your fork?

Here's a link to my slightly modified version. Precise is one of the build options. You can click on the build scripts and they will open in terminal window. It will pause and open an xmessage window just before building the puppy.sfs, this lets you check and modify within rootfs-complete. Click OK to continue.

Enjoy, J

[s243a]

It looks like the root certificate for Let's Encrypt is missing.

Code: Select all

sandbox# wget https://deb.torproject.org/torproject.org/dists/jessie/main/binary-i386/Packages.gz -O /tmp/pkg/root/ppa_Packages.gz
--2020-02-05 17:54:11--  https://deb.torproject.org/torproject.org/dists/jessie/main/binary-i386/Packages.gz
Resolving deb.torproject.org (deb.torproject.org)... 82.195.75.101, 116.202.120.165, 95.216.163.36, ...
Connecting to deb.torproject.org (deb.torproject.org)|82.195.75.101|:443... connected.
ERROR: cannot verify deb.torproject.org's certificate, issued by `/C=US/O=Let\'s Encrypt/CN=Let\'s Encrypt Authority X3':
  Unable to locally verify the issuer's authority.
To connect to deb.torproject.org insecurely, use `--no-check-certificate'.

I was running precise light in a sandbox (above). I was seeing if I could add the jessie tor repo (using sc0ttman's pkg. I'll add the certificate tomorrow and try again.

As a side note the zdrv seems to be required in a chroot for dns resolution. My guess is that libnss must talk to the kernal.

[Moose On The Loose]

@ Moose:-

Try version 2013's Wine 3.3 v2.1 - from here:-

http://www.murga-linux.com/puppy/viewto ... 240#985240

Mikeslr and I have both used this one quite a lot. I've been using an external WINE-3.3 sym-linked into multiple Puppies, with the apps started via custom Menu entries. It works fine with both Precise AND Precise light.

I use LTSpice myself, so I know it'll run it....


Mike.

When I tried ExpressPCBPlus on the wine, it didn't work.
I got an error about unable to find some lib and another about some "device".
I intend to dig a bit deeper on this.

I have converted the wine pet into a SFS that can be used on systems that can't get to the internet but before I publish for others, I will see if I can make mono work.

[s243a]

I'm trying to add the needed certificates, but I'm wondering if we might need to update openssl. See thread:
Draft: Install Let's Encrypt Root CA on Precise Light

On Buster it says the following version of openssl is required:

Code: Select all

dep: openssl (>= 1.1.1) 

https://packages.debian.org/buster/ca-certificates

Edit:

I just looked at /packages/woof-install-packages, and it conforms that the version of openssl in precise-light is older than this:

Code: Select all

openssl_1.0.1|openssl|1.0.1|4ubuntu5.39|Graphic|899K|pool/main/o/openssl|openssl_1.0.1-4ubuntu5.39_i386.deb|+libssl1.0.0&ge1.0.1|Secure Socket Layer SSL binary and related cryptographic tools|ubuntu|precise||

Edit 2
The openssl requirement for stretch seems to be compatable with the openssl in precise light:

Code: Select all

dep: openssl (>= 1.0.0)
    Secure Sockets Layer toolkit - cryptographic utility 

https://packages.debian.org/stretch/ca-certificates

Therefore, I'll try copying the update-ca-certificates command from stretch.

[Moose On The Loose]

This morning, I had to reset my PC because Precise-light appeared to not be able to come back from "screen saver" mode.

I had left a terminal open and a compile happening.

This morning I have a great many xxx.o files so I assume the compile stopped at some point, perhaps when done.

[jrb]

Therefore, I'll try copying the update-ca-certificates command from stretch.

I just copied update-ca-certificates from bionicpup and got

Code: Select all

34 added, 0 removed; done.

/usr/share/ca-certificates/mozilla has 42 certificates all dated 08 Feb 2016,

I'll make a .pet with the "update-ca-certificates" upgrade, unless you're aware of other complications.

Thanks for pointing this out, J

[s243a]

Therefore, I'll try copying the update-ca-certificates command from stretch.

I just copied update-ca-certificates from bionicpup and got

Code: Select all

34 added, 0 removed; done.

/usr/share/ca-certificates/mozilla has 42 certificates all dated 08 Feb 2016,

I'll make a .pet with the "update-ca-certificates" upgrade, unless you're aware of other complications.

Thanks for pointing this out, J

I can test your pet. If we don't find any issues then we can make it a built-in package.