From: Joel Newkirk <netfilter@newkirk.us>
To: bobo <boboaq@163.com>,
"netfilter@lists.netfilter.org" <netfilter@lists.netfilter.org>
Cc: "bobowd@sohu.com" <bobowd@sohu.com>
Subject: Re: What is the difference between modprobe and insmod?
Date: Fri, 20 Dec 2002 03:20:52 -0500 [thread overview]
Message-ID: <200212200320.52534.netfilter@newkirk.us> (raw)
In-Reply-To: <20021220070647.BA0B01C959464@sm181.163.com>
On Friday 20 December 2002 02:11 am, bobo wrote:
> While writing IPtables scripts,there are two command:
> modprobe and insmod.
>
> In some example,some use : modprobe ip_tables,but others use:
> insmod ip_tables.
>
> Why? Is there difference between them?
For the purpose of loading specified modules you can consider them the
same. Modprobe is a higher-level interface that will call insmod. I
personally use modprobe since it succeeds silently. IE, if it
successfully loads the module, or if the module is already loaded,
insmod will report this, while modprobe will not output anything in
these situations. They will both, by default, report failure to
find/load a module, and the -q option tells them both to be quiet about
errors, but insmod will /still/ report success even with -q.
For full details see "man insmod" and "man modprobe"... :^)
(under KDE, the default IIRC with RedHat 7.2, using alt-F2 then #insmod
in the dialog, or #insmod as a URL in konquerer works nicely)
j
next prev parent reply other threads:[~2002-12-20 8:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 7:11 What is the difference between modprobe and insmod? bobo
2002-12-20 8:20 ` Joel Newkirk [this message]
2002-12-20 11:50 ` Dharmendra.T
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=200212200320.52534.netfilter@newkirk.us \
--to=netfilter@newkirk.us \
--cc=boboaq@163.com \
--cc=bobowd@sohu.com \
--cc=netfilter@lists.netfilter.org \
/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.