Bug 12972 - depmod invalid option -- A
Summary: depmod invalid option -- A
Keywords:
Status: CLOSED DUPLICATE of bug 12856
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: modutils
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact:
URL:
Whiteboard:
Depends On: 12238
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-06-24 01:01 UTC by Chris Runge
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2000-07-06 20:55:24 UTC
Embargoed:


Attachments (Terms of Use)

Description Chris Runge 2000-06-24 01:01:01 UTC
after upgrading from 6.2, the initial boot says the following:

Finding module dependencies depmod: invalid option -- A
depmod 2.3.10-pre1
depmod -a [-n -e -v -q -V]
       [-C configfile] [-F kernelsyms] [-b basedirectory] [forced_version]
depmod [-n -e -v -q] [-f kernelsysms] module1.o module2.o ...
If no arguments (expect options) are given, "depmod -a" is assumed

depmod will output a dependency list suitable for the modprobe utility.
depmod -a will find the list of moduules to probe from the file
/etc/modules.conf. It will output the result into the depfile specified
in this configuration file

Normally depmod operates silently, reporting only the list of modules that
won't load properly (missing symbols).
Option -q will make depmod keep quiet about missing symbols
Option -e output all the unresolved symbol for a given module

Comment 1 Pekka Savola 2000-06-26 14:39:30 UTC
This almost certainly happens because you had mkbootdisk installed before, and
modutils didn't get updated because of conflicts!



Comment 2 Bill Nottingham 2000-07-06 21:04:17 UTC

*** This bug has been marked as a duplicate of 12856 ***


Note You need to log in before you can comment on or make changes to this bug.