> In the last episode (Jun 06), Mark Newton said:
> > > There is
> > > apparently quite a difference between Solaris and SCO SVR4; the first
> > > thing I had to do was change the lseek() syscall to use 32-bit
offsets
> > > instead of 64-bit, for example.
> >
> > Interesting - Solaris has two lseek syscalls, notionally "lseek" and
> > "lseek64". If SCO only has one, which is a 64 bit variant, could
> > you perhaps let me know what its syscall number is?
>
> SCO OSR5 has only the 32-bit variant at syscall 19, and its args match
> the ibcs2_lseek syscall (int fd, long offset, int whence). UW7
> apparently has two additional syscalls: lseek32 and lseek64, but I
> don't know what numbers they are; I don't have UW7.
I work at a SCO shop that uses the Progress RDBMS extensively. (I'm working
on writing the Perl DBD module for it as we speak.) Once I get that hacked
out, I'll take a look at the svr4 stuff and offer any SCO-related fixes that
are needed.
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) support. This may have already covered a
lot of the hairy issues (like syscall mappings). I realize it is dated (late
97), but anything helpful is better than nothing :)
--
Matthew Emmerton
GSI Computer Services
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
