public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: Daniel Campbell <zlg@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: adding sbin directories to PATH for all users
Date: Wed, 25 Nov 2015 20:23:55 +0100	[thread overview]
Message-ID: <20151125202355.744e8366.mgorny@gentoo.org> (raw)
In-Reply-To: <5656098A.5040100@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1604 bytes --]

On Wed, 25 Nov 2015 11:18:34 -0800
Daniel Campbell <zlg@gentoo.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> On 11/25/2015 10:17 AM, Michał Górny wrote:
> > On Wed, 25 Nov 2015 19:05:13 +0100 Ulrich Mueller <ulm@gentoo.org>
> > wrote:
> >   
> >>>>>>> On Wed, 25 Nov 2015, Kristian Fiskerstrand wrote:  
> >>   
> >>> On 11/25/2015 06:10 PM, William Hubbs wrote:  
> >>>> I would like for us to discuss adding the sbin directories to
> >>>> PATH for all users.  
> >>   
> >>> This sounds strange to me, if it should be executable by all
> >>> users it likely shouldn't be in sbin in the first place but in
> >>> bin. In any case; I don't see any good reason to change the
> >>> traditional behavior of sbin only being in path for root.  
> >> 
> >> +1
> >> 
> >> The sbin directories are separate from bin for the very reason
> >> that binaries in there (which are only usable with elevated
> >> privileges) can be excluded from normal users' PATH.  
> > 
> > Binaries like blkid, btrfs, getcap, sensors, swapon and various
> > tools from net-tools, iputils, wireless-tools... and I really have
> > better things to do than list all tools that landed in sbin for
> > some fun reason yet work for normal users.
> > 
> > But well, I'm the weird one wanting to be able to check how much
> > free space I've got without going through hoops.
> >   
> 
> Maybe I'm missing something, but `df` is in /bin. Do you use something
> else to determine free space?

btrfs fi df

-- 
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]

  reply	other threads:[~2015-11-25 19:24 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 [this message]
2015-11-25 20:16           ` Mike Gilbert
2015-11-25 20:15             ` Kristian Fiskerstrand
2015-11-26 15:03               ` [gentoo-dev] " Duncan
2015-11-26 15:10                 ` 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=20151125202355.744e8366.mgorny@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=zlg@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