From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: kumba@gentoo.org
Subject: Re: [gentoo-dev] [PATCH] use.desc: add global USE flag 'split-sbin'
Date: Wed, 16 Oct 2019 10:39:23 -0500 [thread overview]
Message-ID: <20191016153923.GA29013@whubbs1.dev.av1.gaikai.org> (raw)
In-Reply-To: <4fdaaef8-b25f-ee2f-505e-d647251d6af9@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 4175 bytes --]
On Tue, Oct 15, 2019 at 11:08:14PM -0400, Joshua Kinard wrote:
> On 10/15/2019 13:34, David Seifert wrote:
> > On Tue, 2019-10-15 at 12:04 -0400, Mike Gilbert wrote:
> >> On Tue, Oct 15, 2019 at 12:02 PM Mike Gilbert <floppym@gentoo.org>
> >> wrote:
> >>> On Tue, Oct 15, 2019 at 8:00 AM David Seifert <soap@gentoo.org>
> >>> wrote:
> >>>> On Sun, 2019-10-13 at 12:33 -0400, Mike Gilbert wrote:
> >>>>> On Sat, Oct 12, 2019 at 1:52 PM David Seifert <soap@gentoo.org>
> >>>>> wrote:
> >>>>>> On Sat, 2019-10-12 at 19:01 +0200, Dennis Schridde wrote:
> >>>>>>> On Samstag, 12. Oktober 2019 18:02:28 CEST William Hubbs
> >>>>>>> wrote:
> >>>>>>>> On Sat, Oct 12, 2019 at 01:11:49PM +0200, Michał Górny
> >>>>>>>> wrote:
> >>>>>>>>> On Sat, 2019-10-12 at 13:00 +0200, David Seifert wrote:
> >>>>>>>>>> * Some distros have not just merged / and /usr, they
> >>>>>>>>>>
> >>>>>>>>>> have also merged /usr/bin and /usr/sbin. By giving
> >>>>>>>>>> users the choice of merging */bin and */sbin,
> >>>>>>>>>> Gentoo follows suit.
> >>>>>>>>>
> >>>>>>>>> What about the scenario when /bin has been merged with
> >>>>>>>>> /usr/sbin
> >>>>>>>>> and /sbin with /usr/bin? ;-P
> >>>>>>>>
> >>>>>>>> I also don't see the need for something like this. The
> >>>>>>>> idea of
> >>>>>>>> the
> >>>>>>>> /usr
> >>>>>>>> merge is to have all binaries available in one place, and
> >>>>>>>> there
> >>>>>>>> really
> >>>>>>>> is not a good justification for separating bin from sbin.
> >>>>>>>
> >>>>>>> Do I read this correctly? USE=-split-usr currently means
> >>>>>>> that
> >>>>>>> /bin,
> >>>>>>> /sbin, /
> >>>>>>> usr/bin and /usr/sbin point to the same directory?
> >>>>>>>
> >>>>>>> If that is not the case, then I agree that users should
> >>>>>>> have the
> >>>>>>> possibility
> >>>>>>> to set it up like this and USE=-split-sbin should be
> >>>>>>> supported.
> >>>>>>>
> >>>>>>> --Dennis
> >>>>>>
> >>>>>> I agree, I wasn't aware that USE=-split-usr implies the
> >>>>>> complete 2-
> >>>>>> level (/usr and *sbin) merge. In that case, all of this is
> >>>>>> obsolete.
> >>>>>
> >>>>> That was NOT my intention when I introduced the split-usr USE
> >>>>> flag.
> >>>>>
> >>>>> For bin/sbin, I would prefer to drop any conflicting links
> >>>>> unconditionally. Do you have examples of scenarios where this
> >>>>> is not
> >>>>> possible?
> >>>>>
> >>>>
> >>>> William has confirmed on IRC that USE=-split-usr performs the
> >>>> complete
> >>>> Fedora-esque /usr merge (which makes sense IMO).
> >>>
> >>> William's opinion is not the only one that matters.
> >>
> >> Sorry, I guess you are referring to the behavior baselayout? That
> >> doesn't necessarily align with the global usage.
> >>
> >
> > https://gitweb.gentoo.org/proj/baselayout.git/tree/Makefile#n93
> >
> > Clearly the usr-merge in baselayout intends to merge all these 4
> > directories. There is currently no option to merge /usr and / but keep
> > /bin and /sbin separate, so the most parsimonious solution here is to
> > assume that usr-merge semantics in Gentoo is about merging all 4
> > directories.
>
> What is the source or origin point of the desire to merge /sbin into /bin?
> I know Fedora/RedHat championed the /usr/[s]bin into /[s]bin bit, but this
> is the first I've heard of trying to put all executables in one spot. I
> have my doubts about such an idea, but want to see what the rationale is
> this time before writing the idea off to the funny farm.
>
> My understanding for the separation was system binaries that only the
> superuser needs to touch go into /sbin and everything else into /bin. This
> allowed for unpriv user PATHs to exclude /sbin (and in times antiquity, also
> exclude /usr/sbin).
Back in the day, the s in /sbin and /usr/sbin meant static, not super
user. All binaries in those directories were statically linked.
https://www.osnews.com/story/25556/understanding-the-bin-sbin-usrbin-usrsbin-split/
http://lists.busybox.net/pipermail/busybox/2010-December/074114.html
The tl;dr is that the meaning of /sbin and /usr/sbin was lost years ago.
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-10-16 15:39 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 [this message]
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
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=20191016153923.GA29013@whubbs1.dev.av1.gaikai.org \
--to=williamh@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=kumba@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