From: Jesper Juhl <jesper.juhl@gmail.com>
To: iSteve <isteve@rulez.cz>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>, linux-kernel@vger.kernel.org
Subject: Re: query_modules syscall gone? Any replacement?
Date: Tue, 13 Sep 2005 17:50:00 +0200 [thread overview]
Message-ID: <9a8748490509130850672ab774@mail.gmail.com> (raw)
In-Reply-To: <4326F093.80206@rulez.cz>
On 9/13/05, iSteve <isteve@rulez.cz> wrote:
> > Nope, they are not prevented. However, there is a Tainted flag
> > that is set when one is loaded (and that flag is never cleared).
> >
>
> Okay, I've been wrong in my conclusion and I gotta read some fine manual
> about how the modules actually work -- could you recommend me some in
> particular?
>
Well, the depmod(8), lsmod(8), insmod(8), modprobe(8), modules.dep(5),
depmod.old(8) and modprobe.conf(5) man pages all have various bits of
info.
There's also some info in chapter 2 of "Linux Device Drivers, Third
Edition" - http://lwn.net/images/pdf/LDD3/ch02.pdf
Then there's The Linux Kernel Module Programming Guide -
http://www.tldp.org/LDP/lkmpg/2.6/html/
As well as the Linux Loadable Kernel Module HOWTO -
http://www.tldp.org/HOWTO/Module-HOWTO/
Also take a look at the file Documentation/kbuild/modules.txt in your
kernel source dir.
That's just a little bit of reading material for you :)
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2005-09-13 15:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4KSFY-2pO-17@gated-at.bofh.it>
2005-09-09 20:25 ` query_modules syscall gone? Any replacement? Bodo Eggert
2005-09-09 20:33 ` iSteve
2005-09-13 14:11 ` iSteve
2005-09-13 15:15 ` Randy.Dunlap
2005-09-13 15:30 ` iSteve
2005-09-13 15:44 ` Randy.Dunlap
2005-09-13 16:26 ` iSteve
2005-09-13 16:52 ` Randy.Dunlap
2005-09-13 19:50 ` Daniel Barkalow
2005-09-13 15:50 ` Jesper Juhl [this message]
2005-09-09 15:02 iSteve
2005-09-09 15:27 ` linux-os (Dick Johnson)
2005-09-09 16:10 ` iSteve
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9a8748490509130850672ab774@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=isteve@rulez.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.