Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:14658 comp.os.linux.misc:30431 Newsgroups: comp.os.386bsd.questions,comp.os.linux.misc Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!pipex!uknet!info!iialan From: iialan@iifeak.swan.ac.uk (Alan Cox) Subject: Re: ELF and dynamic loading (Re: 386BSD vs Linux) Message-ID: <CztKMo.K4A@info.swan.ac.uk> Sender: news@info.swan.ac.uk Nntp-Posting-Host: iifeak.swan.ac.uk Organization: Institute For Industrial Information Technology References: <3alnmi$57g@pdq.coe.montana.edu> <CzM9tE.C83@info.swan.ac.uk> <3aqs7t$cp3@pdq.coe.montana.edu> Date: Fri, 25 Nov 1994 10:47:11 GMT Lines: 22 In article <3aqs7t$cp3@pdq.coe.montana.edu> nate@bsd.coe.montana.edu (Nate Williams) writes: >Ahh, but in the case of NetBSD/FreeBSD/Linux, there is not always a >mapping of functions one to another. The functions are different, and >have different API's which would require OS specific libraries. And, >because of this it is MUCH more work to determine on a OS by OS basic >what is required than to just grab all of the shared libraries and >install them. Almost everything maps neatly. There are a few obscure calls that don't really matter - things like sysctl(), ps are rarely portable as binaries. Real applications should map simply. The worst bit is probably mappings between the (obsolete) pre posix BSD terminal ioctl()'s and termios. The real thrust anyway should be towards iBCS2. Thats the common standard and the one that counts - at least until people like WP jump on the native linux application bandwagon. Alan -- ..-----------,,----------------------------,,----------------------------,, // Alan Cox // iialan@www.linux.org.uk // GW4PTS@GB7SWN.#45.GBR.EU // ``----------'`----------------------------'`----------------------------''