Date: Tue, 16 Mar 2021 18:01:24 -0400
From: Jay via Bug reports for the GNU Bourne Again SHell
<bug-bash@gnu.org>
Message-ID: <86f1f224-2930-ee73-5431-6e130d92f...@aim.com>
First, thanks Lawrence for the translation from RTF, I am one of
the people he intended to help... The RTF form I was going to
simply ignore.
| The system is modern Intel computer, 2018 to 2019 configured in BIOS
| mode.
That should make no difference.
| Operating system is BionicPup64 8.0.
That might. More importantly is probably whatever package management
system it uses. I have no idea what the "ash" the bug report refers to
is (there is an ancient shell of that name, but I cannot imagine any
distribution including that, instead of one of its bug fixed and updated
successors, like say, dash) but it seems to me as if the problem here
relates to whatever package manager was used, that doesn't keep track of
what files various packages touch, and allows one package to overwrite
another's files. That is, not a bash problem at all. The OS might
also have issues, if doing things to files can cause it to crash, but it
is more likely, that ash, whatever it is, did something which caused a
problem, when some of its files were destroyed by the package manager.
Finally, it is generally not a good idea to do anything as "root" (or
using sudo to the same effect) if you aren't 100% confident in what you
are doing.
kre
