public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Borowski <kilobyte@angband.pl>
To: David Laight <David.Laight@ACULAB.COM>
Cc: 'Ilkka Prusi' <ilkka.prusi@pp.inet.fi>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.11-rc1
Date: Mon, 4 Jan 2021 02:47:29 +0100	[thread overview]
Message-ID: <20210104014729.GA13829@angband.pl> (raw)
In-Reply-To: <1930c2a3f18440ccb4890b7b01a33b94@AcuMS.aculab.com>

On Sun, Jan 03, 2021 at 05:45:16PM +0000, David Laight wrote:
> From: Ilkka Prusi
> > Note that /sbin is now just a symlink to /usr/sbin on Debian since 10 (Buster) as per FHS[1][2].
> > 
> > [1] https://wiki.linuxfoundation.org/lsb/fhs
> > [2] https://arstechnica.com/information-technology/2019/09/debian-10-playing-catch-up-with-the-rest-
> > of-the-linux-world-thats-a-good-thing/
> 
> Which is exactly 100% backwards :-)

I agree with you that, if all, it's /usr/sbin which should be a symlink,
to reduce typing and to get rid of a vestige of _The_ Unix machine having
/bin spill to a disk that used to have user homes.

But, /sbin is a symlink on only _some_ Debian installations.  There's
currently a discussion whether to go deeper into this scheme, abandon it
or do nothing.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ .--[ Makefile ]
⣾⠁⢠⠒⠀⣿⡁ # beware of races
⢿⡄⠘⠷⠚⠋⠀ all: pillage burn
⠈⠳⣄⠀⠀⠀⠀ `----

  reply	other threads:[~2021-01-04  1:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-02 23:26 Linux 5.11-rc1 Ilkka Prusi
2021-01-03 17:45 ` David Laight
2021-01-04  1:47   ` Adam Borowski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-12-28  7:30 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
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
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=20210104014729.GA13829@angband.pl \
    --to=kilobyte@angband.pl \
    --cc=David.Laight@ACULAB.COM \
    --cc=ilkka.prusi@pp.inet.fi \
    --cc=linux-kernel@vger.kernel.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