From: David Mosberger-Tang <David.Mosberger@acm.org>
To: Jamie Lokier <jamie@shareable.org>
Cc: linux-kernel@vger.kernel.org, davidm@hpl.hp.com
Subject: Re: common name for the kernel DSO
Date: 19 Jun 2003 13:26:42 -0700 [thread overview]
Message-ID: <ug3ci5zud9.fsf@panda.mostang.com> (raw)
In-Reply-To: <20030619192018$5cab@gated-at.bofh.it>
>>>>> On Thu, 19 Jun 2003 21:20:19 +0200, Jamie Lokier <jamie@shareable.org> said:
Jamie> H. Peter Anvin wrote:
>> It's a pretty ugly name, quite frankly, since it doesn't explain
>> what it is a gate from or to. linux-syscall.so.1 or
>> linux-kernel.so.1 would make a lot more sense.
Jamie> linux-syscall.so.1 makes most sense to me.
Jamie> It's the only one which is correct and unambiguous.
It's not really correct. The DSO can be used for up-calls (e.g.,
signal trampolines), too.
Like I said, I can _live_ with "syscall", but would prefer "gate",
because it's technically more accurate. It's also shorter, always a
bonus... ;-)
--david
next parent reply other threads:[~2003-06-19 20:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030618192007$14a5@gated-at.bofh.it>
[not found] ` <20030619062011$555e@gated-at.bofh.it>
[not found] ` <20030619192018$5cab@gated-at.bofh.it>
2003-06-19 20:26 ` David Mosberger-Tang [this message]
2003-06-18 19:12 common name for the kernel DSO David Mosberger
2003-06-18 20:32 ` Sam Ravnborg
2003-06-18 20:35 ` David Mosberger
2003-06-18 22:51 ` David Mosberger
2003-06-18 23:35 ` Andrew Morton
2003-06-18 23:56 ` David Mosberger
2003-06-25 3:19 ` Roland McGrath
2003-06-19 6:18 ` H. Peter Anvin
2003-06-19 6:25 ` David Mosberger
2003-06-19 6:46 ` H. Peter Anvin
2003-06-19 6:49 ` David Mosberger
2003-06-21 6:42 ` Pavel Machek
2003-06-19 19:15 ` Jamie Lokier
-- strict thread matches above, loose matches on Subject: below --
2003-06-18 19:12 David Mosberger
2003-06-18 20:32 ` Sam Ravnborg
2003-06-18 20:35 ` David Mosberger
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=ug3ci5zud9.fsf@panda.mostang.com \
--to=david.mosberger@acm.org \
--cc=davidm@hpl.hp.com \
--cc=jamie@shareable.org \
--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 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.