From owner-freebsd-emulation Wed Nov 22 18:40:39 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 446EE37B4D7 for ; Wed, 22 Nov 2000 18:40:37 -0800 (PST) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id eAN2dkB87509; Wed, 22 Nov 2000 20:39:46 -0600 (CST) (envelope-from jlemon) Date: Wed, 22 Nov 2000 20:39:46 -0600 (CST) From: Jonathan Lemon Message-Id: <200011230239.eAN2dkB87509@prism.flugsvamp.com> To: marcel@cup.hp.com, emulation@freebsd.org Subject: Re: "Bogon" Discovered in linux.ko syscall-mapping X-Newsgroups: local.mail.freebsd-emulation In-Reply-To: References: Organization: Cc: Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you write: >Pascal Hofstee wrote: >> >> 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" > >You're probably right. We can't map Linux' reboot to FreeBSDs as is. Yeah. I have a simplistic linux wrapper for the reboot call somewhere, I should dig it up and commit it. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message