From owner-freebsd-emulation Wed Nov 22 13: 1:19 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 73B9A37B479 for ; Wed, 22 Nov 2000 13:01:17 -0800 (PST) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id C2C441FD6; Wed, 22 Nov 2000 22:01:16 +0100 (CET) Date: Wed, 22 Nov 2000 22:01:16 +0100 From: Pascal Hofstee To: freebsd-emulation@freebsd.org Subject: "Bogon" Discovered in linux.ko syscall-mapping Message-ID: <20001122220116.C81552@shadowmere.student.utwente.nl> Reply-To: daeron@shadowmere.student.utwente.nl Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Today i accidentilly stumbled over a "bogon" in our linux.ko syscall-mapping. Apparently the reboot-command of Linux's "libc" gets mapped to our own libc's reboot-command, which sounds reasonable at a first glance. I noticed though that Linux's reboot-command has additional functionality that is (as far as i can tell) not available in our native libc. One of those features is "disbale reboot-key-sequence". I am almost positive that the application in question was trying to issue one of these unsupported features ... which caused our native reboor-call to fall back to it's default behaviour ... "Reboot the System" -- Pascal Hofstee < daeron @ shadowmere . student . utwente . nl > begin LOVE-LETTER-FOR-YOU.TXT.vbs I'm a signature virus. Please copy me and help me spread. end To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message