From: "John Stoffel" <john@stoffel.org>
To: "Joshua Hudson" <joshudson@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fwd: [PATCH] Add a /proc/self/exedir link
Date: Fri, 7 Apr 2006 15:17:30 -0400 [thread overview]
Message-ID: <17462.47818.652096.604638@smtp.charter.net> (raw)
In-Reply-To: <bda6d13a0604071201h64bfab2av21c8c3e0bbd8af0d@mail.gmail.com>
>>>>> "Joshua" == Joshua Hudson <joshudson@gmail.com> writes:
Joshua> Excellent point. This proposal needs to die, but there needs
Joshua> to be some way to solve this problem.
Why don't you try to explain the problem in more depth, but without
assuming a solution at all. Just talk about what you're trying to
fix.
As a SysAdmin by trade, if the program is written sanely, it's not
hard to make it relocateable and runable from anywhere. It's when the
program *knows* or the libraries is uses *know* that stuff is in
certain locations that things break.
I'm really writing from memory here, since I first saw your proposal
and looked it over and went "why bother?" but didn't have the time to
check it out in detail.
John
next prev parent reply other threads:[~2006-04-07 19:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5XGlt-GY-23@gated-at.bofh.it>
[not found] ` <5XGOz-1eP-35@gated-at.bofh.it>
2006-04-06 11:39 ` Bodo Eggert
2006-04-06 13:21 ` Mike Hearn
2006-04-06 17:02 ` Bodo Eggert
2006-04-06 19:36 ` Mike Hearn
2006-04-07 18:40 ` Eric W. Biederman
[not found] ` <bda6d13a0604071201o36496a55o2eae6a65153a06c3@mail.gmail.com>
2006-04-07 19:01 ` Fwd: " Joshua Hudson
2006-04-07 19:17 ` John Stoffel [this message]
2006-04-07 19:22 ` Mike Hearn
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=17462.47818.652096.604638@smtp.charter.net \
--to=john@stoffel.org \
--cc=joshudson@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®