From owner-freebsd-hackers Fri Feb 28 15:40:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA26169 for hackers-outgoing; Fri, 28 Feb 1997 15:40:17 -0800 (PST) Received: from obiwan.aceonline.com.au (obiwan.aceonline.com.au [203.103.90.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA26159; Fri, 28 Feb 1997 15:40:12 -0800 (PST) Received: from localhost (adrian@localhost) by obiwan.aceonline.com.au (8.8.5/8.8.5) with SMTP id NAA01571; Sat, 1 Mar 1997 13:42:50 +0800 (WST) Date: Sat, 1 Mar 1997 13:42:50 +0800 (WST) From: Adrian Chadd To: Warner Losh cc: questions@freebsd.org, hackers@freebsd.org Subject: Re: Java binary support in FreeBSD ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 28 Feb 1997, Warner Losh wrote: > If you go off and do this, it might not be bad to make this > generalized so that I can run my old CP/M programs through the z80 > emulator that I have laying around, or the MS-DOS programs through > DOSEMU or whatever. > > Warner > Again - its just one file (imgact_java.c) which has the code to recognise java binaries, and then do some magic to execute it with the right interpreter and command args, etc. Extending it to cover DOS binaries, etc, wouldn't be hard (for dos .EXE Dont' you look for 'MZ' at the beginning of the file? Com files will be different, since they are just an image of a segment of code to throw in memory, with no real discernable headers. Anyways, back to work. Adrian.