Your message dated Sun, 19 Jan 2020 11:37:02 +0100 with message-id <[email protected]> and subject line Re: bash: $PATH in bash does not include /sbin and /usr/sbin has caused the Debian Bug report #918754, regarding bash: $PATH in bash does not include /sbin and /usr/sbin to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 918754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918754 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: bash Version: 4.4.18-3.1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? On a fresh installation of Debian testing/buster, used the Debian Testing net install CD. Installed the MATE desktop from the selection menu in the installer to install MATE desktop Was trying to install Wi-Fi drivers for my laptop. After installing the drivers, I was trying reinsert the iwlwifi kernel module using modprobe. * What exactly did you do (or not do) that was effective (or ineffective)? root@sanganak:~# adduser rajudev sudo bash: adduser: command not found root@sanganak:~# reboot bash: reboot: command not found root@sanganak:~# modprobe -r iwlwifi bash: modprobe: command not found root@sanganak:~# * What was the outcome of this action? apparently the above commands were not there in there relative PATH's by default root@sanganak:~# echo $PATH /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games * What outcome did you expect instead? Since this was a fresh install of Debian Testing/Buster, the PATH should have contained the paths for /sbin or /usr/sbin etc. by default. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bash depends on: ii base-files 10.1 ii debianutils 4.8.6 ii libc6 2.28-2 ii libtinfo6 6.1+20181013-1 Versions of packages bash recommends: ii bash-completion 1:2.8-5 Versions of packages bash suggests: pn bash-doc <none> -- no debconf information
--- End Message ---
--- Begin Message ---Hello, As already mentioned in this bug report the relevant change is documented in NEWS.Debian. While I no longer maintain util-linux I'm directly responsible for making the change. This change is intentional and aligns su with its documented behaviour. I would also like to stress that using plain 'su' is DANGEROUS because it means you're running a shell as root with the environment inherited from another user. I've over the years seen countless bug reports against different components claiming $SOMETHING completely broke their system beyond all repair, while in fact the problem was that they where running a root shell with environment inherited from their main user account. (Only resetting the PATH does not make it any more safe.) You should thus ALWAYS use 'su -' (or even better, don't use su at all in favour of other alternatives like 'sudo -i'). The use of plain 'su' should be deprecated, but this might be hard or atleast require alot of work since there might be alot of legacy stuff using it. (Many should likely instead be switched to use either runuser or possibly setpriv.) I've already tagged this bug report 'wontfix' and hope the above explanation is clear enough as to why I'm closing this bug report. Regards, Andreas Henriksson
--- End Message ---
