Re: Likely Bash bug

[Jay]

   Thanks for your feedback.

   For reference, other details are as follows:

   In addition to bash, the distribution includes sh and ash
   shells/scripts.

   ▶—— Linux Kernel ——◀
   Kernel Release: 4.19.23
   Build Date: Tue Feb 19 15:07:58 GMT 2019
   Build GCC: 7.3.0
   OS Support: GNU/Linux
   Architecture: x86_64
   SMP Enabled: Yes
   Kernel Command Line:
   psave=/Bionicpup64save-jay pmedia=ataflash pfix=fsck  #pmedia=atahd
   ▶—— Distro Specifications ——◀
   Distro: bionicpup64 8.0
   Window Manager: JWM v2.3.7
   Desktop Start: xwin jwm
   Development:
    Bash: 4.4.19
    Geany: 1.33
    Gtkdialog: 0.8.4
    Perl: 5.26.1
    Python: 2.7.15rc1
    Yad: 0.40.0 (GTK+ 2.24.32)
    --
    busybox: 1.29.3
    dhcpcd: 6.6.2
    Devx GCC: (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
    Glibc: 2.27
    OpenSSL: 1.1.0g  2 Nov 2017, built on: reproducible build, date
   unspecified
    wpa_supplicant: 2.6
   ▶—— /etc/DISTRO_SPECS ——◀
   One or more words that identify this distribution:
    • DISTRO_NAME='bionicpup64'
   Version number of this distribution:
    • DISTRO_VERSION=8.0
   The distro whose binary packages were used to build this distribution:
    • DISTRO_BINARY_COMPAT='ubuntu'
   Prefix for some filenames: exs: bionicpup64save.2fs,
   bionicpup64-7.9.8.sfs
    • DISTRO_FILE_PREFIX='bionicpup64'
   The version of the distro whose binary packages were used to build this
   distro:
    • DISTRO_COMPAT_VERSION='bionic'
   Read by /usr/bin/xwin to bypass Xorg Wizard at first boot:
    • DISTRO_XORG_AUTO='yes'
    • DISTRO_KERNEL_PET='Huge_Kernel'
    • DISTRO_DB_SUBNAME='bionic64'
    • WOOF_VERSION=8
    • DISTRO_TARGETARCH='x86_64'
    • BUILD_FROM_WOOF='testing;c3552eef;2019-02-25 04:50:55 +0800'
   Puppy default filenames...
   Note, the 'SFS' files below are what the 'init' script in initrd.gz
   searches for,
   For the partition, path and actual files loaded, see PUPSFS and ZDRV in
   /etc/rc.d/PUPSTATE
    • DISTRO_PUPPYSFS='puppy_bionicpup64_8.0.sfs'
    • DISTRO_ZDRVSFS='zdrv_bionicpup64_8.0.sfs'
    • DISTRO_FDRVSFS='fdrv_bionicpup64_8.0.sfs'
    • DISTRO_ADRVSFS='adrv_bionicpup64_8.0.sfs'
    • DISTRO_YDRVSFS='ydrv_bionicpup64_8.0.sfs'
    • DISTRO_PUPPYDATE='Feb 2019'
   Multiarch distros, such as Ubuntu, will have this. ex:
   /usr/lib/i386-linux-gnu, so DISTRO_ARCHDIR=i386-linux-gnu
    • DISTRO_ARCHDIR='x86_64-linux-gnu'
   ▶—— /etc/os-release ——◀
   NAME=Puppy
   VERSION="8.0"
   ID=puppy_bionicpup64
   VERSION_ID=8.0
   PRETTY_NAME="bionicpup64 8.0"
   ANSI_COLOR="0;34"
   CPE_NAME="cpe:/o:puppy:puppy_linux:8.0"
   HOME_URL=[1]"http://puppylinux.com/";
   SUPPORT_URL=[2]"http://www.murga-linux.com/puppy/index.php";
   BUG_REPORT_URL=[3]"https://github.com/puppylinux-woof-CE/woof-CE";

   Best Regards.

   On 3/16/2021 11:59 PM, Robert Elz wrote:

    Date:        Tue, 16 Mar 2021 18:01:24 -0400
    From:        Jay via Bug reports for the GNU Bourne Again SHell [4]<bug-bash
@gnu.org>
    Message-ID:  [5]<86f1f224-2930-ee73-5431-6e130d92f3e9@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

References

   1. http://puppylinux.com/
   2. http://www.murga-linux.com/puppy/index.php
   3. https://github.com/puppylinux-woof-CE/woof-CE
   4. mailto:bug-bash@gnu.org
   5. 86f1f224-2930-ee73-5431-6e130d92f3e9@aim.com">mailto:86f1f224-2930-ee73-5431-6e130d92f3e9@aim.com