Hi, [dropping Perry's non-working email address again]
On Sat, 14 Jul 2018, brian m. carlson wrote: > On Tue, Jul 10, 2018 at 10:03:10AM -0400, Jeff King wrote: > > My point is that aside from RUNTIME_PREFIX, we don't need /proc. So > > somebody who currently builds Git with a static path like > > "/usr/libexec/git-core" and runs it inside a chroot will be just fine as > > long as /usr/libexec/git-core is available at that name inside the > > chroot. But if the build starts relying on RUNTIME_PREFIX, it's going to > > regress their case. > > 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? Ciao, Johannes
