> On Fri, Oct 05, 2001 at 11:43:21AM +0200, Jan Hudec wrote:
> > > > I wonder how the kernel will know which module to be loaded.
> > >
> > > The kernel doesn't know, it just asks modprobe to do the dirty job.
> >
> > Anyway. How does the kernel know it should load a module? It sure does
> > know when device is open (if it has no driver, it composes alias from
> > the major number (eq. char-major-36) and asks modprobe to load this). But
> > when a syscall is not installed...
>
> There is no such thing as loadable syscalls in linux so your problem
> doesn't exist.
That's not my problem. This thread started with something about module
implementing a syscall. Without patching a kernel. So we came to a conclusion,
that the module must be explicitely loaded (not talking about other problems
with modifying syscall table).
--------------------------------------------------------------------------------
- Jan Hudec `Bulb' <bulb@ucw.cz>
-
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
IRC Channel: irc.openprojects.net / #kernelnewbies
Web Page: http://www.kernelnewbies.org/
