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@xxxxxxxxx> wrote:
Keith Daniels wrote:
> Note I am not Anti-Russian, in fact I am addicted to news on RT.com
> (according to my friends anyway).
>
Same here, but do you read Russian? Because also other nations use the same
alphabet
> I installed altlinux-p7-sysv-tde-20160312-x86_64.iso trinity version
> thinking about switching over to it:
>
> I played with it for a couple of days and decided it would be more work
> than I wanted to do, to customize it to what I wanted, which was too bad
> since I liked it.
>
> I then deleted it and installed the live Q4OS version. I liked it too but
> did not want to be forced to use LVM. While testing Q4OS I noticed that
> the large blue box with two Russian words in it thatI first saw after
> install ALT_Linux, was still appearing on the screen--right after the
> power came on.
>
which are the words?
> I thought maybe that during the live install it was put on the boot
> section or the disk, or possibly some where else on the hard drive that
> didn't get erased, so I used dd to zero out those sections as well as the
> entire
> drive, and created a new partition with gparted. Then the first time I
> restarted the computer it was gone. But when I pushed the reset button, it
> was there again and after that all power on events caused it to reappear.
>
> About this time I started getting nervous, and wanted to know where was
> this image stored on my computer and what activated it at startup.
>
> So. I pulled the hard drive and started the computer up with no usb or
> hard
> drive attached and still got the logo. This meant that the image was not
> on the hard drive. So I thought it might be in the volatile ram on the
> BIOS chip. I used the jumpers to clear the BIOS chip and just for good
> measure removed the chip and let it sit for 30 minutes. Nothing changed
> when I put it back in and started up the computer, the image still
> appeared.
>
> The only thing I can think of that would permit this scenario to work,
> would be if they burned the image into the non-volatile part of the BIOS
> chip.
>
> I don't think they are hacking my computer, I think they are just showing
> off. But the idea of someone burning code onto my BIOS chip, or hiding it
> somewhere I can't find it--doesn't make me happy. They could have put
> anything, including a back door access to my computer in it.
>
> Has anyone else had or noticed this problem when installing ALT_Linux
> versions? And does anyone have any other ideas as to what I could test or
> other things to try that might remove it?
>
why not try debian
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: trinity-devel-help@xxxxxxxxxxxxxxxxxxxxxxxxxx
Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
