From owner-freebsd-hackers Tue Sep 5 22:22:24 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.11/8.6.6) id WAA29599 for hackers-outgoing; Tue, 5 Sep 1995 22:22:24 -0700 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.freebsd.org (8.6.11/8.6.6) with ESMTP id WAA29586 for ; Tue, 5 Sep 1995 22:22:21 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id XAA19172; Tue, 5 Sep 1995 23:18:32 -0600 Date: Tue, 5 Sep 1995 23:18:32 -0600 From: Nate Williams Message-Id: <199509060518.XAA19172@rocky.sri.MT.net> To: Michael Smith Cc: hackers@freebsd.org, sef@kithrup.com Subject: Re: More iBCS2 hacking... In-Reply-To: <199509060338.NAA25501@genesis.atrad.adelaide.edu.au> References: <199509060338.NAA25501@genesis.atrad.adelaide.edu.au> Sender: hackers-owner@freebsd.org Precedence: bulk > > Ok, I shifted the header into the kernel includes, and the lkm builds OK. > (With all of the debugging enabled) > > Running the victim application tells me that it's making an unimplemented > ioctl call; which pulls me up short. I see those, but things seem to continue working. However, it's dying on my box with a panic when it tries to load (actually exec) any shlibs. > Does anyone have a SCO box lying around that can tell me what 0x6301 is? I have a couple SCO boxes, but what exactly do you want me to look for? A smart-alec answer would be that 0x6301 is 405505, but I'm sure you could have figured that out on your own. :-) > If anyone else is looking at this, I'd love to work on it with you... Sean Fagan has access to the necessary files to reproduce the errors I and Jordan have seen, and I hope he is finding time to look at it. Nate