I am using Mint 19.1 Tessa and have updated my kernal to 5.4.0-137.
Supposedly the kernal is only supported until April 2023. What happens
after April 2023?

--
Pity the fool who followed his GPS over the cliff

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2023-02-02, Nic wrote:
> I am using Mint 19.1 Tessa and have updated my kernal to 5.4.0-137.
> Supposedly the kernal is only supported until April 2023. What happens
> after April 2023?

No, it's not "the kernel" that is going EOL, but rather that the entire
Linux Mint 19 release set (19, 19.1, 19.2, 19.3) goes EOL in April. It
means that the version is no longer supported, and that it will no
longer receive security updates.

Best course of action is to upgrade to LM 20.

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmPbywAACgkQbWVw5Uzn
KGBWlQ/8DGpLaJak/uB6AUnoTGwyu6g9uTQHQ0UtsHWVx6qCTblTPYOQHs2t2kZw
Wb0zwmNMPgT25jRbu/fNFw1dCFkAX2yJDRY7n9uOO5yPde5lf1aPE4kOcIUSfhyg
XzcI11S1uc4WwIbtCp3bvUnktCWTuVRNt3v696FSPNOzDVFELQkAXtoVkmt9WF92
a46CzUglcMAlfXG4VqoM9TI6bvScYKVyetfcc336QnV/Y2oKmCCw+CbKNGTd0KhC
XVa8KDvwqQ2CZdZbkYUx5hZ3AN3Cqcwce7hUc2wD6hISNjVyiheSRTmrUoxd130X
3dLvRBV09z7XVHBLgKiuSh3rk+QOhK9z39i5DoQS4EVQq2XxnuZMoLhcuxcRvGgq
+TCGWhxQLt8F2gLSZZMPXxfIXDS+BZMJs1QgQQNmcz6/WUn4i1oxjGChgFyu7nkq
ofJLO4L874VTJLJ2ysTW1Z/aO/tiYxYzzDQrXGCaq9N7N7nm0th7izOCMlbx5h3J
nS23xJjtwQtIVv/7y9Zdj0dnbPqfvyrqwMv4XkfwOCccFds7aaXqCTuOxDk0d2qY
CJ6iz3kXujXLQZquJs4c2HYXDv9r4sonCWoedVKB/VNC1crS4Y5SM9W27aSvVW+g
kjAPiO5sdtoCOK2RPkex+uB16JnrT7uJiWf0YazmBfMxy+D3xJc=
=aUhM
-----END PGP SIGNATURE-----

--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

On 2/2/23 9:37 AM, Dan Purgert wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On 2023-02-02, Nic wrote:
>> I am using Mint 19.1 Tessa and have updated my kernal to 5.4.0-137.
>> Supposedly the kernal is only supported until April 2023. What happens
>> after April 2023?
> No, it's not "the kernel" that is going EOL, but rather that the entire
> Linux Mint 19 release set (19, 19.1, 19.2, 19.3) goes EOL in April. It
> means that the version is no longer supported, and that it will no
> longer receive security updates.
>
> Best course of action is to upgrade to LM 20.
>
>
> -----BEGIN PGP SIGNATURE-----
>
> iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmPbywAACgkQbWVw5Uzn
> KGBWlQ/8DGpLaJak/uB6AUnoTGwyu6g9uTQHQ0UtsHWVx6qCTblTPYOQHs2t2kZw
> Wb0zwmNMPgT25jRbu/fNFw1dCFkAX2yJDRY7n9uOO5yPde5lf1aPE4kOcIUSfhyg
> XzcI11S1uc4WwIbtCp3bvUnktCWTuVRNt3v696FSPNOzDVFELQkAXtoVkmt9WF92
> a46CzUglcMAlfXG4VqoM9TI6bvScYKVyetfcc336QnV/Y2oKmCCw+CbKNGTd0KhC
> XVa8KDvwqQ2CZdZbkYUx5hZ3AN3Cqcwce7hUc2wD6hISNjVyiheSRTmrUoxd130X
> 3dLvRBV09z7XVHBLgKiuSh3rk+QOhK9z39i5DoQS4EVQq2XxnuZMoLhcuxcRvGgq
> +TCGWhxQLt8F2gLSZZMPXxfIXDS+BZMJs1QgQQNmcz6/WUn4i1oxjGChgFyu7nkq
> ofJLO4L874VTJLJ2ysTW1Z/aO/tiYxYzzDQrXGCaq9N7N7nm0th7izOCMlbx5h3J
> nS23xJjtwQtIVv/7y9Zdj0dnbPqfvyrqwMv4XkfwOCccFds7aaXqCTuOxDk0d2qY
> CJ6iz3kXujXLQZquJs4c2HYXDv9r4sonCWoedVKB/VNC1crS4Y5SM9W27aSvVW+g
> kjAPiO5sdtoCOK2RPkex+uB16JnrT7uJiWf0YazmBfMxy+D3xJc=
> =aUhM
> -----END PGP SIGNATURE-----
>
I do dread that idea. I realize there is a thread active right now about
the pitfalls/requirements of upgrading. Upgrading versus a clean
install. I guess if I am going to upgrade I should start making a list
of the data I want/need to backup/copy to an external drive.

On 2/2/23 09:46, this is what Nic wrote:
> On 2/2/23 9:37 AM, Dan Purgert wrote:
> On 2023-02-02, Nic wrote:
>>>> I am using Mint 19.1 Tessa and have updated my kernal to 5.4.0-137.
>>>> Supposedly the kernal is only supported until April 2023. What happens
>>>> after April 2023?
> No, it's not "the kernel" that is going EOL, but rather that the entire
> Linux Mint 19 release set (19, 19.1, 19.2, 19.3) goes EOL in April. It
> means that the version is no longer supported, and that it will no
> longer receive security updates.
>
> Best course of action is to upgrade to LM 20.
>
Hell if he's going to do a fresh install, install 21.1.
He can boot the live cd and see how it works. I ran the live cd for about 2 hours and tested adding some apps. etc.>
> I do dread that idea. I realize there is a thread active right now about the pitfalls/requirements of upgrading.
> Upgrading versus a clean install. I guess if I am going to upgrade I should start making a list of the data I want/need
> to backup/copy to an external drive.
>

You don't already do that?
I use the backup tool to pick stuff in my home folder, exclude a bunch of stuff that large and useless (to me).
And since backtool only does home, the I have a shell that copies select files / folders below home also, all to a thumb
drive.

Every day. Simple plug and run script. I failure read to 8am every day.
Al

Every day. Simple plug and run script. I'm failure ready back to 8am every day.
Al

On 2/2/23 10:02 AM, Big Al wrote:
> Every day. Simple plug and run script.   I'm failure ready back to 8am
> every day.
>      Al

Sounds complicated, for those who are not able to write a script. My
method has been so far, to clone the entire hard drive, so that the only
things that would be missing would be my journal (calendar/appointment) 
entries made up to that time.

On 2/2/2023 9:46 AM, Nic wrote:
> On 2/2/23 9:37 AM, Dan Purgert wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA512
>>
>> On 2023-02-02, Nic wrote:
>>> I am using Mint 19.1 Tessa and have updated my kernal to 5.4.0-137.
>>> Supposedly the kernal is only supported until April 2023. What happens
>>> after April 2023?
>> No, it's not "the kernel" that is going EOL, but rather that the entire
>> Linux Mint 19 release set (19, 19.1, 19.2, 19.3) goes EOL in April.  It
>> means that the version is no longer supported, and that it will no
>> longer receive security updates.
>>
>> Best course of action is to upgrade to LM 20.
>>
> I do dread that idea. I realize there is a thread active right now about the pitfalls/requirements of upgrading. Upgrading versus a clean install. I guess if I am going to upgrade I should start making a list of the data I want/need to backup/copy to an external drive.
>

Some distros are nothing but trouble, and the teams
there seem to love to leave loose ends for you to cut
yourself.

Ubuntu and Linux Mint aren't like that.

You still need technical proficiency, to the level of
being able to root cause what customization you did,
broke something.

If you update your notes file, with the details (like
the special procedure for the DeCSS library, or how
Google Earth put an entry in package manager), then you
should be able to reverse those, and make the Upgrade
go smoother.

I try to return the graphics to whatever the install
default was. To reduce the chances of something
DKMS-related breaking. I'm not even sure now, that
they are using DKMS any more (used for VirtualBox additions
and Nvidia additions).

I just back up the whole machine (one drive), as
working at the component level is "too much work
for me".

if this is your Daily Driver, just make sure to find
a low-pressure time on your schedule. The machine
can sense when you're nervous, and it will then use
every opportunity to make life miserable for you.

Paul

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2023-02-02, Big Al wrote:
> On 2/2/23 09:46, this is what Nic wrote:
>> On 2/2/23 9:37 AM, Dan Purgert wrote:
>> On 2023-02-02, Nic wrote:
>>>>> I am using Mint 19.1 Tessa and have updated my kernal to 5.4.0-137.
>>>>> Supposedly the kernal is only supported until April 2023. What happens
>>>>> after April 2023?
>> No, it's not "the kernel" that is going EOL, but rather that the entire
>> Linux Mint 19 release set (19, 19.1, 19.2, 19.3) goes EOL in April. It
>> means that the version is no longer supported, and that it will no
>> longer receive security updates.
>>
>> Best course of action is to upgrade to LM 20.
>>
> Hell if he's going to do a fresh install, install 21.1.

Definitely :)

> [...]

>> I do dread that idea. I realize there is a thread active right now
>> about the pitfalls/requirements of upgrading. Upgrading versus a
>> clean install. I guess if I am going to upgrade I should start making
>> a list of the data I want/need to backup/copy to an external drive.
>>
>
> You don't already do that?

On the upside, no existing backups does kind of imply none of the data
is all that important if it were lost :)

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmPb8koACgkQbWVw5Uzn
KGBHAw//YzajZxjO6Dp4svL+ttx9kV5HV4UfR6sV5HhaDe716zW+yCjAH0oaO86W
WjW6vSbcoRSVsSQVLF5fxrqMopdaPxwRJYxyln0XPaqCN7saUU9biPqwDrwaYGHg
aLDbmggWKT0uVdQH/5DAhUfL7c254LOzTeQz6NdZwtFvn6K9PofFsw0CcNo6px9M
9r855Vz3n2Yn8qUWgoVJC1pFtdAjBebS2GToIg9+5uTx7VeWfBWziYpXjICi9OFN
aC4nwsw6UhcRPHL1DkL31FgZBgRCaxIUwIxl3OxuzW79SQgF4KgqqaYg2OYm4UKn
O4RNiF/Ze5KrLoYyWvWGRaqTMImTWDt7T8icEjvQTdNZNCAfojUeUAZPVNSLpBc4
sEHnaSvfE2AtzTeGYzIbyGt5wjD/84XikdAw0wrGomFA3J7v01iOuT73tNAKYRUT
hdeuUAxJ3ajUmbd7atE7+ZPyxaVCu7DQrhMj2Uih9WzSYK6pBQQcJvUzLjhBv/hC
jbe7Is505WTlBRxkQns4jpnd0dO+3B4CkqgsQg8ZiIyLFgRGyGNk+Gdp0jalImvZ
5bJ6oTuJdNQGCbiUzxwpL/n1LZEviVRvnDxOpqUpuFFsUzvJVn3ppnoYCTrtXZt0
OfQq8qjjMQ6ozREoDh4AVcSbWJqVpbPY5XftGahk1m9G1uud19w=
=7+mI
-----END PGP SIGNATURE-----

--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2023-02-02, Nic wrote:
> On 2/2/23 10:02 AM, Big Al wrote:
>> Every day. Simple plug and run script.   I'm failure ready back to 8am
>> every day.
>>      Al
>
> Sounds complicated, for those who are not able to write a script. My
> method has been so far, to clone the entire hard drive, so that the only
> things that would be missing would be my journal (calendar/appointment) 
> entries made up to that time.
>

I use rsync myself; from the laptop to the desktop (pretending to be a
server).

the "script" is just so I can plug a single script
("/usr/local/bin/backup") into a cronjob that runs daily at 00:30.

The entire body of the script is just the two commands

rsync -avP -e "/root/backup.key" \
--exclude-from "/root/exclude.txt" \
/home/ backups@backup:/srv/backups

echo "Backup done on $host"|mail -s "Backup Done!" root

Saturdays I run a job on the "backups" machine that copies to an
external USB drive (but this is manual).

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmPb9GcACgkQbWVw5Uzn
KGBABg//VnO1RN/1BkXr0JlHTKztvydaeB0hYObWkqISLXUHDuefiW9UH2cmdiY4
IGvihkPuTz9JxLddsJo2gq7X5Ol7u1AlorPE3upWXjN/1ca0ivzXIZvWjM+idnBv
5ExGBy+icj7Et9E7MnjRcouqU3HAzcucqufHWMN+Lmc9opyJ7/1PRfCDx4AU12Ey
vZ+Y6caetsocJlaMuvOkjC6jrd9l4KbKM48NpfA/DWLlEFvlj7c9FOYJSQUly+/y
BQ+TopC0xsQ+A7w9bD2kpB+nGbsQXS1yy6ZkMOJCExzH+3KxTDWjo8pCnWTC5UQW
Sxl1fVF+sTL7Io/Cr66Z0iwcdSAcRM6ytZu0SZIHfluzlNZKmY2Hj/EbBMXgaHwl
m7N7eLH5mRIx709pPmgnAVbxYP7sm9F4jdamC6I03hIQ42/X/OjF5CqdFWIwM+ny
UwX9xmU9WB/1De/elQWIsWbFhNkeoAX0ua+0QAdl3Yh9/A+CVhtV/3IVz9wxdz2O
xqhcQ0vtU9DF+PEsvwVcGiSO0l/a9pqfG9K4Ljhw99mYdC85oPI4UwxdjRpclTHP
LSr2JK2qC477A2G3hig2VVCM74NlerWrz59LWLgOP51qKodyxb7Be8CiODzewahp
vp5keDyY6NCnBOof8qEWehVVAH0oZs3C8idv1ZHLc3x/azeuKNo=
=vUfS
-----END PGP SIGNATURE-----

--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

On Thu, 2 Feb 2023 10:16:22 -0500, Nic wrote:
> On 2/2/23 10:02 AM, Big Al wrote:
>> Every day. Simple plug and run script.   I'm failure ready back to 8am
>> every day.
>>      Al
>
> Sounds complicated, for those who are not able to write a script.

Yep, you either tell the computer what work to do :)
or let the computer work you. :(

A basic script is a copy of the commands you would execute in a terminal.
You would need to find/use Cli commands to do whatever you would do in a
gui tool.

Coding a script is easy enough in bash. Take a look at
http://tldp.org/LDP/Bash-Beginners-Guide/html/
http://tldp.org/LDP/abs/html/index.html

Changing configuration files are fairly easy to do with a
while loop, set. and case statements.

I use expect to automagically feed input to interactive scripts like
the install script needed for my printer/scanner driver install.

ftp://ftp.cme.nist.gov/pub/expect/

You can run your script through shellcheck to catch possible errors.
I found is handy to keep/have boilerplate/skeleton scripts which have most
of the code needed for the task. I just copy one to new_script name and
start deleting/adding needed code. Examples

$ dir *skel*
-rwxr-xr-x 1 root root 2.6K Nov 6 09:12 bash_skeleton
-rwxr-xr-x 1 root root 6.9K Aug 2 2020 install_skeleton
-rwxr-xr-x 1 root root 3.6K Jan 30 2021 skeleton_changes
-rwxr-xr-x 1 root root 3.8K May 16 2021 skeleton_sb_drop_in_changes
-rwxr-xr-x 1 root root 4.9K Aug 3 2020 skeleton_service_changes

Then there are all sorts of FAQ and guide to be found with your browser.
Need help try a shell Usenet group, example comp.unix.shell

I believe in the six P's,
prior planning prevents piss poor performance.

You might consider putting
warnier orr diagrams
in your search engine.

You can put repetitive stuff in an include file. For example for changes I
have a functions_changes file with these subroutines/functions.

$ grep function fun*change* | grep -v '}'
#* functions_change - functions for changes scripts
function set_facl ()
function save_facl ()
function save_perms ()
function set_perms ()
function ck_vorig_dir()
function ck_vsave_dir()
function ck_rpmnew()
function cp_vsave_vinstal()
function cp_vinstall()
function cp_vorig()
function mv_vorig()
function restore_vinstall()
function restore_vorig()
function null_fn ()
function chg_check ()
#************************** end functions_changes ****************
with about
$ sort -u functions_change | grep -v '#' | wc -l
127
lines of code.

Pretty sure someone in this group can tell you what command can be used
to do something that you do with a gui tool.

On 2/2/23 12:25, this is what Dan Purgert wrote:
> On 2023-02-02, Big Al wrote:
>> On 2/2/23 09:46, this is what Nic wrote:
>>> On 2/2/23 9:37 AM, Dan Purgert wrote:
>>> On 2023-02-02, Nic wrote:
>>>>>> I am using Mint 19.1 Tessa and have updated my kernal to 5.4.0-137.
>>>>>> Supposedly the kernal is only supported until April 2023. What happens
>>>>>> after April 2023?
>>> No, it's not "the kernel" that is going EOL, but rather that the entire
>>> Linux Mint 19 release set (19, 19.1, 19.2, 19.3) goes EOL in April. It
>>> means that the version is no longer supported, and that it will no
>>> longer receive security updates.
>>>
>>> Best course of action is to upgrade to LM 20.
>>>
>> Hell if he's going to do a fresh install, install 21.1.
>
> Definitely :)
>
>> [...]
>
>>> I do dread that idea. I realize there is a thread active right now
>>> about the pitfalls/requirements of upgrading. Upgrading versus a
>>> clean install. I guess if I am going to upgrade I should start making
>>> a list of the data I want/need to backup/copy to an external drive.
>>>
>
>> You don't already do that?
>
> On the upside, no existing backups does kind of imply none of the data
> is all that important if it were lost :)
>
>
>
One thing about IMAP email is that if anything goes belly up, if I can get the local folders out of TB pretty easy and
then reloading the program and making the new accounts is simple, and all the files just appear, inbox/trash etc.
Its the settings that kill you. Thus I backup the ~/.thunderbird folder nightly.

On 2/2/23 9:37 AM, Dan Purgert wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On 2023-02-02, Nic wrote:
>> I am using Mint 19.1 Tessa and have updated my kernal to 5.4.0-137.
>> Supposedly the kernal is only supported until April 2023. What happens
>> after April 2023?
> No, it's not "the kernel" that is going EOL, but rather that the entire
> Linux Mint 19 release set (19, 19.1, 19.2, 19.3) goes EOL in April. It
> means that the version is no longer supported, and that it will no
> longer receive security updates.
>
> Best course of action is to upgrade to LM 20.
>
>
> -----BEGIN PGP SIGNATURE-----
>
> iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmPbywAACgkQbWVw5Uzn
> KGBWlQ/8DGpLaJak/uB6AUnoTGwyu6g9uTQHQ0UtsHWVx6qCTblTPYOQHs2t2kZw
> Wb0zwmNMPgT25jRbu/fNFw1dCFkAX2yJDRY7n9uOO5yPde5lf1aPE4kOcIUSfhyg
> XzcI11S1uc4WwIbtCp3bvUnktCWTuVRNt3v696FSPNOzDVFELQkAXtoVkmt9WF92
> a46CzUglcMAlfXG4VqoM9TI6bvScYKVyetfcc336QnV/Y2oKmCCw+CbKNGTd0KhC
> XVa8KDvwqQ2CZdZbkYUx5hZ3AN3Cqcwce7hUc2wD6hISNjVyiheSRTmrUoxd130X
> 3dLvRBV09z7XVHBLgKiuSh3rk+QOhK9z39i5DoQS4EVQq2XxnuZMoLhcuxcRvGgq
> +TCGWhxQLt8F2gLSZZMPXxfIXDS+BZMJs1QgQQNmcz6/WUn4i1oxjGChgFyu7nkq
> ofJLO4L874VTJLJ2ysTW1Z/aO/tiYxYzzDQrXGCaq9N7N7nm0th7izOCMlbx5h3J
> nS23xJjtwQtIVv/7y9Zdj0dnbPqfvyrqwMv4XkfwOCccFds7aaXqCTuOxDk0d2qY
> CJ6iz3kXujXLQZquJs4c2HYXDv9r4sonCWoedVKB/VNC1crS4Y5SM9W27aSvVW+g
> kjAPiO5sdtoCOK2RPkex+uB16JnrT7uJiWf0YazmBfMxy+D3xJc=
> =aUhM
> -----END PGP SIGNATURE-----
>
I noticed that you chose upgrade to LM 20 and not LM21, and ignored a
clean install.

I did a live try of LM21 and installed 1 program that I use frequently.
The program is called OSMO. On my current version I have a contacts tab,
whereas the new version installed on LM21 did not have this contact tab.
This for me was a deal breaker. I will try out LM20 to see if it has the
same problem.

Nic wrote:
> I did a live try of LM21 and installed 1 program that I use frequently.
> The program is called OSMO. On my current version I have a contacts tab,
> whereas the new version installed on LM21 did not have this contact tab.
> This for me was a deal breaker. I will try out LM20 to see if it has the
> same problem.

According to my reading, the most recent release of osmo is 4.4 which
was released 2020 Apr. while my LM 20.1 shows v 4.2 in its repo/s which
was rel in 2017.

Booting a live LM 21 and updating its repo/s showed me its osmo package
was 4.4,

Since I don't use osmo, I'm not familiar w/ the contacts tab which you
mention; but in the live lm21 4.4 General preferences mentions locating
the tabs (top or otherwise) whereas the preferences for Contacts doesn't
mention tabs.

--
Mike Easter

On 2023-02-02, Nic <Nic@none.net> wrote:
> On 2/2/23 9:37 AM, Dan Purgert wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA512
>>
>> On 2023-02-02, Nic wrote:
>>> I am using Mint 19.1 Tessa and have updated my kernal to 5.4.0-137.
>>> Supposedly the kernal is only supported until April 2023. What happens
>>> after April 2023?
>> No, it's not "the kernel" that is going EOL, but rather that the entire
>> Linux Mint 19 release set (19, 19.1, 19.2, 19.3) goes EOL in April. It
>> means that the version is no longer supported, and that it will no
>> longer receive security updates.
>>
>> Best course of action is to upgrade to LM 20.
>>
>>
>> -----BEGIN PGP SIGNATURE-----
>>
>> iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmPbywAACgkQbWVw5Uzn
>> KGBWlQ/8DGpLaJak/uB6AUnoTGwyu6g9uTQHQ0UtsHWVx6qCTblTPYOQHs2t2kZw
>> Wb0zwmNMPgT25jRbu/fNFw1dCFkAX2yJDRY7n9uOO5yPde5lf1aPE4kOcIUSfhyg
>> XzcI11S1uc4WwIbtCp3bvUnktCWTuVRNt3v696FSPNOzDVFELQkAXtoVkmt9WF92
>> a46CzUglcMAlfXG4VqoM9TI6bvScYKVyetfcc336QnV/Y2oKmCCw+CbKNGTd0KhC
>> XVa8KDvwqQ2CZdZbkYUx5hZ3AN3Cqcwce7hUc2wD6hISNjVyiheSRTmrUoxd130X
>> 3dLvRBV09z7XVHBLgKiuSh3rk+QOhK9z39i5DoQS4EVQq2XxnuZMoLhcuxcRvGgq
>> +TCGWhxQLt8F2gLSZZMPXxfIXDS+BZMJs1QgQQNmcz6/WUn4i1oxjGChgFyu7nkq
>> ofJLO4L874VTJLJ2ysTW1Z/aO/tiYxYzzDQrXGCaq9N7N7nm0th7izOCMlbx5h3J
>> nS23xJjtwQtIVv/7y9Zdj0dnbPqfvyrqwMv4XkfwOCccFds7aaXqCTuOxDk0d2qY
>> CJ6iz3kXujXLQZquJs4c2HYXDv9r4sonCWoedVKB/VNC1crS4Y5SM9W27aSvVW+g
>> kjAPiO5sdtoCOK2RPkex+uB16JnrT7uJiWf0YazmBfMxy+D3xJc=
>> =aUhM
>> -----END PGP SIGNATURE-----
>>
> I noticed that you chose upgrade to LM 20 and not LM21, and ignored a
> clean install.
>
> I did a live try of LM21 and installed 1 program that I use frequently.
> The program is called OSMO. On my current version I have a contacts tab,
> whereas the new version installed on LM21 did not have this contact tab.
> This for me was a deal breaker. I will try out LM20 to see if it has the
> same problem.
>
Go on be a devil and install LM 20.3

Why do you not just upgrade via the instructions

https://linuxmint-user-guide.readthedocs.io/en/latest/upgrade-to-mint-20.html

Uses the upgrade tool.

On 2/2/23 10:40 PM, Gordon wrote:
> On 2023-02-02, Nic <Nic@none.net> wrote:
>> On 2/2/23 9:37 AM, Dan Purgert wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA512
>>>
>>> On 2023-02-02, Nic wrote:
>>>> I am using Mint 19.1 Tessa and have updated my kernal to 5.4.0-137.
>>>> Supposedly the kernal is only supported until April 2023. What happens
>>>> after April 2023?
>>> No, it's not "the kernel" that is going EOL, but rather that the entire
>>> Linux Mint 19 release set (19, 19.1, 19.2, 19.3) goes EOL in April. It
>>> means that the version is no longer supported, and that it will no
>>> longer receive security updates.
>>>
>>> Best course of action is to upgrade to LM 20.
>>>
>>>
>>> -----BEGIN PGP SIGNATURE-----
>>>
>>> iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmPbywAACgkQbWVw5Uzn
>>> KGBWlQ/8DGpLaJak/uB6AUnoTGwyu6g9uTQHQ0UtsHWVx6qCTblTPYOQHs2t2kZw
>>> Wb0zwmNMPgT25jRbu/fNFw1dCFkAX2yJDRY7n9uOO5yPde5lf1aPE4kOcIUSfhyg
>>> XzcI11S1uc4WwIbtCp3bvUnktCWTuVRNt3v696FSPNOzDVFELQkAXtoVkmt9WF92
>>> a46CzUglcMAlfXG4VqoM9TI6bvScYKVyetfcc336QnV/Y2oKmCCw+CbKNGTd0KhC
>>> XVa8KDvwqQ2CZdZbkYUx5hZ3AN3Cqcwce7hUc2wD6hISNjVyiheSRTmrUoxd130X
>>> 3dLvRBV09z7XVHBLgKiuSh3rk+QOhK9z39i5DoQS4EVQq2XxnuZMoLhcuxcRvGgq
>>> +TCGWhxQLt8F2gLSZZMPXxfIXDS+BZMJs1QgQQNmcz6/WUn4i1oxjGChgFyu7nkq
>>> ofJLO4L874VTJLJ2ysTW1Z/aO/tiYxYzzDQrXGCaq9N7N7nm0th7izOCMlbx5h3J
>>> nS23xJjtwQtIVv/7y9Zdj0dnbPqfvyrqwMv4XkfwOCccFds7aaXqCTuOxDk0d2qY
>>> CJ6iz3kXujXLQZquJs4c2HYXDv9r4sonCWoedVKB/VNC1crS4Y5SM9W27aSvVW+g
>>> kjAPiO5sdtoCOK2RPkex+uB16JnrT7uJiWf0YazmBfMxy+D3xJc=
>>> =aUhM
>>> -----END PGP SIGNATURE-----
>>>
>> I noticed that you chose upgrade to LM 20 and not LM21, and ignored a
>> clean install.
>>
>> I did a live try of LM21 and installed 1 program that I use frequently.
>> The program is called OSMO. On my current version I have a contacts tab,
>> whereas the new version installed on LM21 did not have this contact tab.
>> This for me was a deal breaker. I will try out LM20 to see if it has the
>> same problem.
>>
> Go on be a devil and install LM 20.3
>
> Why do you not just upgrade via the instructions
>
> https://linuxmint-user-guide.readthedocs.io/en/latest/upgrade-to-mint-20.html
>
> Uses the upgrade tool.

I booted the LM 20 version and OSMO has the contacts tab. I guess my
next question is, the version 19 of LM that I am using is only supported
until April 2023, is there any chance that the kernel will be updated at
some later date? Or can I use a kernel intended for LM20 or LM21 in LM19?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2023-02-02, Nic wrote:
> On 2/2/23 9:37 AM, Dan Purgert wrote:
>> [...]
>> Best course of action is to upgrade to LM 20.
> I noticed that you chose upgrade to LM 20 and not LM21, and ignored a
> clean install.

Well, sure; you can in-place upgrade from 19.3 to 20. That can be
easier / more straight-forward than paving over to install from the live
image.

>
> I did a live try of LM21 and installed 1 program that I use frequently.
> The program is called OSMO. On my current version I have a contacts tab,
> whereas the new version installed on LM21 did not have this contact tab.
> This for me was a deal breaker. I will try out LM20 to see if it has the
> same problem.

That's not a Linux Mint problem. Your best course of action would be to
contact the devteam to see why they pulled out he feature you liked.

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmPdHQMACgkQbWVw5Uzn
KGBvkg//atpqtoxv+hj91SOqJi0Mpf7qDcwa3G6YEhTqfnUKFS56VgYA6q+gcKjz
NO1K27j+zqIR7dwuE3CJLA4N6jqoAZdYvSKUW0rOTHlPgbovpCVAK0rmaodEKFPD
mzTJiEFMPSEfhvQipRY9vL3oAkjfDo+ubKF48AntK07s1Qt75iPz1pfniu9Heg9Z
2iyna6lt8H3+AjTQDxlynWV5DXXZxO0JReRaZbUXmT+6wCirWBpzdb9Miwg28058
RM6JZk2E0jd0F1ey1DclCl1N+KpTWsSA53LRzGZQ4a1+ruIe9jVUnRZBFNIdPaXD
pcpkGjN4eNvCEvS3oVSgIqmZthVBFzXKKI/qCdfqE6R3vTNHD8gfEJXdJQ8xPc4j
ndSCmmHxto9evY1qQxSogevjhmyY9OwZAXu7pXhWBVBFpp1fhcXwnVJjrOUmIrmI
PXzAZ9cjfL8OQjvQxcapr3yYbnj/IvA53Qd60dIkdGRxe11hoG7uCFMeVFN0TMYY
9+y9OG1/N6ErpJSxkwGWKQD7hAWC/3JD5peaAIW3gzckrnuFXBgQXxcgqe+iU/7Y
2m3SKBrwdSaTTo7qSJKR6Tap4n0Mw9LRZsxnI8UUg42AAAAKYUy5Izf5IuBKzW1G
/VehhdL292HCGA67mbKu8GisHmvaZTrTPOntBcqMUw2VcKLyf6c=
=iOAi
-----END PGP SIGNATURE-----

--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2023-02-03, Nic wrote:
>
> I booted the LM 20 version and OSMO has the contacts tab. I guess my
> next question is, the version 19 of LM that I am using is only supported
> until April 2023, is there any chance that the kernel will be updated at
> some later date? Or can I use a kernel intended for LM20 or LM21 in LM19?

No, "End Of Life" means exactly that. The release is _dead_ in April.

You _MUST_ move to a version that is still supported. LM20 is supported
until 2025; LM21 is supported until 2027.

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmPdHdwACgkQbWVw5Uzn
KGBGlhAAt66WmiUZL0NluTf6DtYsW+OKT5kaherhuWX1pQ/GVoPOChjR7EthMPTu
WkeUXjfSF4InlysBJgbwF7qRS3JJu09K4WkBkbhkzAbmlcAbbK77xnpXFDBDhvj8
GUn6NDgAivWWK5obSIZ8Ex8xUMILz59O3ZLCJpcRfEsu1KUOQu2KdaJFO1Z0cJpS
ISJgddn8cWAc7C0hK7W1QtfjydmsKG5rmZa5ZudP///XCHbcElR+l7kKYxAOJvED
eTyJsId4+jk8yx/cjBigrVzSOVWFuWLUFoUDeEOlO4XTjrhyOgBtq5zdE50Tmj/J
vv5S2PtLlqk5GV9S+93ewAyV5ZT0u8pxz9w3ibBsh9vD8Ur24IZUUORtava5DsOZ
8HsD3gvRAB4nPO51HRIXNllVVtPSDm95x+pCOT6z1u+DqBpXCfdYG9KeQ2haHLDt
SoU4mirRrZiCpIfH3b87RtdW2Y08WTjnkbNE2uV0SOS/aHKHQHJRePwm6dq+RX61
1OthFizaRv9ILeat6oqlrdeysyG89AK/o/SUyLhhIa4KtZoP6/bR4SXJpICaX2hb
MpLKVLEk+csDoM/b0wptboZaiWKREzI+o2py5cg7EzR6/KMe5n8+CKlCxiW0X2gV
JY3TcMO1WV5j095fwo1RBblu118qXta0OgzwT7wVJ8Hd3jvHBOc=
=a/yL
-----END PGP SIGNATURE-----

--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

On 2/3/23 09:40, this is what Dan Purgert wrote:
> On 2023-02-02, Nic wrote:
>> On 2/2/23 9:37 AM, Dan Purgert wrote:
>>> [...]
>>> Best course of action is to upgrade to LM 20.
>> I noticed that you chose upgrade to LM 20 and not LM21, and ignored a
>> clean install.
>
> Well, sure; you can in-place upgrade from 19.3 to 20. That can be
> easier / more straight-forward than paving over to install from the live
> image.
>
>
>> I did a live try of LM21 and installed 1 program that I use frequently.
>> The program is called OSMO. On my current version I have a contacts tab,
>> whereas the new version installed on LM21 did not have this contact tab.
>> This for me was a deal breaker. I will try out LM20 to see if it has the
>> same problem.
>
> That's not a Linux Mint problem. Your best course of action would be to
> contact the devteam to see why they pulled out he feature you liked.
>
>
>

Why do your PGP sign your message posts?

On 2/3/23 9:43 AM, Dan Purgert wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On 2023-02-03, Nic wrote:
>> I booted the LM 20 version and OSMO has the contacts tab. I guess my
>> next question is, the version 19 of LM that I am using is only supported
>> until April 2023, is there any chance that the kernel will be updated at
>> some later date? Or can I use a kernel intended for LM20 or LM21 in LM19?
> No, "End Of Life" means exactly that. The release is _dead_ in April.
>
> You _MUST_ move to a version that is still supported. LM20 is supported
> until 2025; LM21 is supported until 2027.
>
> -----BEGIN PGP SIGNATURE-----
>
> iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmPdHdwACgkQbWVw5Uzn
> KGBGlhAAt66WmiUZL0NluTf6DtYsW+OKT5kaherhuWX1pQ/GVoPOChjR7EthMPTu
> WkeUXjfSF4InlysBJgbwF7qRS3JJu09K4WkBkbhkzAbmlcAbbK77xnpXFDBDhvj8
> GUn6NDgAivWWK5obSIZ8Ex8xUMILz59O3ZLCJpcRfEsu1KUOQu2KdaJFO1Z0cJpS
> ISJgddn8cWAc7C0hK7W1QtfjydmsKG5rmZa5ZudP///XCHbcElR+l7kKYxAOJvED
> eTyJsId4+jk8yx/cjBigrVzSOVWFuWLUFoUDeEOlO4XTjrhyOgBtq5zdE50Tmj/J
> vv5S2PtLlqk5GV9S+93ewAyV5ZT0u8pxz9w3ibBsh9vD8Ur24IZUUORtava5DsOZ
> 8HsD3gvRAB4nPO51HRIXNllVVtPSDm95x+pCOT6z1u+DqBpXCfdYG9KeQ2haHLDt
> SoU4mirRrZiCpIfH3b87RtdW2Y08WTjnkbNE2uV0SOS/aHKHQHJRePwm6dq+RX61
> 1OthFizaRv9ILeat6oqlrdeysyG89AK/o/SUyLhhIa4KtZoP6/bR4SXJpICaX2hb
> MpLKVLEk+csDoM/b0wptboZaiWKREzI+o2py5cg7EzR6/KMe5n8+CKlCxiW0X2gV
> JY3TcMO1WV5j095fwo1RBblu118qXta0OgzwT7wVJ8Hd3jvHBOc=
> =a/yL
> -----END PGP SIGNATURE-----
>
Are you saying that it will _stop_ working?

Nic wrote:
> I booted the LM 20 version and OSMO has the contacts tab.

That is osmo 4.2.

> I guess my next question is, the version 19 of LM that I am using is
> only supported until April 2023,
Correct.

> is there any chance that the kernel will be updated at some later
> date? Or can I use a kernel intended for LM20 or LM21 in LM19?
You are getting the 'kernel' term/condition/version 'mixed up' w/ the
*distro* (LM) version/term 19.x, 20.x, 21.x.

The 'essential' here, in terms of /support/ is your *distro* -- don't
'say' kernel in this context. That is another different subject which
isn't actually under discussion in this thread you have started.

Your thread is actually about a version of osmo, 4.2 vs 4.4 which 4.2 is
'natively' in LM 19 whereas LM 20 & 21 natively have the 4.4 v.

The reason that people are arguing for upping your LM 19 is because it
isn't long until its support ends in about 2 mo.

It is also possible to use a 'retro' osmo 4.2 in a 'newer' LM such as 20
or 21, but no one has started talking about that yet.

--
Mike Easter

Nic wrote:
> Are you saying that it will _stop_ working?

LM 19.x will not stop working when its support ends, but it will no
longer receive 'essential' updates.

It is quite possible to continue to use a distro in that condition, but
the potential for security breaches will progressively grow. That is
not 'smart'.

Nowadays, the 'strategy' for distro/s like LM (non-rolling) to be
upgraded w/o breakage is better than in the past, but not 'perfect'
because the upgrade route cannot 'predict' how you may have tweaked your
personal touches for the distro.

One of your options is to up your LM distro and employ a retro v. of
osmo instead of the one that is in the native repo/s.

--
Mike Easter

Mike Easter wrote:
> One of your options is to up your LM distro and employ a retro v. of
> osmo instead of the one that is in the native repo/s.

Since you are currently running a LM 19.x, you could dl the osmo 4.2
package from your repo/s w/ such as

sudo apt install --download-only osmo

.... and then do your little 'trick' you did earlier where you boot a
live LM 20 or 21, and then install that dl/ed & saved .osmo 4.2 .deb
into the live such as LM 21.

That experiment, to see if the retro 4.2 osmo 'works' ok in the newer LM
would be easier than an alternative which would be to use the source for
osmo 4.2 and compile it for LM 21.

The other earlier advice about interacting w/ the osmo dev about your
opinion of the desirability of contact tabs in the newer 4.4 v might
result in such an 'improvement' in the current osmo.

--
Mike Easter

Oops. I failed to appreciate part of a Nic report.

Mike Easter wrote:
> Nic wrote:
>> I booted the LM 20 version and OSMO has the contacts tab.
>
> That is osmo 4.2.
>
> Your thread is actually about a version of osmo, 4.2 vs 4.4 which 4.2 is
> 'natively' in LM 19 whereas LM 20 & 21 natively have the 4.4 v.
>
Not correct.

I should have realized that both LM 19 & 20 have 4.2. Only 21 has 4.4;
according to what you say above and what I saw for myself w/ a LM 21 live.

> The reason that people are arguing for upping your LM 19 is because it
> isn't long until its support ends in about 2 mo.
>
Since LM 20 is the 'natural' upgrade path for your LM 19, and since LM
20 has osmo 4.2 in its universal repo, the upgrade to LM 20 would
represent a smoother transition for you, and LM 20 is supported until
2025 Apr, which is certainly better than 2023 Apr.

--
Mike Easter

On 2/3/23 12:14 PM, Mike Easter wrote:
> Nic wrote:
>> Are you saying that it will _stop_ working?
>
> LM 19.x will not stop working when its support ends, but it will no
> longer receive 'essential' updates.
>
> It is quite possible to continue to use a distro in that condition,
> but the potential for security breaches will progressively grow.  That
> is not 'smart'.
>
> Nowadays, the 'strategy' for distro/s like LM (non-rolling) to be
> upgraded w/o breakage is better than in the past, but not 'perfect'
> because the upgrade route cannot 'predict' how you may have tweaked
> your personal touches for the distro.
>
> One of your options is to up your LM distro and employ a retro v. of
> osmo instead of the one that is in the native repo/s.
>
>
>
Good point, a retro version, if available. Looking at this more
accurately, I tried to upgrade from LM 19.1 to LM19.3 in order to
consider the upgrade to LM 20, but I got a failure. So for now I am
stuck with LM19.1, and a future clean install to LM21.

On 2/3/23 1:01 PM, Mike Easter wrote:
> Oops. I failed to appreciate part of a Nic report.
>
> Mike Easter wrote:
>> Nic wrote:
>>> I booted the LM 20 version and OSMO has the contacts tab.
>>
>> That is osmo 4.2.
>>
>> Your thread is actually about a version of osmo, 4.2 vs 4.4 which 4.2
>> is 'natively' in LM 19 whereas LM 20 & 21 natively have the 4.4 v.
>>
> Not correct.
>
> I should have realized that both LM 19 & 20 have 4.2.  Only 21 has
> 4.4; according to what you say above and what I saw for myself w/ a LM
> 21 live.
>
>> The reason that people are arguing for upping your LM 19 is because
>> it isn't long until its support ends in about 2 mo.
>>
> Since LM 20 is the 'natural' upgrade path for your LM 19, and since LM
> 20 has osmo 4.2 in its universal repo, the upgrade to LM 20 would
> represent a smoother transition for you, and LM 20 is supported until
> 2025 Apr, which is certainly better than 2023 Apr.
>
>
>
Could you elaborate what  security issues would occur if a person
continued to use LM19 past April. As a casual user and not running a
server or website, how will continuing to use LM19.1  compromise my
security?