P.O. Johnson: My reply is bottom posted, to provide better
understanding to most readers of this message.
/s/ Bill Turner, wb4alm
On 1/3/23 11:38, P.O. Jonsson wrote:
Am 03.01.2023 um 16:13 schrieb Bill Turner, WB4ALM <wb4...@arrl.net>:
I would also like to suggest, that starting with Release 5, that a
version be pre-compiled for LINUX MINT 21.
I have found a number of folks who are not happy with some of the
recent versions of UBUNTU, and many of them are switching to LINUX
MINT 17 or LINUX MINT 21.
Hi Bill, we do have Linux Mint 20, is that not good for Linux Mint 21?
This is what I read:
"the Linux Mint 20 was released in 2020 based on Ubuntu 20.04, Mint 21
came in 2022 based on Ubuntu 22.04“.
The reason we have more versions of Ubuntu is accidental, we use
Ubuntu internally and build and test on 16,20 and 22 as it happens.
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Oh, I do understand....
Since I never had Linux Mint 20 installed, (I have been using Ubuntu 14,
18, 20, 22 LTS versions) I do not know if the internal changes between
Linux Mint 20 and 21 are "significant" or not.
I do know that the internal changes to UBUNTU 22 from --any-- previous
UBUNTU system were quite significant, and since MINT 21 uses UBUNTU
22.04 as a base, I choose to use the UBUNTU 22 version, in case the
internal changes might make a difference.
So far, REXX V5 works, but as you will see, I don't know if all of my
previous Rexx code would have continued to work...
...knowing what the ooRexx Developers do, and how they attempt to insure
compatibility, I'm sure that everything that I have constructed in the
past would continue to work.
But the UBUNTU developers aren't as thorough in some areas...
- - -
I no longer do "Systems Programmer" type work (and never did in either
the Windows or the Linux worlds), so I do not know what areas of the
kernel were changed, or how significant those changes might be to the
operation of REXX V5.0
One of the major changes in Ubuntu 22.04.1 LTS was in the Display
Subsystems and a forced change away from "X11" and towards "WAYLAND" for
GUI type stuff. (Overall Display System changes and the lack of system
stability is why I switched from UBUNTU to Linux Mint.) (My display
card is one from NVIDIA, and WAYLAND and NVIDIA drivers do not play
together very well.)
Another was a forced change was to use "SNAP" packages instead of ".deb"
packages for major software packages like GIMP, FIREFOX, THUNDERBIRD,
etc. Because SNAP creates fully contained sandboxes at an application
level, FIREFOX was no longer able to access my Home page, or any of the
normal files that it maintains; Thunderbird could not access the POP3
email files. Neither Thunderbird or Firefox could access the password
files, etc.
From August thru November, UBUNTU updated the 5.15 Kernel four or five
times, each change also impacted my primary desktop system.
and the other MAJOR reason for switching was, in my opinion, a very
poorly implemented upgrade process from UBUNTU 20.04.1 to UBUNTU 22.04.1:
UBUNTU apparently uses many PYTHON-3 scripts to assist in the
installation of software.
So in the --MIDDLE-- of a multi-hours long upgrade they swapped out
python3 and attempted to reinstall Python3 "on-the-fly". (Murphy's law:
It didn't reinstall.)
Apparently an older PYTHON script distributed in either UBUNTU 18 or 20
was on my system, and it caused the python3 reinstall to fail.
Since python3 is not now installed, the rest of the UPGRADE also failed
intermittently, which, somehow, caused a different 1-TB hard drive
(normally not mounted) to become MOUNTED, in addition to the one being
upgraded. Files from both 1-TB drives were now intermixed causing a
total destruction to the contents of both drives.
No problem, right? Just restore from backup and do it it again...
...WRONG! The second drive contained all of the backup files, along
with the operating system used to take the backups.
The backup system on this second drive was the only one that ever
mounted both set of drives.
Over 25 years of Rexx programming was lost in that exercise - and all
because nobody bothered to check "return codes" ---
or even considered do a PYTHON3 upgrade prior to the full install as
some sort of prerequisite.
Yes, I am "still" in the process of rewriting old support subroutines,
some of which are becoming much more "Object Oriented". (Which I am not
very good at...)
/s/ Bill Turner, wb4alm
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
