From: David Laight <David.Laight@ACULAB.COM>
To: 'Bernd Petrovitsch' <bernd@petrovitsch.priv.at>,
"sedat.dilek@gmail.com" <sedat.dilek@gmail.com>,
Masahiro Yamada <masahiroy@kernel.org>
Cc: Pavel Machek <pavel@ucw.cz>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: Linux 5.11-rc1
Date: Sun, 3 Jan 2021 17:39:51 +0000 [thread overview]
Message-ID: <3f76e002f96b43de903133b5cd053012@AcuMS.aculab.com> (raw)
In-Reply-To: <b9d3c1063d4c3f9a0cb71442cc92ad77a859d438.camel@petrovitsch.priv.at>
From: Bernd Petrovitsch
> Sent: 02 January 2021 11:05
>
> 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).
Yep, I've pretty much always added sbin to my non-root $PATH
for most of the last 30+ years.
Too much stuff that a 'techie' wants to run non-root is in there.
/usr/bin, /usr/sbin and /usr/lib should have got removed once
disks got large enough that the boot disk (aka /) didn't overflow
required some system files be moved into the 'user' disk.
(The last disks that weren't really big enough were the 600MB ones.
The user's home directories could go into /usr where they belong.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2021-01-03 17:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 7:30 Linux 5.11-rc1 Sedat Dilek
2020-12-28 8:04 ` Sedat Dilek
2020-12-28 15:18 ` Sedat Dilek
2020-12-28 19:40 ` Linus Torvalds
2020-12-28 20:05 ` Sedat Dilek
2021-01-01 16:14 ` Pavel Machek
2021-01-01 18:55 ` Sedat Dilek
2021-01-01 22:31 ` Sedat Dilek
2021-01-02 7:51 ` Masahiro Yamada
2021-01-02 9:13 ` Sedat Dilek
2021-01-02 11:05 ` Bernd Petrovitsch
2021-01-02 11:26 ` Sedat Dilek
2021-01-02 11:57 ` Bernd Petrovitsch
2021-01-02 12:11 ` Sedat Dilek
2021-01-03 17:39 ` David Laight [this message]
2021-01-02 15:30 ` Masahiro Yamada
2020-12-28 15:25 ` Sedat Dilek
2020-12-28 19:45 ` Linus Torvalds
2020-12-28 20:08 ` Sedat Dilek
-- strict thread matches above, loose matches on Subject: below --
2021-01-02 23:26 Ilkka Prusi
2021-01-03 17:45 ` David Laight
2021-01-04 1:47 ` Adam Borowski
2020-12-28 0:04 Linus Torvalds
2020-12-28 15:51 ` Guenter Roeck
2020-12-28 18:59 ` Linus Torvalds
2020-12-28 19:37 ` Kalesh Singh
2020-12-28 20:02 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3f76e002f96b43de903133b5cd053012@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=bernd@petrovitsch.priv.at \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=pavel@ucw.cz \
--cc=sedat.dilek@gmail.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox