From: Joshua Kinard <kumba@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] use.desc: add global USE flag 'split-sbin'
Date: Sat, 19 Oct 2019 19:36:41 -0400 [thread overview]
Message-ID: <ce3df529-d18a-4551-bc2f-16b495f5145b@gentoo.org> (raw)
In-Reply-To: <20191016181951.GA29746@whubbs1.dev.av1.gaikai.org>
On 10/16/2019 14:19, William Hubbs wrote:
> On Wed, Oct 16, 2019 at 07:17:09PM +0200, Ulrich Mueller wrote:
>>>>>>> On Wed, 16 Oct 2019, William Hubbs wrote:
>>
>>> Back in the day, the s in /sbin and /usr/sbin meant static, not super
>>> user. All binaries in those directories were statically linked.
>>
[snip]
>
> Please read the links I posted before --specifically the comments
> from Rob.
>
> Also, there is this.
>
> https://news.ycombinator.com/item?id=3519952
>
> Tl;dr the bin sbin separation is a historical separation that doesn't
> make sense any longer.
This is just your opinion. Why does it not make sense? Please back that
up. Especially the "historical separation" bit. Why is is historical?
Whom is the authority on that? Is this strictly a Gentoo thing? Is RedHat
doing this? Is someone else? Etc...
FWIW, my opinion is I //like// the separation of /sbin and /bin. In fact,
I'm that old codger who //still// likes keeping /usr/bin and /usr/sbin
separate (yes, on separate partitions). Maybe it's because I'm really poor
at organizing (and staying organized), so dumping everything into one spot
-- which is something I do at home WAY too much -- just strikes me as a bad
idea. Binning stuff into different buckets offers SOME degree of
organization. It also means 'ls -l /bin' is still somewhat readable on a
system with a full desktop installed.
--
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org
rsa6144/5C63F4E3F5C6C943 2015-04-27
177C 1972 1FB8 F254 BAD0 3E72 5C63 F4E3 F5C6 C943
"The past tempts us, the present confuses us, the future frightens us. And
our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic
next prev parent reply other threads:[~2019-10-19 23:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 11:00 [gentoo-dev] [PATCH] use.desc: add global USE flag 'split-sbin' David Seifert
2019-10-12 11:11 ` Michał Górny
2019-10-12 16:02 ` William Hubbs
2019-10-12 17:01 ` Dennis Schridde
2019-10-12 17:52 ` David Seifert
2019-10-13 16:33 ` Mike Gilbert
2019-10-13 16:43 ` Mike Gilbert
2019-10-13 17:38 ` Michał Górny
2019-10-15 12:00 ` David Seifert
2019-10-15 16:02 ` Mike Gilbert
2019-10-15 16:04 ` Mike Gilbert
2019-10-15 17:34 ` David Seifert
2019-10-16 3:08 ` Joshua Kinard
2019-10-16 15:39 ` William Hubbs
2019-10-16 17:17 ` Ulrich Mueller
2019-10-16 18:19 ` William Hubbs
2019-10-17 6:59 ` Ulrich Mueller
2019-10-19 23:36 ` Joshua Kinard [this message]
2019-10-16 9:18 ` Jaco Kroon
2019-10-16 9:48 ` David Seifert
2019-10-16 10:03 ` Jaco Kroon
2019-10-16 10:38 ` Michał Górny
2019-10-16 16:06 ` William Hubbs
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=ce3df529-d18a-4551-bc2f-16b495f5145b@gentoo.org \
--to=kumba@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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