version 2, including all changes.
.
| Rev |
Author |
# |
Line |
| 1 |
perry |
1 |
UPDATE-MODULES |
| |
|
2 |
!!!UPDATE-MODULES |
| |
|
3 |
NAME |
| |
|
4 |
SYNOPSIS |
| |
|
5 |
DESCRIPTION |
| |
|
6 |
FILES |
| |
|
7 |
OPTIONS |
| |
|
8 |
SEE ALSO |
| |
|
9 |
BUGS |
| |
|
10 |
AUTHOR |
| |
|
11 |
---- |
| |
|
12 |
!!NAME |
| |
|
13 |
|
| |
|
14 |
|
| |
|
15 |
update-modules - (re)generate /etc/modules.conf and /etc/chandev.conf |
| |
|
16 |
!!SYNOPSIS |
| |
|
17 |
|
| |
|
18 |
|
| |
|
19 |
__update-modules__ [[force] |
| |
|
20 |
!!DESCRIPTION |
| |
|
21 |
|
| |
|
22 |
|
| |
|
23 |
__update-modules__ is a simple tool to manage |
| |
|
24 |
''/etc/modules.conf'' and ''/etc/chandev.conf'' for |
| |
|
25 |
the s390 architecture. The Linux module utilities use one |
| |
|
26 |
configuration file for all their configuration. This makes |
| |
|
27 |
it hard for packages to dynamically add information about |
| |
|
28 |
their own modules. To fix this __update-modules__ has |
| |
|
29 |
been introduced. |
| |
|
30 |
|
| |
|
31 |
|
| |
|
32 |
__update-modules__ attempts to fix this by generating the |
| |
|
33 |
configuration file from seperate files which are located in |
| |
|
34 |
''/etc/modutils''. All files in that directory are |
| |
|
35 |
assembled together to form ''/etc/modules.conf'' and |
| |
|
36 |
''/etc/chandev.conf''. There is also a special |
| |
|
37 |
subdirectory (''/etc/modutils/arch'') which contains |
| |
|
38 |
information for special architectures. __update-modules__ |
| |
|
39 |
determines the architecture and selects which file it must |
| |
|
40 |
use. |
| |
|
41 |
|
| |
|
42 |
|
| |
|
43 |
After generation a backup of the old file is put in |
| |
|
44 |
''/etc/modules.conf.old'' or |
| |
|
45 |
''/etc/chandev.conf.old''. |
| |
|
46 |
!!FILES |
| |
|
47 |
|
| |
|
48 |
|
| |
|
49 |
There are two types of file you can put in |
| |
|
50 |
''/etc/modutils'': normal files and exectuable files. |
| |
|
51 |
Normal files contain standard modules configuration |
| 2 |
perry |
52 |
information, as described in modules.conf(5). Files |
| 1 |
perry |
53 |
with the suffix .chandev contain the module options, as |
| |
|
54 |
described in chandev(8). The special file |
| |
|
55 |
0chandev.chandev contains the channel device layer specific |
| |
|
56 |
options. Executable files are executed and their output is |
| |
|
57 |
used as extra configuration information. Error messages sent |
| |
|
58 |
to stderr are not redirected. |
| |
|
59 |
|
| |
|
60 |
|
| |
|
61 |
__update-modules__ will ignore files that match the |
| |
|
62 |
following regular expression: |
| |
|
63 |
|
| |
|
64 |
|
| |
|
65 |
__*$__ |
| |
|
66 |
|
| |
|
67 |
|
| |
|
68 |
(ie files with the extension ''.dpkg-new'', |
| |
|
69 |
''.dpkg-orig'', ''.dpkg-dist'', ''.dpkg-old'', or |
| |
|
70 |
whose filename end with a ''~''). |
| |
|
71 |
!!OPTIONS |
| |
|
72 |
|
| |
|
73 |
|
| |
|
74 |
''force'' |
| |
|
75 |
|
| |
|
76 |
|
| |
|
77 |
__update-modules__ check if the current |
| |
|
78 |
''/etc/modules.conf and /etc/chandev.conf'' are generated |
| |
|
79 |
files by checking for a special tag on the first line. If |
| |
|
80 |
this tag is not found generation is aborted. By supplying |
| |
|
81 |
''force'' as parameter only a warning is |
| |
|
82 |
printed. |
| |
|
83 |
!!SEE ALSO |
| |
|
84 |
|
| |
|
85 |
|
| 2 |
perry |
86 |
depmod(1) modules.conf(5) modprobe(8) |
| 1 |
perry |
87 |
chandev(8), |
| |
|
88 |
!!BUGS |
| |
|
89 |
|
| |
|
90 |
|
| |
|
91 |
None of course! :) |
| |
|
92 |
!!AUTHOR |
| |
|
93 |
|
| |
|
94 |
|
| |
|
95 |
This manual page was written by Wichert Akkerman |
| |
|
96 |
---- |
