From owner-freebsd-emulation Thu Feb 5 10:07:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27969 for freebsd-emulation-outgoing; Thu, 5 Feb 1998 10:07:43 -0800 (PST) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from pegasus.com (pegasus.com [206.127.225.31]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA27961 for ; Thu, 5 Feb 1998 10:07:39 -0800 (PST) (envelope-from richard@pegasus.com) Received: by pegasus.com (8.6.8/PEGASUS-2.2) id IAA09715; Thu, 5 Feb 1998 08:07:12 -1000 Date: Thu, 5 Feb 1998 08:07:12 -1000 From: richard@pegasus.com (Richard Foulk) Message-Id: <199802051807.IAA09715@pegasus.com> In-Reply-To: Allan Strand "Re: NetBSD emulation" (Feb 5, 8:21am) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: freebsd-emulation@FreeBSD.ORG Subject: Re: NetBSD emulation Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe freebsd-emulation" } > NetBSD *IS* emulated by FreeBSD. The problem is that someone (Net ? Free } > ?) reversed the exec magic number. This means that FreeBSD recognizes the } > NetBSD Magic, load and starts the binary. The binary try to load the } > ld.so dynamic linker *BUT*, before, it checks the ld.so magic number and } > find it reversed !! (then it dies, spiting something about 'bad ld.so } > magic'). } > So what about fudging a copy with the magic number modified? Richard