On Wed, Jun 07, 2000 at 10:24:15PM -0400, Matthew Emmerton wrote:
brandelf will really understand any brand at all; We just add special
cases to suppress the need for -f for "known" brands. As it happens,
though, there's no reason why you can't run "brandelf -f -t BOGUS-BOGUS
foo"
and
On Tue, Jun 13, 2000 at 11:45:28PM -0400, Matthew Emmerton wrote:
Even more interesting is the SCO document on how ELFs are pseudo-branded.
OpenServer 5: No brand, but have a 28-byte NOTE field.
UnixWare 7: No brand, but have one of the flags set in the FLAG field. (I
couldn't find
In article [EMAIL PROTECTED],
Dan Nelson [EMAIL PROTECTED] wrote:
Hmm. So does this mean that SVR4-compliant programs must be
dynamically-linked?
Yes. The specification says that statically-linked programs are not
compliant.
Is there any recommendations on how an OS should supply an
In the last episode (Jun 07), Matthew Emmerton said:
And while we're on the topic, has anyone looked at the svr4 emulation
stuff for Linux, most notably Debian? According to this link
(http://www.debian.org/Packages/stable/otherosfs/ibcs-base.html), it
has SCO SVR3 as well as SCO ODT5 (SVR4)
On Wed, Jun 07, 2000 at 09:46:26AM -0500, Dan Nelson wrote:
It's hard because SCO doesn't
document any of this. You have to root through headers trying to
figure out what structures are used when.
How do you think the rest of the emulator has been written? :-)
Ok -- I envisaged that
To fix it in as painless a way as possible, I'm envisaging something
along the lines of this:
* The existing svr4 KLD module, which implements the guts of the
emulator; and
* Additional much, much smaller modules which implement the differences
between the "base" svr4 and
On Wed, Jun 07, 2000 at 10:24:15PM -0400, Matthew Emmerton wrote:
Each variant would have its own ELF brand to aid the selection of the
correct API.
Makes sense. On a related note, I'm curious to see how this will integrate
into existing non-kernel tools. For example, truss and
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
8 matches
Mail list logo