Thanks for this.
For what its worth:
I have made the kernel module work with 3.0-release using the LKM
interface instead, calling the MOD_SYSCALL wrapper (or whatever its
called, can't remember). the examples of writing and calling an lkm
syscall probably reflect the lkm interface itself.
I was cursing the ioctl calls i was making to /dev/lkm to search the
loaded modules for the one I loaded just to get the offset. does modfind
work for LKM's in 3.0-release?
I completely understand your plea to not use 3.0 release.
I am personally using 4.2-stable. Its not my decision to use 3.0
I beleive the computers running 3.0 have been running it for several years
now - i.e. it was the latest available at the time.
On 7 Feb 2001, Dag-Erling Smorgrav wrote:
> Matthew Luckie <[EMAIL PROTECTED]> writes:
> > 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
>
> Don't run 3.0.
>
> > Is it possible for me to hack my kernel module to work on freebsd
> > 3.0-release?
>
> Don't run 3.0.
>
> > So my question is, is it possible for me to hack my kernel module to work
> > on FreeBSD 3.0-release?
>
> Don't run 3.0.
>
> Even when released, 3.0 was not meant for production use, or in fact
> any use at all except by developers and those interested in helping
> out debugging RELENG_3 so we would one day be able to call it -STABLE.
> It's quite conceivably the most buggy and incomplete FreeBSD release
> ever. So allow me to repeat my advice:
>
> Don't run 3.0.
>
> In fact, don't run any kind of 3.x at all, since we stopped fixing
> bugs (except for some, but not all, known security holes) about half a
> year ago. If you absolutely must run RELENG_3, don't run anything but
> the very latest 3.5-STABLE (cvsup and cvs are your friends).
>
> DES
> --
> Dag-Erling Smorgrav - [EMAIL PROTECTED]
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
