From owner-freebsd-hackers Mon Feb 5 15:12:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from postal.sdsc.edu (postal.sdsc.edu [132.249.20.114]) by hub.freebsd.org (Postfix) with ESMTP id 5A24B37B4EC for ; Mon, 5 Feb 2001 15:11:59 -0800 (PST) Received: from multivac.sdsc.edu (multivac.sdsc.edu [132.249.20.57]) by postal.sdsc.edu (8.9.3/8.9.3/SDSCserver-16) with ESMTP id PAA13360; Mon, 5 Feb 2001 15:11:58 -0800 (PST) Received: from localhost by multivac (8.9.3+Sun/1.11-SolarisClient) with ESMTP id PAA24722; Mon, 5 Feb 2001 15:11:58 -0800 (PST) Date: Mon, 5 Feb 2001 15:11:58 -0800 (PST) From: Matthew Luckie To: Cc: Subject: syscall kernel modules on 3.0-release Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I have written a KLD module that implements a syscall I wrote this module on 3.2-release, although this module is going to be used on a 3.0-release machine The relevant support for writing a syscall module was added after 3.0-release and is present in 3.1-release according to http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sys/sys/sysent.h.diff?r1=1.19&r2=1.20 Is it possible for me to hack my kernel module to work on freebsd 3.0-release? I have tried patching the sys/sysent.h file with the patch linked above and the module compiles perfectly, although when I kldload'd the module the system crashed and rebooted. I didnt see the crash message, although I can get that if it will help. So my question is, is it possible for me to hack my kernel module to work on FreeBSD 3.0-release? If not, can isolated patches be made to the kernel short of doing a cvsup for src-all to enable this to work? Matthew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message