Subject: Re: While we're talking about binary emulation (FreeBSD)
To: Todd Vierling <tv@pobox.com>
From: David Maxwell <david@fundy.ca>
List: port-i386
Date: 09/30/1998 10:23:31
On Wed, Sep 30, 1998 at 07:52:44AM -0400, Todd Vierling wrote:
> On Wed, 30 Sep 1998, David Maxwell wrote:
> 
> :  11311 validate CALL  madvise(0x54000,0x1000,0x5)
> :  11311 validate RET   madvise -1 errno 45 Operation not supported
> 
> Grumble.  It seems to actually care what madvise() returns.  We don't yet
> support it, but it _should_ gracefully continue without that support.
> 
> You can hack around this by editing src/sys/kern/[u]vm/[u]vm_mmap.c
> Find the function sys_madvise() and change:
>        return (EOPNOTSUPP);
> to:
>        return (0);

Okay, further along now... on 3.0 FreeBSD libs, the bin dies, trying
syscall [253]. No big loss - The 2.x libs get past that part. In fact,
I can now get the server configured and 'running'. However, as soon
as I connect from a client, the client gets Ccbfh, and the server
goes like this...

/usr/libexec/ld.so: Undefined symbol "___inet_ntoa" called from typhoond:typhoond at 0x810fc

Here's the last portion of the trace, it feels relevant at this point to
mention that this box is running NetBSD 1.2 (Just happens to be old
box that was convienient for this testing. It's due for an ungrade
anyway - if someone thinks it will help here.)

   416 typhoond CALL  sigprocmask(0x3,0xffffffff)
   416 typhoond RET   sigprocmask -65793/0xfffefeff
   416 typhoond CALL  write(0x2,0x18e784,0x14)
   416 typhoond GIO   fd 2 wrote 20 bytes
       "/usr/libexec/ld.so: "
   416 typhoond RET   write 20/0x14
   416 typhoond CALL  write(0x2,0x18e79c,0x48)
   416 typhoond GIO   fd 2 wrote 72 bytes
       "Undefined symbol "___inet_ntoa" called from typhoond:typhoond at 0x810fc"
   416 typhoond RET   write 72/0x48
   416 typhoond CALL  write(0x2,0x18e788,0x1)
   416 typhoond GIO   fd 2 wrote 1 bytes
       "
       "
   416 typhoond RET   write 1
   416 typhoond CALL  exit(0x1)

I don't know the emulation system well enough to know which layer
this error is coming from.

-- 
David Maxwell, david@vex.net|david@maxwell.net --> Mastery of UNIX, like
mastery of language, offers real freedom. The price of freedom is always dear,
but there's no substitute. Personally, I'd rather pay for my freedom than live
in a bitmapped, pop-up-happy dungeon like NT. - Thomas Scoville