From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Location of absolute IA32 shared objects.
Date: Thu, 13 Sep 2001 19:52:09 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805178@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805122@msgid-missing>
>>>>> On 10 Sep 2001 21:30:02 -0700, Ulrich Drepper <drepper@redhat.com> said:
Uli> David Mosberger <davidm@hpl.hp.com> writes:
>> As far as I can see, neither LSB nor FHS address the issue of
>> where to place emulation files, so I'll propose a prefix of
>> "/emul/ia32-linux/" as a starter. Any objections?
Uli> Not that I care, but this is clearly a place for a new /proc
Uli> entry which can be changed by the sysadmin.
I'd have thought that this should be treated like "/": an unchanging
prefix. Mount, symlinks, and chroot are your friend. Making it
variable makes installation harder, as others have pointed out. But
it's not like I care a whole lot (as long as ia64 kernel performance
isn't impacted noticably).
--david
next prev parent reply other threads:[~2001-09-13 19:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-05 17:26 [Linux-ia64] Location of absolute IA32 shared objects Don Dugger
2001-09-05 20:47 ` Christoph Hellwig
2001-09-05 20:53 ` Don Dugger
2001-09-11 4:11 ` David Mosberger
2001-09-11 4:30 ` Ulrich Drepper
2001-09-11 10:26 ` Christoph Hellwig
2001-09-11 11:25 ` Mark Goodwin
2001-09-12 11:58 ` Christoph Hellwig
2001-09-13 19:52 ` David Mosberger [this message]
2001-09-14 14:30 ` Doug Beattie
2001-09-14 15:51 ` David Mosberger
2001-09-14 21:26 ` Dugger's
2001-09-17 20:33 ` David Mosberger
2001-09-18 8:05 ` Jes Sorensen
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=marc-linux-ia64-105590698805178@msgid-missing \
--to=davidm@hpl.hp.com \
--cc=linux-ia64@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.