From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: rfc: adding sbin directories to PATH for all users
Date: Thu, 26 Nov 2015 15:03:57 +0000 (UTC) [thread overview]
Message-ID: <pan$4d5e$f1e9ba0d$c5ce1d19$ea5eb2a1@cox.net> (raw)
In-Reply-To: 565616E9.9070501@gentoo.org
Kristian Fiskerstrand posted on Wed, 25 Nov 2015 21:15:37 +0100 as
excerpted:
> On 11/25/2015 09:16 PM, Mike Gilbert wrote:
>> On Wed, Nov 25, 2015 at 2:23 PM, Michał Górny <mgorny@gentoo.org>
>> wrote:
>>> On Wed, 25 Nov 2015 11:18:34 -0800 Daniel Campbell <zlg@gentoo.org>
>>> wrote:
>>>> Maybe I'm missing something, but `df` is in /bin. Do you use
>>>> something else to determine free space?
>>>
>>> btrfs fi df
>>
>> In thins case, upstream's build system installs everything in bindir,
>> which I override to /sbin. I think that's where the ebuild was
>> installing things when I inherited it from the previous maintainer.
>>
>> If William's PATH proposal is not implemented, I would be happy to move
>> it all to /bin if so desired. Just file a bug.
>
> If moving it in the first place, wouldn't it go to /usr/bin as not being
> essential to system?
It's essential to system, as btrfs device scan is needed before mounting
a multi-device btrfs, and btrfs check is a an fsck that may be needed to
fix a broken btrfs /usr/ mount.
Else reiserfsck, e2fsck, fsck itself, and others, should be in /usr/sbin,
not in /sbin/.
btrfs is the general userspace binary. Subcommands such as check and
device scan require device privs and don't normally work when run as
ordinary users, but some subcommands such as filesystem df don't need
device privs and work just fine when run as ordinary users.
(Not that I particularly care about the topic of the thread in general,
as here: /sbin -> bin, /usr -> ., so all four locations, /bin, /sbin,
/usr/bin, /usr/sbin, point to the same single /bin, and I no longer have
to worry about which dir something's in, unless I'm checking the
canonical path as installed by the package, for which equery belongs
works nicely. But I'm a btrs user and upstream btrfs list regular so I
care about that angle, thus this reply. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2015-11-26 15:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 17:10 [gentoo-dev] rfc: adding sbin directories to PATH for all users William Hubbs
2015-11-25 17:24 ` Michael Orlitzky
2015-11-25 17:36 ` Kristian Fiskerstrand
2015-11-25 18:05 ` Ulrich Mueller
2015-11-25 18:17 ` Michał Górny
2015-11-25 19:18 ` Daniel Campbell
2015-11-25 19:23 ` Michał Górny
2015-11-25 20:16 ` Mike Gilbert
2015-11-25 20:15 ` Kristian Fiskerstrand
2015-11-26 15:03 ` Duncan [this message]
2015-11-26 15:10 ` [gentoo-dev] " Alan McKinnon
2015-11-25 18:14 ` [gentoo-dev] " William Hubbs
2015-11-25 18:31 ` Ulrich Mueller
2015-11-25 18:38 ` William Hubbs
2015-11-25 18:51 ` Ulrich Mueller
2015-11-25 19:47 ` William Hubbs
2015-11-25 20:53 ` Ulrich Mueller
2015-11-25 21:39 ` William Hubbs
2015-11-25 20:12 ` splite-gentoo
2015-11-25 18:58 ` Mike Gilbert
2015-11-25 20:42 ` Anthony G. Basile
2015-11-26 16:37 ` Peter Stuge
2015-11-25 19:17 ` Nicolas Sebrecht
2015-11-25 21:39 ` Andrew Savchenko
2015-11-26 3:58 ` Mike Gilbert
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='pan$4d5e$f1e9ba0d$c5ce1d19$ea5eb2a1@cox.net' \
--to=1i5t5.duncan@cox.net \
--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