All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Ruediger Meier <sweet_f_a@gmx.de>,
	util-linux@vger.kernel.org, Isaac Dunham <ibid.ag@gmail.com>
Subject: Re: question about hardcoded binary paths (swapon / mkswap)
Date: Thu, 2 Apr 2015 21:15:30 +0200	[thread overview]
Message-ID: <20150402191530.GG2097@ws.net.home> (raw)
In-Reply-To: <20150402161952.GB22171@vapier>

On Thu, Apr 02, 2015 at 12:19:52PM -0400, Mike Frysinger wrote:
> On 02 Apr 2015 10:20, Karel Zak wrote:
> > If I good remember then the reason is that the helpers does not have
> > to be installed in standard PATH. Well, you're author of this thing
> > :-)
> 
> i wrote the code to make it a configure option, but the actual behavior predates 
> me.  i'm interested more in the behavior, not the exact configure option.

 So, the basis question is if we really need to support non-standard
 paths for the helpers. IMHO it's unnecessary legacy and I don't see a
 problem to drop this feature and require $PATH, and for critical
 things like fsck fallback to /sbin if $PATH is undefined.

 Comments?

> looks like mkfs added it during the 2.2->2.5 transition, but otherwise no 
> details in the bundled NEWS that i saw.  oh well.

 mkfs is deprecated, the right way is to call directly mkfs.<type>.

> mount makes sense as it's set*id and we can't trust users to not be evil :)

 It does not execute anything with root rights, but yes, hardcoded
 paths make sense there (just to avoid complexity and external
 dependencies on environment).

    Karel


-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  reply	other threads:[~2015-04-02 19:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01 11:42 question about hardcoded binary paths (swapon / mkswap) Ruediger Meier
2015-04-01 13:38 ` Isaac Dunham
2015-04-01 16:17   ` Ruediger Meier
2015-04-01 20:10     ` Mike Frysinger
2015-04-01 21:06       ` Ruediger Meier
2015-04-01 21:38         ` Karel Zak
2015-04-02  1:12           ` Mike Frysinger
2015-04-02  8:20             ` Karel Zak
2015-04-02 16:19               ` Mike Frysinger
2015-04-02 19:15                 ` Karel Zak [this message]
2015-04-02 22:50                   ` Ruediger Meier
2015-04-03  1:15                   ` Mike Frysinger
2015-04-03  8:52                     ` Karel Zak
2015-04-03 23:16                       ` Mike Frysinger
2015-04-02 17:28               ` Isaac Dunham
2015-04-01 22:23         ` Mike Frysinger

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=20150402191530.GG2097@ws.net.home \
    --to=kzak@redhat.com \
    --cc=ibid.ag@gmail.com \
    --cc=sweet_f_a@gmx.de \
    --cc=util-linux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.