modprobe.sgml

用于linux2.6内核支持模块的插入和卸载

	    This applies any modules inserted: both the module (or
	    alias) on the command line, and any modules it depends on.
	 </para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term><option>--force-vermagic</option>
        </term>
        <listitem>
          <para>
	    Every module contains a small string containing important
	    information, such as the kernel and compiler versions.  If
	    a module fails to load and the kernel complains that the
	    "version magic" doesn't match, you can use this option to
	    remove it.  Naturally, this check is there for your
	    protection, so this using option is dangerous.
	 </para>
	 <para>
	    This applies any modules inserted: both the module (or
	    alias) on the command line, and any modules it depends on.
	 </para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term><option>--force-modversion</option>
        </term>
        <listitem>
          <para>
	    When modules are compiled with CONFIG_MODVERSIONS set, a
	    section is created detailing the versions of every
	    interface used by (or supplied by) the module.  If a
	    module fails to load and the kernel complains that the
	    module disagrees about a version of some interface, you
	    can use "--force-modversion" to remove the version
	    information altogether.  Naturally, this check is there
	    for your protection, so using this option is dangerous.
	 </para>
	 <para>
	    This applies any modules inserted: both the module (or
	    alias) on the command line, and any modules it depends on.
	 </para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term><option>-l</option> <option>--list</option>
        </term>
        <listitem>
          <para>List all modules matching the given wildcard (or "*"
		if no wildcard is given).  This option is provided for
		backwards compatibility: see
	    <citerefentry>
	      <refentrytitle>find</refentrytitle><manvolnum>1</manvolnum>
	    </citerefentry> and
	    <citerefentry>
	      <refentrytitle>basename</refentrytitle><manvolnum>1</manvolnum>
	    </citerefentry> for a more flexible alternative.
	 </para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term><option>-a</option> <option>--all</option>
        </term>
        <listitem>
          <para>Insert all modules matching the given wildcard.  This
		option is provided for backwards compatibility: see
	    <citerefentry>
	      <refentrytitle>find</refentrytitle><manvolnum>1</manvolnum>
	    </citerefentry> and
	    <citerefentry>
	      <refentrytitle>basename</refentrytitle><manvolnum>1</manvolnum>
	    </citerefentry> for a more flexible alternative.
	 </para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term><option>-t</option> <option>--type</option>
        </term>
        <listitem>
          <para>Restrict <option>-l</option> or <option>-a</option> to modules
		in directories matching the
		<replaceable>dirname</replaceable> given.  This option
		is provided for backwards compatibility: see
	    <citerefentry>
	      <refentrytitle>find</refentrytitle><manvolnum>1</manvolnum>
	    </citerefentry>
	    and
	    <citerefentry>
	      <refentrytitle>basename</refentrytitle><manvolnum>1</manvolnum>
	    </citerefentry> or a more flexible alternative.
	 </para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term><option>-s</option> <option>--syslog</option>
        </term>
        <listitem>
          <para>
	    This option causes any error messages to go through the
	    syslog mechanism (as LOG_DAEMON with level LOG_NOTICE)
	    rather than to standard error.  This is also automatically
	    enabled when stderr is unavailable.
	  </para>
          <para>
	    This option is passed through <command>install</command>
	    or <command>remove</command> commands to other
	    <command>modprobe</command> commands in the
	    MODPROBE_OPTIONS environment variable.
	  </para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term><option>--set-version</option>
        </term>
        <listitem>
          <para>
	    Set the kernel version, rather than using
	    <citerefentry><refentrytitle>uname</refentrytitle><manvolnum>2</manvolnum></citerefentry> to decide on the kernel version (which dictates where to
	    find the modules).  This also disables backwards
	    compatibility checks (so 
	    <citerefentry>
	      <refentrytitle>modprobe.old</refentrytitle><manvolnum>8</manvolnum></citerefentry> will never be run).
	  </para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term><option>--show-depends</option>
        </term>
        <listitem>
          <para>
	    List the dependencies of a module (or alias), including
	    the module itself.  This produces a (possibly empty) set
	    of module filenames, one per line.  It does not run any
	    install commands which might apply.  Note that
	    <citerefentry><refentrytitle>modinfo</refentrytitle><manvolnum>8</manvolnum></citerefentry>
	    can be used to extract dependencies of a module from the
	    module itself, but knows nothing of aliases.
	  </para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term><option>-o</option> <option>--name</option>
        </term>
        <listitem>
          <para>
	    This option tries to rename the module which is being
	    inserted into the kernel.  Some testing modules can
	    usefully be inserted multiple times, but the kernel
	    refuses to have two modules of the same name.  Normally,
	    modules should not require multiple insertions, as that
	    would make them useless if there were no module support.
	  </para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term><option>--first-time</option>
        </term>
        <listitem>
          <para>
	    Normally, <command>modprobe</command> will succeed (and do
	    nothing) if told to insert a module which is already
	    present, or remove a module which isn't present.  This is
	    backwards compatible with the modutils, and ideal for
	    simple scripts.  However, more complicated scripts often
	    want to know whether <command>modprobe</command> really
	    did something: this option makes modprobe fail for that
	    case.
	  </para>
        </listitem>
      </varlistentry>
    </variablelist>
  </refsect1>
  <refsect1>
    <title>BACKWARDS COMPATIBILITY</title>

    <para>
      This version of <command>modprobe</command> is for kernels
      <literal>2.5.48</literal> and above.  If it detects a kernel
      with support for old-style modules (for which much of the work
      was done in userspace), it will attempt to run
      <command>modprobe.old</command> in its place, so it is
      completely transparent to the user.
    </para>
  </refsect1>
  <refsect1>
    <title>ENVIRONMENT</title>
    <para>
      The MODPROBE_OPTIONS environment variable can also be used to
      pass arguments to <command>modprobe</command>.
    </para>
  </refsect1>
  <refsect1>
    <title>COPYRIGHT</title>
    <para>
      This manual page Copyright 2002, Rusty Russell, IBM Corporation.
    </para>
  </refsect1>
  <refsect1>
    <title>SEE ALSO</title>
    <para>
      <citerefentry>
	<refentrytitle>modprobe.conf</refentrytitle><manvolnum>5</manvolnum>
      </citerefentry>,
      <citerefentry>
	<refentrytitle>lsmod</refentrytitle><manvolnum>8</manvolnum>
      </citerefentry>,
      <citerefentry>
	<refentrytitle>modprobe.old</refentrytitle><manvolnum>8</manvolnum>
      </citerefentry>
    </para>
  </refsect1>
</refentry>

<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-default-dtd-file:nil
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
-->