Date: Thu, 17 Jul 2008 10:11:34 +0200 From: Hans Petter Selasky <hselasky@c2i.net> To: freebsd-hackers@freebsd.org Cc: Jacky Oh <assaulter0x80@gmail.com> Subject: Re: SYSINIT Message-ID: <200807171011.35988.hselasky@c2i.net> In-Reply-To: <ed8027db0807161234wb760fceh9dfd7434669a6abb@mail.gmail.com> References: <ed8027db0807161234wb760fceh9dfd7434669a6abb@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 16 July 2008, Jacky Oh wrote: > Hello, > > I'm insvestigating about KLD's programming, and I cant find in my way wiht > the SYSINIT framework. My problem is that im from spanish, and the SYSINIT > concept is more complex for my as I understand in english. My question is, > anyone can explain to in a less complex form? please, I would be very > grateful, thankzz!! > > I belive that is a kernel trap for link modules and sub-systems, but i > don't sure. The best documentation about it is the charpter 5 of "FreeBSD > Architechture Handbook" Is the best doc but i need a small help..I'm > writing a KLD programming article for a spanish underground magazine. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" Hi, Simply put. The sysinit macro expands to a static structure using the "section" attribute which means the data ends up in a separate section after linking. Then the data in the sysinit section is scanned, sorted and executed at boot time or when you load a module. Sysuninit works in a similar way. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200807171011.35988.hselasky>