My fault... It was kinda funny when I finally found out what had happened. It wasn't Alt_Linux at all, they had nothing to do with it. When I started the installation of ALT_Linux I moved the spare testing computer into my room to work on it and borrowed my son's monitor because I didn't have a spare one. The first thing I installed was ALT_Linux. Since the install was going to wipe the system I didn't pay attention to the install startup. Later when I saw the Russian Language box on the screen, I thought "why not, it's a Russian build". Afterwards, when I finished the second Q4OS install, over the original ALT_Linux install, I noticed the box was still there. This led to hours of trying to figure out why, which I gave up on. So, I took his monitor back about an hour ago, plugged it in and started his computer up, and there was the box with the Russian text. Duh..... I then asked him if he had seen this before and he said: "Sure, I can't get rid of it." I growled... "What do you mean?" He said well, one day I noticed you could change the language of the monitor and was playing around with it and turned on the Russian and then, since I can't read Russian, I couldn't figure out how to put it back to English and left it like that..." Sometimes I wonder why I had children.... Sorry for the bother everyone. As for Debian, I had been using it for years. Both my son and I wanted to upgrade and I upgraded my system with Debian first. The install went well until I started testing my bash scripts, which I have hundreds of. Half of them would not work with permission denied error messages from internal calls inside the scripts. All the file and directory permissions looked correct and they had been working fine before I upgraded. I decided it might be ACL issues, and discovered that Buster turns it on by default. So I started trying to learn about it and testing what I could. It was either broken or did not install correctly. The tools did not give the expected results, nor match the instructions on how to use them. I could not make calls to bash nor would tools like grep work The ACL tools said ACL was not activated but I read where Debian activated them by default. By this time I was frustrated and decided to check out some other distros--but not on my computer. Which led to the ALT_Linux fiasco and more frustration... Another frustration that happened after the above... was that, while zeroing out a USB stick so I would have a clean stick to put the Ubuntu/Trinity ISO on--my next test... some how my SSD drive got it's partition wiped an all its info wiped. I have no clue how that happened, The drive specified was correct, I watched the USB light blink while it was being zeroed out, so I know it wasn't me putting in the wrong drive spec. I have backups for most of it so it is not a major issue. All in all it was a bad 76th birthday... Keith On Sun, May 10, 2020 at 9:34 PM deloptes <deloptes(a)gmail.com> wrote:

Glad you enjoyed it. Real life is sometimes the funniest of all. BTW I recovered everything lost on the SSD drive. Being highly paranoid, I run rdiff-backup twice a day from crontab. It had backed up the SSD completely a couple of hours before it died and was smart enough to not to do anything after the drive died. Keith On Mon, May 11, 2020 at 7:02 AM Marvin Jones via trinity-devel < trinity-devel(a)lists.pearsoncomputing.net&gt; wrote: