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 <mgo...@gentoo.org>
>> wrote:
>>> On Wed, 25 Nov 2015 11:18:34 -0800 Daniel Campbell <z...@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


Reply via email to