Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:14759 comp.os.linux.misc:30640 Newsgroups: comp.os.386bsd.questions,comp.os.linux.misc Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!werple.apana.org.au!otis.apana.org.au!serval.net.wsu.edu!netnews.nwnet.net!oracle.pnl.gov!osi-east2.es.net!lll-winken.llnl.gov!uwm.edu!cs.utexas.edu!swrinde!pipex!uknet!info!iialan From: iialan@iifeak.swan.ac.uk (Alan Cox) Subject: Re: ELF and dynamic loading (Re: 386BSD vs Linux) Message-ID: <CzzAw7.H8z@info.swan.ac.uk> Sender: news@info.swan.ac.uk Nntp-Posting-Host: iifeak.swan.ac.uk Organization: Institute For Industrial Information Technology References: <3aqs7t$cp3@pdq.coe.montana.edu> <CztKMo.K4A@info.swan.ac.uk> <Czu7u5.D7J@deshaw.com> Date: Mon, 28 Nov 1994 13:02:30 GMT Lines: 24 In article <Czu7u5.D7J@deshaw.com> christos@deshaw.com (Christos Zoulas) writes: >Actually the problem is not the ioctl's! These are simple to implement on >top of the existing terminal driver. The problem is missing subsystems >such as streams, tli, etc. which are used to implement the networking code. Actually I disagree. Mapping tli to sockets is not trivial but quite viable. Most streams operations also map to some suitable faking. Linux iBCS does an (extremely trivial) mapping of this for local SCO X apps. >And you need the networking code to run any X application... Tell that to the coherent people ;) >Another problem is pty implementation; fortunately only a handful of >applications use ptys. pty implementation is almost constant on any OS nowdays. Alan -- ..-----------,,----------------------------,,----------------------------,, // Alan Cox // iialan@www.linux.org.uk // GW4PTS@GB7SWN.#45.GBR.EU // ``----------'`----------------------------'`----------------------------''