From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joel Newkirk Subject: Re: What is the difference between modprobe and insmod? Date: Fri, 20 Dec 2002 03:20:52 -0500 Sender: netfilter-admin@lists.netfilter.org Message-ID: <200212200320.52534.netfilter@newkirk.us> References: <20021220070647.BA0B01C959464@sm181.163.com> Reply-To: netfilter@newkirk.us Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20021220070647.BA0B01C959464@sm181.163.com> Errors-To: netfilter-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Content-Type: text/plain; charset="us-ascii" To: bobo , "netfilter@lists.netfilter.org" Cc: "bobowd@sohu.com" On Friday 20 December 2002 02:11 am, bobo wrote: > While writing IPtables scripts,there are two command:=20 > 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=20 same. Modprobe is a higher-level interface that will call insmod. I=20 personally use modprobe since it succeeds silently. IE, if it=20 successfully loads the module, or if the module is already loaded,=20 insmod will report this, while modprobe will not output anything in=20 these situations. They will both, by default, report failure to=20 find/load a module, and the -q option tells them both to be quiet about=20 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=20 in the dialog, or #insmod as a URL in konquerer works nicely) j