[openi18n-im:01096] Re: name space cleanup
AShiZaWa KaZuNoRi <[email protected]>
| Newsgroups | gmane.comp.internationalization.input-methods |
|---|---|
| Message-ID | <[email protected]> |
Date: Fri, 22 Oct 2004 19:53:29 +0900 (JST) From: Akira TAGOH <[email protected]>: > >>>>> On Fri, 22 Oct 2004 19:27:53 +0900, > >>>>> "AK" == AShiZaWa KaZuNoRi <[email protected]> wrote: > > AK> By the way, I've found that FHS claims the following. > AK> (http://www.pathname.com/fhs/pub/fhs-2.3.html) > > AK> /usr/lib : Libraries for programming and packages > AK> Purpose > > AK> /usr/lib includes object files, libraries, and internal > AK> binaries that are not intended to be executed directly by > AK> users or shell scripts. [22] > > AK> Would somebody tell me the interpretation of the sentence? It > AK> means that internal binaries that are intended to be executed in > AK> SYSTEM shell scripts should NOT go to into /usr/lib? > > For example, iiimf-segv-logger, which I added for logging > the backtrace, isn't intended to be executed directly by > users. such binaries should go under /usr/lib. also, the aux > object binaries, which isn't the shared libraries, should go > under /usr/lib. > In particular, which binaries are you worrying about this > claim? Four binaries. iiimd (htt), which is executed by init script. iiim-server (htt_server), which is executed by iiimd (htt). iiimx (httx), which is executed by X startup script. iiim-xbe (htt_xbe), which is executed by iiimx (httx). These binaries are not intended to be executed directly by users, even though they can be. Thanks, -- kasha