home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.linux:10581 comp.unix.bsd:5604
- Newsgroups: comp.os.linux,comp.unix.bsd
- Path: sparky!uunet!van-bc!stewart
- From: stewart@wimsey.bc.ca (Jim Stewart)
- Subject: Re: Shared libraries - info for 386BSD porting wanted
- Organization: Wimsey
- Date: Sat, 12 Sep 1992 22:47:35 GMT
- Message-ID: <BuHLzC.FzA@wimsey.bc.ca>
- Keywords: shared 386bsd
- References: <peter.716225737@hilly> <veit.716293407@du9ds3> <3583@ra.nrl.navy.mil>
- Lines: 25
-
- In article <3583@ra.nrl.navy.mil> eric@tantalus.dell.com (Eric Youngdale) writes:
- >In article <veit.716293407@du9ds3> veit@du9ds3.uni-duisburg.de writes:
- >>Another thread has been just started about that. Don't look at the Linux
- >>sources, the type of implementation is for a hacker's OS ;-), but not for the
- >>future. Linux uses (as most SysV systems) fixed addresses for shared
- >>libraries, which is, with one simple word *unacceptable*.
- >
- > Huh? Let me see, BSD does not have shared libraries, and Linux, like
- >SysV uses fixed addresses... Exactly what OS does have acceptable sharable
- >libraries? When you say "unacceptable", it almost sounds like you will
- >refuse to use them under linux. Is this really the case?
- >
- > [paragraph about 3Gb address space, and library address assignmet deleted]
- >--
- >Eric Youngdale
- >eric@tantalus.nrl.navy.mil
-
- in fact, Open VMS has sharable libraries that are origined at 00000000, can be
- mapped anywhere in process address spaced, and are fixed up at image
- activation time. The imave activator/image fixup internal services make
- nice bedtime reading :) ... but get out you BLISS-32 books :)
-
- js who_is_waiting_for_x11v2.0_and_LOVES_Linux
-
-
-