From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Jeff King <peff@peff.net>, Jonathan Nieder <jrnieder@gmail.com>,
git@vger.kernel.org, paul@mad-scientist.net, dnj@google.com
Subject: Re: Git 2.18: RUNTIME_PREFIX... is it working?
Date: Thu, 19 Jul 2018 22:26:13 +0000 [thread overview]
Message-ID: <20180719222613.GA7066@genre.crustytoothpaste.net> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1807181418120.71@tvgsbejvaqbjf.bet>
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
On Wed, Jul 18, 2018 at 02:18:44PM +0200, Johannes Schindelin wrote:
> On Sat, 14 Jul 2018, brian m. carlson wrote:
> > I will say that at cPanel, we have a configuration where end users can
> > end up inside a mount namespace without /proc (depending on the
> > preferences of the administrator). However, it's easy enough for us to
> > simply build without RUNTIME_PREFIX if necessary.
> >
> > If we turn it on by default, it would be nice if we documented (maybe in
> > the Makefile) that it requires /proc on Linux for the benefit of other
> > people who might be in a similar situation.
>
> Is there *really* no other way on Linux to figure out the absolute path of
> the current executable than to open a pseudo file in the `/proc` file
> system?
Nope, not that I'm aware of. You have to read the destination of
the /proc/PID/exe symlink.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 867 bytes --]
next prev parent reply other threads:[~2018-07-19 22:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 5:12 Git 2.18: RUNTIME_PREFIX... is it working? Paul Smith
2018-07-04 11:22 ` Johannes Schindelin
2018-07-05 15:36 ` Paul Smith
2018-07-06 9:00 ` Johannes Schindelin
2018-07-06 13:18 ` Daniel Jacques
2018-07-08 18:52 ` Paul Smith
2018-07-08 21:52 ` Johannes Schindelin
2018-07-09 19:58 ` Jeff King
2018-07-09 20:26 ` Johannes Schindelin
2018-07-10 2:21 ` Jeff King
2018-07-10 11:40 ` Johannes Schindelin
2018-07-10 14:03 ` Daniel Jacques
2018-07-10 16:09 ` Junio C Hamano
2018-07-09 21:05 ` Junio C Hamano
2018-07-10 3:56 ` Jeff King
2018-07-10 7:13 ` Perry Hutchison
2018-07-10 14:03 ` Jeff King
2018-07-10 22:20 ` Jonathan Nieder
2018-07-10 22:21 ` Jonathan Nieder
2018-07-17 9:45 ` Johannes Schindelin
2018-07-14 20:51 ` brian m. carlson
2018-07-18 12:18 ` Johannes Schindelin
2018-07-19 22:26 ` brian m. carlson [this message]
2018-07-20 14:29 ` Jeff Hostetler
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=20180719222613.GA7066@genre.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=dnj@google.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=paul@mad-scientist.net \
--cc=peff@peff.net \
/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.