Date: Wed, 7 Jun 2000 22:40:10 -0500 From: Dan Nelson <dnelson@emsphone.com> To: Mark Newton <newton@internode.com.au> Cc: Matthew Emmerton <matt@xena.gsicomp.on.ca>, freebsd-hackers@FreeBSD.ORG Subject: Re: SVR4 Emulation [was Re: iBCS status?] Message-ID: <20000607224010.A29029@dan.emsphone.com> In-Reply-To: <20000608101038.B46114@internode.com.au>; from "Mark Newton" on Thu Jun 8 10:10:38 GMT 2000 References: <000a01bfcf7a$cc810330$1200a8c0@matt> <20000606152128.B82736@internode.com.au> <20000606012552.A1515@dan.emsphone.com> <20000606162453.B83108@internode.com.au> <20000606094719.A19961@dan.emsphone.com> <006101bfd04c$59de5c60$1200a8c0@matt> <20000607094626.B22129@dan.emsphone.com> <20000608101038.B46114@internode.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jun 08), Mark Newton said: > Ok -- I envisaged that there'd be a difficulty with different SysV > vendors who used different semantics for the same syscalls, or > different syscall numbering schemes. "It could happen!" (and, as we > can see, it probably has). Possibly.. But isn't there some SVR4 ABI standard that says "you must implement these syscalls and these ioctls this way", etc? I'm sure the ABI explicitly says what lseek() takes for arguments, for example. > Each variant would have its own ELF brand to aid the selection of the > correct API. This I'm not sure we need. Linux's ibcs2 code does a pretty good job of automatically determining what ABI the program expects. The first thing an SCO binary does, for example, is call sysarch(SI86GETFEATURES) which tells it what version of SCO it's running (ABIs within ABIs. Imagine that.) I imagine Solaris has a similar call. If not, we can just assume we're using the Solaris ABI until we see a sysarch call. I'm not a big fan of branding executables; they make it really hard to run things off CDROM or use automated installation scripts. > "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 "Daniel Nelson" - Anagram of "No Inland Eels" :( dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000607224010.A29029>