version 4, including all changes.
.
| Rev |
Author |
# |
Line |
| 1 |
perry |
1 |
MKINITRD |
| |
|
2 |
!!!MKINITRD |
| |
|
3 |
NAME |
| |
|
4 |
SYNOPSIS |
| |
|
5 |
DESCRIPTION |
| |
|
6 |
OPTIONS |
| |
|
7 |
FILES |
| |
|
8 |
SEE ALSO |
| |
|
9 |
AUTHOR |
| |
|
10 |
---- |
| |
|
11 |
!!NAME |
| |
|
12 |
|
| |
|
13 |
|
| |
|
14 |
mkinitrd - make an initrd image |
| |
|
15 |
!!SYNOPSIS |
| |
|
16 |
|
| |
|
17 |
|
| |
|
18 |
__mkinitrd__ [[__-k__] [[__-d__ ''confdir''] |
| |
|
19 |
[[__-m__ ''command''] [[__-o__ ''outfile''] |
| |
|
20 |
[[__-r__ ''root''] ''moduledir'' |
| |
|
21 |
!!DESCRIPTION |
| |
|
22 |
|
| |
|
23 |
|
| |
|
24 |
The __mkinitrd__ script constructs a directory structure |
| |
|
25 |
that can serve as an __initrd__ root file system. It then |
| |
|
26 |
generates an image containing that directory structure using |
| |
|
27 |
mkcramfs(8), which can be loaded using the |
| |
|
28 |
__initrd__ mechanism. The kernel modules placed in the |
| |
|
29 |
directory structure will be taken from ''moduledir''. |
| |
|
30 |
This is usually of the form |
| |
|
31 |
''/lib/modules/your-kernel-version''. |
| |
|
32 |
|
| |
|
33 |
|
| |
|
34 |
The directory structure can be customised by placing scripts |
| |
|
35 |
into ''confdir/scripts''. They will be run using |
| 4 |
perry |
36 |
run-parts(8) just before the directory is fed to |
| 1 |
perry |
37 |
mkcramfs(8). You can also specify modules to load by |
| |
|
38 |
putting them in ''confdir/modules'', whose format is |
| |
|
39 |
identical to that of ''/etc/modules'', which is described |
| |
|
40 |
in __modules(5)__. |
| |
|
41 |
|
| |
|
42 |
|
| |
|
43 |
When the system boots using an __initrd__ image created |
| |
|
44 |
by mkinitrd(8), the __linuxrc__ will wait for an |
| |
|
45 |
amount of time which is configured through |
| 4 |
perry |
46 |
mkinitrd.conf(5), during which it may be interrupted |
| 1 |
perry |
47 |
by pressing __ENTER__. After that, the modules specified |
| |
|
48 |
in ''confdir/modules'' (and possibly others if |
| |
|
49 |
__ROOT__ is not null) will be loaded, followed by any |
| |
|
50 |
actions generated when __ROOT__ is not null. Finally any |
| |
|
51 |
scripts or executables in ''/scripts'' will be run in |
| |
|
52 |
alphabetical order. |
| |
|
53 |
!!OPTIONS |
| |
|
54 |
|
| |
|
55 |
|
| |
|
56 |
__-d__ ''confdir'' |
| |
|
57 |
|
| |
|
58 |
|
| |
|
59 |
By default __mkinitrd__ looks for its configuration files |
| |
|
60 |
in ''/etc/mkinitrd''. Use this option to override |
| |
|
61 |
that. |
| |
|
62 |
|
| |
|
63 |
|
| |
|
64 |
__-k__ |
| |
|
65 |
|
| |
|
66 |
|
| |
|
67 |
Do not delete the temporary working directory that |
| |
|
68 |
__mkinitrd__ uses. This is useful for |
| |
|
69 |
debugging. |
| |
|
70 |
|
| |
|
71 |
|
| |
|
72 |
__-m__ ''command'' |
| |
|
73 |
|
| |
|
74 |
|
| |
|
75 |
This option overrides the setting of __MKIMAGE__ in |
| |
|
76 |
''mkinitrd.conf''. |
| |
|
77 |
|
| |
|
78 |
|
| |
|
79 |
__-o__ ''outfile'' |
| |
|
80 |
|
| |
|
81 |
|
| |
|
82 |
This option causes __mkinitrd__ to write the image to |
| |
|
83 |
''outfile'' instead of the standard output. |
| |
|
84 |
|
| |
|
85 |
|
| |
|
86 |
__-r__ ''root'' |
| |
|
87 |
|
| |
|
88 |
|
| |
|
89 |
This option overrides the setting of __ROOT__ in |
| |
|
90 |
''mkinitrd.conf''. |
| |
|
91 |
!!FILES |
| |
|
92 |
|
| |
|
93 |
|
| |
|
94 |
''/etc/mkinitrd/exe'' |
| |
|
95 |
|
| |
|
96 |
|
| |
|
97 |
This file contains full paths to shared executables that |
| |
|
98 |
should be included in the __initrd__ image. |
| |
|
99 |
__mkinitrd__ will include them as well as any shared |
| |
|
100 |
libraries that they are linked with. |
| |
|
101 |
|
| |
|
102 |
|
| |
|
103 |
''/etc/mkinitrd/files'' |
| |
|
104 |
|
| |
|
105 |
|
| |
|
106 |
This file contains full paths to files that should be |
| |
|
107 |
included in the __initrd__ image. |
| |
|
108 |
|
| |
|
109 |
|
| |
|
110 |
''/etc/mkinitrd/mkinitrd.conf'' |
| |
|
111 |
|
| |
|
112 |
|
| |
|
113 |
The default configuration file for the script. |
| |
|
114 |
|
| |
|
115 |
|
| |
|
116 |
''/etc/mkinitrd/modules'' |
| |
|
117 |
|
| |
|
118 |
|
| |
|
119 |
All modules specified in this file will be loaded when the |
| |
|
120 |
system boots using the generated image. However, they are |
| |
|
121 |
not automatically included on the image. You will either |
| |
|
122 |
have to use the appropriate __MODULES__ setting, or copy |
| |
|
123 |
them in using a script in |
| |
|
124 |
''/etc/mkinitrd/scripts''. |
| |
|
125 |
|
| |
|
126 |
|
| |
|
127 |
''/etc/mkinitrd/scripts'' |
| |
|
128 |
|
| |
|
129 |
|
| |
|
130 |
Scripts in this directory are run just before the image is |
| |
|
131 |
generated from. |
| |
|
132 |
!!SEE ALSO |
| |
|
133 |
|
| |
|
134 |
|
| 4 |
perry |
135 |
mkcramfs(8), mkinitrd.conf(5) |
| 1 |
perry |
136 |
!!AUTHOR |
| |
|
137 |
|
| |
|
138 |
|
| |
|
139 |
Herbert Xu |
| |
|
140 |
---- |