Messages in this thread |  | | | Date | Tue, 31 Dec 96 23:42:28 EST | | From | Tom Dyas <> | | Subject | question about modules rewrite | |
Now that the kernel modules implementation has been rewritten for the
better and the interface changed somewhat, is there any reason to have
both sys_create_module() and sys_init_module()?
Why isn't the functionality of sys_create_module() in
sys_init_module()? It might be better to move it because then you
could have sys_create_module() return ENOSYS. This would have the
effect of causing the older, unsupported module utilities to bail out
early.
Tom
|  |