Date: Mon, 29 Jan 2001 08:45:24 +0200 From: Mark Murray <mark@grondar.za> To: "Sue Wainer" <wainer@sandgate.com> Cc: "Freebsd-Arch" <freebsd-arch@FreeBSD.ORG> Subject: Re: kldunload, and calling uninit function Message-ID: <200101290645.f0T6jQW23655@gratis.grondar.za> In-Reply-To: <NDBBLIBAPKIAHMINJJNFAEAGCEAA.wainer@sandgate.com> ; from "Sue Wainer" <wainer@sandgate.com> "Sun, 28 Jan 2001 02:43:42 EST." References: <NDBBLIBAPKIAHMINJJNFAEAGCEAA.wainer@sandgate.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200101290645.f0T6jQW23655>