[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+icZUWsffXuBUTcjLhrGvDKRp8fut=k_HdyhQ-QLZHjfXpqmg@mail.gmail.com>
Date: Sat, 2 Jan 2021 12:26:30 +0100
From: Sedat Dilek <sedat.dilek@...il.com>
To: Bernd Petrovitsch <bernd@...rovitsch.priv.at>
Cc: Masahiro Yamada <masahiroy@...nel.org>,
Pavel Machek <pavel@....cz>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 5.11-rc1
On Sat, Jan 2, 2021 at 12:05 PM Bernd Petrovitsch
<bernd@...rovitsch.priv.at> wrote:
>
> On Sat, 2021-01-02 at 10:13 +0100, Sedat Dilek wrote:
> [...]
> > To be honest I wondered why there were no more reports on this.
>
> Perhaps I'm not the only one who has /sbin and /usr/sbin in the
> $PATH of normal accounts too (and idk what's the default
> behaviour of distributions is - my .bashrc "fixes" the
> $PATH).
>
I was thinking more towards maxim/dictum:
"Never break userspace!" or "It worked before but now it is not."
Think of automated kernel build and test setups based on Debian.
Debian/testing AMD64 has...
[ /etc/login.defs ]
# *REQUIRED* The default PATH settings, for superuser and normal users.
#
# (they are minimal, add the rest in the shell startup files)
ENV_SUPATH
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
ENV_PATH PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
IMHO users should not need to fix their environment.
( The discussion is a bit obsolete as we now have a fix. )
- Sedat -
Powered by blists - more mailing lists