From owner-freebsd-arch Sun Jan 28 22:46:12 2001 Delivered-To: freebsd-arch@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 97AA837B404 for ; Sun, 28 Jan 2001 22:45:51 -0800 (PST) Received: from grondar.za (root@gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f0T6jQW23655; Mon, 29 Jan 2001 08:45:29 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200101290645.f0T6jQW23655@gratis.grondar.za> To: "Sue Wainer" Cc: "Freebsd-Arch" Subject: Re: kldunload, and calling uninit function References: In-Reply-To: ; from "Sue Wainer" "Sun, 28 Jan 2001 02:43:42 EST." Date: Mon, 29 Jan 2001 08:45:24 +0200 From: Mark Murray Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am having problems getting my SYSUNINIT function called when I do a > kldunload. Is there a particular reason that you need to use SYS[UN]INIT? I tried those, and had little luck. What workes much better for me was the "modevent" method - look in sys/dev/random/randomdev.c > I have reduced my source file to containing nothing more than > a sysinit and sysunit function, both of which only print out a > diagnostic. I believe the setdef files look OK. I have traced through > the loader symbol look up function, and the sysinit_set name is there, > but the sysuninit_set name is not. I do get the diagnostic printed > from my sysinit function. There is very little use of the SYSUNINIT macro in the kernel, and I believe it to be broken, as last time I used it, I got compile errors from it. Give me a yell if you need a hand getting the (better) MODULE_* macros going instead. M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message