mdadm-1.6.0
[thirdparty/mdadm.git] / ReadMe.c
CommitLineData
64c4757e 1/*
9a9dab36 2 * mdadm - manage Linux "md" devices aka RAID arrays.
64c4757e 3 *
cd29a5c8 4 * Copyright (C) 2001-2002 Neil Brown <neilb@cse.unsw.edu.au>
64c4757e
NB
5 *
6 *
7 * This program is free software; you can redistribute it and/or modify
8 * it under the terms of the GNU General Public License as published by
9 * the Free Software Foundation; either version 2 of the License, or
10 * (at your option) any later version.
11 *
12 * This program is distributed in the hope that it will be useful,
13 * but WITHOUT ANY WARRANTY; without even the implied warranty of
14 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
15 * GNU General Public License for more details.
16 *
17 * You should have received a copy of the GNU General Public License
18 * along with this program; if not, write to the Free Software
19 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
20 *
21 * Author: Neil Brown
22 * Email: <neilb@cse.unsw.edu.au>
23 * Paper: Neil Brown
24 * School of Computer Science and Engineering
25 * The University of New South Wales
26 * Sydney, 2052
27 * Australia
28 */
29
9a9dab36 30#include "mdadm.h"
64c4757e 31
dd0781e5 32char Version[] = Name " - v1.6.0 - 4 June 2004\n";
64c4757e
NB
33/*
34 * File: ReadMe.c
35 *
36 * This file contains general comments about the implementation
9a9dab36 37 * and the various usage messages that can be displayed by mdadm
64c4757e 38 *
9a9dab36 39 * mdadm is a single program that can be used to control Linux md devices.
64c4757e
NB
40 * It is intended to provide all the functionality of the mdtools and
41 * raidtools but with a very different interface.
9a9dab36 42 * mdadm can perform all functions without a configuration file.
64c4757e
NB
43 * There is the option of using a configuration file, but not in the same
44 * way that raidtools uses one
45 * raidtools uses a configuration file to describe how to create a RAID
46 * array, and also uses this file partially to start a previously
47 * created RAID array. Further, raidtools requires the configuration
48 * file for such things as stopping a raid array which needs to know
49 * nothing about the array.
50 *
9a9dab36 51 * The configuration file that can be used by mdadm lists two
64c4757e
NB
52 * different things:
53 * 1/ a mapping from uuid to md device to identify which arrays are
54 * expect and what names (numbers) they should be given
55 * 2/ a list of devices that should be scanned for md sub-devices
56 *
57 *
58 */
59
60/*
dd0781e5 61 * mdadm has 7 major modes of operation:
64c4757e 62 * 1/ Create
5787fa49 63 * This mode is used to create a new array with a superblock
64c4757e
NB
64 * It can progress in several step create-add-add-run
65 * or it can all happen with one command
66 * 2/ Assemble
67 * This mode is used to assemble the parts of a previously created
68 * array into an active array. Components can be explicitly given
9a9dab36 69 * or can be searched for. mdadm (optionally) check that the components
5787fa49 70 * do form a bona-fide array, and can, on request, fiddle superblock
64c4757e
NB
71 * version numbers so as to assemble a faulty array.
72 * 3/ Build
73 * This is for building legacy arrays without superblocks
74 * 4/ Manage
e0d19036
NB
75 * This is for doing something to one or more devices
76 * in an array, such as add,remove,fail.
77 * run/stop/readonly/readwrite are also available
78 * 5/ Misc
79 * This is for doing things to individual devices.
80 * They might be parts of an array so
81 * zero-superblock, examine might be appropriate
82 * They might be md arrays so
83 * run,stop,rw,ro,detail might be appropriate
84 * Also query will treat it as either
85 * 6/ Monitor
86 * This mode never exits but just monitors arrays and reports changes.
dd0781e5
NB
87 * 7/ Grow
88 * This mode allows for changing of key attributes of a raid array, such
89 * as size, number of devices, and possibly even layout.
90 * At the time if writing, there is only minimal support.
64c4757e
NB
91 */
92
dd0781e5 93char short_options[]="-ABCDEFGQhVvbc:l:p:m:n:x:u:c:d:z:U:sa::rfRSow1t";
64c4757e
NB
94struct option long_options[] = {
95 {"manage", 0, 0, '@'},
e0d19036 96 {"misc", 0, 0, '#'},
64c4757e
NB
97 {"assemble", 0, 0, 'A'},
98 {"build", 0, 0, 'B'},
99 {"create", 0, 0, 'C'},
100 {"detail", 0, 0, 'D'},
101 {"examine", 0, 0, 'E'},
52826846 102 {"follow", 0, 0, 'F'},
dd0781e5 103 {"grow", 0, 0, 'G'},
e0d19036
NB
104 {"zero-superblock", 0, 0, 'K'}, /* deliberately no a short_option */
105 {"query", 0, 0, 'Q'},
52826846
NB
106
107 /* synonyms */
108 {"monitor", 0, 0, 'F'},
109
64c4757e
NB
110 /* after those will normally come the name of the md device */
111 {"help", 0, 0, 'h'},
56eedc1a 112 {"help-options",0,0,'h'},
64c4757e
NB
113 {"version", 0, 0, 'V'},
114 {"verbose", 0, 0, 'v'},
115
116 /* For create or build: */
117 {"chunk", 1, 0, 'c'},
118 {"rounding", 1, 0, 'c'}, /* for linear, chunk is really a rounding number */
98c6faba 119 {"level", 1, 0, 'l'}, /* 0,1,4,5,6,linear */
5787fa49 120 {"parity", 1, 0, 'p'}, /* {left,right}-{a,}symmetric */
64c4757e
NB
121 {"layout", 1, 0, 'p'},
122 {"raid-disks",1, 0, 'n'},
b83d95f3 123 {"raid-devices",1, 0, 'n'},
64c4757e 124 {"spare-disks",1,0, 'x'},
b83d95f3 125 {"spare-devices",1,0, 'x'},
dd0781e5
NB
126 {"size", 1, 0, 'z'},
127 {"auto", 2, 0, 'a'}, /* also for --assemble */
128 {"assume-clean",0,0, 3 },
64c4757e
NB
129
130 /* For assemble */
131 {"uuid", 1, 0, 'u'},
52826846 132 {"super-minor",1,0, 'm'},
64c4757e
NB
133 {"config", 1, 0, 'c'},
134 {"scan", 0, 0, 's'},
135 {"force", 0, 0, 'f'},
5787fa49 136 {"update", 1, 0, 'U'},
64c4757e
NB
137 /* Management */
138 {"add", 0, 0, 'a'},
139 {"remove", 0, 0, 'r'},
140 {"fail", 0, 0, 'f'},
141 {"set-faulty",0, 0, 'f'},
142 {"run", 0, 0, 'R'},
143 {"stop", 0, 0, 'S'},
144 {"readonly", 0, 0, 'o'},
145 {"readwrite", 0, 0, 'w'},
52826846 146
cd29a5c8
NB
147 /* For Detail/Examine */
148 {"brief", 0, 0, 'b'},
bd526cee 149 {"sparc2.2", 0, 0, 22},
feb716e9 150 {"test", 0, 0, 't'},
cd29a5c8 151
52826846
NB
152 /* For Follow/monitor */
153 {"mail", 1, 0, 'm'},
154 {"program", 1, 0, 'p'},
155 {"alert", 1, 0, 'p'},
156 {"delay", 1, 0, 'd'},
56eedc1a
NB
157 {"daemonise", 0, 0, 'f'},
158 {"daemonize", 0, 0, 'f'},
aa88f531 159 {"oneshot", 0, 0, '1'},
64c4757e
NB
160
161 {0, 0, 0, 0}
162};
163
164char Usage[] =
9a9dab36 165"Usage: mdadm --help\n"
64c4757e
NB
166" for help\n"
167;
168
169char Help[] =
9a9dab36
NB
170"Usage: mdadm --create device options...\n"
171" mdadm --assemble device options...\n"
172" mdadm --build device options...\n"
e0d19036
NB
173" mdadm --manage device options...\n"
174" mdadm --misc options... devices\n"
175" mdadm --monitor options...\n"
9a9dab36 176" mdadm device options...\n"
5787fa49 177" mdadm is used for building, managing, and monitoring\n"
56eedc1a
NB
178" Linux md devices (aka RAID arrays)\n"
179" For detailed help on the above major modes use --help after the mode\n"
e0d19036 180" e.g.\n"
9a9dab36 181" mdadm --assemble --help\n"
56eedc1a
NB
182" For general help on options use\n"
183" mdadm --help-options\n"
184;
185
186char OptionHelp[] =
64c4757e 187"Any parameter that does not start with '-' is treated as a device name\n"
e0d19036
NB
188"The first such name is often the name of an md device. Subsequent\n"
189"names are often names of component devices."
52826846 190"\n"
e0d19036 191"Some common options are:\n"
56eedc1a 192" --help -h : General help message or, after above option,\n"
64c4757e 193" mode specific help message\n"
56eedc1a 194" --help-options : This help message\n"
9a9dab36 195" --version -V : Print version information for mdadm\n"
64c4757e 196" --verbose -v : Be more verbose about what is happening\n"
e0d19036
NB
197" --brief -b : Be less verbose, more brief\n"
198" --force -f : Override normal checks and be more forceful\n"
199"\n"
200" --assemble -A : Assemble an array\n"
201" --build -B : Build a legacy array\n"
202" --create -C : Create a new array\n"
203" --detail -D : Display details of an array\n"
5787fa49 204" --examine -E : Examine superblock on an array component\n"
e0d19036
NB
205" --monitor -F : monitor (follow) some arrays\n"
206" --query -Q : Display general information about how a\n"
207" device relates to the md driver\n"
208;
209/*
64c4757e
NB
210"\n"
211" For create or build:\n"
212" --chunk= -c : chunk size of kibibytes\n"
5787fa49 213" --rounding= : rounding factor for linear array (==chunk size)\n"
98c6faba
NB
214" --level= -l : raid level: 0,1,4,5,6,linear,mp. 0 or linear for build\n"
215" --parity= -p : raid5/6 parity algorithm: {left,right}-{,a}symmetric\n"
64c4757e 216" --layout= : same as --parity\n"
b83d95f3
NB
217" --raid-devices= -n : number of active devices in array\n"
218" --spare-devices= -x: number of spares (eXtras) devices in initial array\n"
98c6faba 219" --size= -z : Size (in K) of each drive in RAID1/4/5/6 - optional\n"
52826846
NB
220" --force -f : Honour devices as listed on command line. Don't\n"
221" : insert a missing drive for RAID5.\n"
dd0781e5
NB
222" --auto(=p) -a : Automatically allocate new (partitioned) md array if needed.\n"
223" --assume-clean : Assume the array is already in-sync. This is dangerous.\n"
64c4757e
NB
224"\n"
225" For assemble:\n"
226" --uuid= -u : uuid of array to assemble. Devices which don't\n"
227" have this uuid are excluded\n"
52826846
NB
228" --super-minor= -m : minor number to look for in super-block when\n"
229" choosing devices to use.\n"
64c4757e
NB
230" --config= -c : config file\n"
231" --scan -s : scan config file for missing information\n"
232" --force -f : Assemble the array even if some superblocks appear out-of-date\n"
feb716e9 233" --update= -U : Update superblock: one of sparc2.2, super-minor or summaries\n"
dd0781e5 234" --auto(=p) -a : Automatically allocate new (partitioned) md array if needed.\n"
64c4757e 235"\n"
cd29a5c8
NB
236" For detail or examine:\n"
237" --brief -b : Just print device name and UUID\n"
238"\n"
52826846
NB
239" For follow/monitor:\n"
240" --mail= -m : Address to mail alerts of failure to\n"
241" --program= -p : Program to run when an event is detected\n"
242" --alert= : same as --program\n"
243" --delay= -d : seconds of delay between polling state. default=60\n"
244"\n"
64c4757e
NB
245" General management:\n"
246" --add -a : add, or hotadd subsequent devices\n"
247" --remove -r : remove subsequent devices\n"
248" --fail -f : mark subsequent devices a faulty\n"
249" --set-faulty : same as --fail\n"
250" --run -R : start a partially built array\n"
5787fa49 251" --stop -S : deactivate array, releasing all resources\n"
64c4757e
NB
252" --readonly -o : mark array as readonly\n"
253" --readwrite -w : mark array as readwrite\n"
9a9dab36 254" --zero-superblock : erase the MD superblock from a device.\n"
64c4757e 255;
e0d19036 256*/
64c4757e
NB
257
258char Help_create[] =
b83d95f3 259"Usage: mdadm --create device -chunk=X --level=Y --raid-devices=Z devices\n"
64c4757e 260"\n"
aa88f531
NB
261" This usage will initialise a new md array, associate some\n"
262" devices with it, and activate the array. In order to create an\n"
263" array with some devices missing, use the special word 'missing' in\n"
264" place of the relevant device name.\n"
64c4757e 265"\n"
aa88f531 266" Before devices are added, they are checked to see if they already contain\n"
e0d19036 267" raid superblocks or filesystems. They are also checked to see if\n"
64c4757e 268" the variance in device size exceeds 1%.\n"
aa88f531
NB
269" If any discrepancy is found, the user will be prompted for confirmation\n"
270" before the array is created. The presence of a '--run' can override this\n"
64c4757e
NB
271" caution.\n"
272"\n"
e0d19036
NB
273" If the --size option is given then only that many kilobytes of each\n"
274" device is used, no matter how big each device is.\n"
682c7051 275" If no --size is given, the apparent size of the smallest drive given\n"
e0d19036
NB
276" is used for raid level 1 and greater, and the full device is used for\n"
277" other levels.\n"
682c7051 278"\n"
e0d19036
NB
279" Options that are valid with --create (-C) are:\n"
280" --chunk= -c : chunk size of kibibytes\n"
5787fa49 281" --rounding= : rounding factor for linear array (==chunk size)\n"
98c6faba
NB
282" --level= -l : raid level: 0,1,4,5,6,linear,multipath and synonyms\n"
283" --parity= -p : raid5/6 parity algorithm: {left,right}-{,a}symmetric\n"
e0d19036 284" --layout= : same as --parity\n"
b83d95f3
NB
285" --raid-devices= -n : number of active devices in array\n"
286" --spare-devices= -x: number of spares (eXtras) devices in initial array\n"
98c6faba 287" --size= -z : Size (in K) of each drive in RAID1/4/5/6 - optional\n"
e0d19036
NB
288" --force -f : Honour devices as listed on command line. Don't\n"
289" : insert a missing drive for RAID5.\n"
aa88f531 290" --run -R : insist of running the array even if not all\n"
e0d19036 291" : devices are present or some look odd.\n"
aa88f531 292" --readonly -o : start the array readonly - not supported yet.\n"
64c4757e
NB
293"\n"
294;
295
296char Help_build[] =
b83d95f3 297"Usage: mdadm --build device -chunk=X --level=Y --raid-devices=Z devices\n"
64c4757e
NB
298"\n"
299" This usage is similar to --create. The difference is that it creates\n"
e0d19036 300" a legacy array without a superblock. With these arrays there is no\n"
64c4757e
NB
301" different between initially creating the array and subsequently\n"
302" assembling the array, except that hopefully there is useful data\n"
303" there in the second case.\n"
304"\n"
e0d19036 305" The level may only be 0, raid0, or linear.\n"
64c4757e 306" All devices must be listed and the array will be started once complete.\n"
e0d19036
NB
307" Options that are valid with --build (-B) are:\n"
308" --chunk= -c : chunk size of kibibytes\n"
5787fa49 309" --rounding= : rounding factor for linear array (==chunk size)\n"
e0d19036 310" --level= -l : 0, raid0, or linear\n"
b83d95f3 311" --raid-devices= -n : number of active devices in array\n"
64c4757e
NB
312;
313
314char Help_assemble[] =
9a9dab36
NB
315"Usage: mdadm --assemble device options...\n"
316" mdadm --assemble --scan options...\n"
64c4757e
NB
317"\n"
318"This usage assembles one or more raid arrays from pre-existing\n"
319"components.\n"
e0d19036 320"For each array, mdadm needs to know the md device, the identity of\n"
52826846
NB
321"the array, and a number of sub devices. These can be found in a number\n"
322"of ways.\n"
323"\n"
324"The md device is either given on the command line or is found listed\n"
325"in the config file. The array identity is determined either from the\n"
e0d19036 326"--uuid or --super-minor commandline arguments, from the config file,\n"
52826846 327"or from the first component device on the command line.\n"
64c4757e 328"\n"
52826846
NB
329"The different combinations of these are as follows:\n"
330" If the --scan option is not given, then only devices and identities\n"
331" listed on the command line are considered.\n"
e0d19036 332" The first device will be the array device, and the remainder will be\n"
52826846
NB
333" examined when looking for components.\n"
334" If an explicit identity is given with --uuid or --super-minor, then\n"
e0d19036 335" only devices with a superblock which matches that identity is considered,\n"
52826846 336" otherwise every device listed is considered.\n"
64c4757e 337"\n"
52826846
NB
338" If the --scan option is given, and no devices are listed, then\n"
339" every array listed in the config file is considered for assembly.\n"
e0d19036 340" The identity of candidate devices are determined from the config file.\n"
64c4757e 341"\n"
52826846
NB
342" If the --scan option is given as well as one or more devices, then\n"
343" Those devices are md devices that are to be assembled. Their identity\n"
344" and components are determined from the config file.\n"
64c4757e 345"\n"
e0d19036
NB
346"Options that are valid with --assemble (-A) are:\n"
347" --uuid= -u : uuid of array to assemble. Devices which don't\n"
348" have this uuid are excluded\n"
349" --super-minor= -m : minor number to look for in super-block when\n"
350" choosing devices to use.\n"
351" --config= -c : config file\n"
352" --scan -s : scan config file for missing information\n"
353" --run -R : Try to start the array even if not enough devices\n"
354" for a full array are present\n"
355" --force -f : Assemble the array even if some superblocks appear\n"
356" : out-of-date. This involves modifying the superblocks.\n"
feb716e9 357" --update= -U : Update superblock: one of sparc2.2, super-minor or summaries\n"
e0d19036
NB
358;
359
360char Help_manage[] =
361"Usage: mdadm arraydevice options component devices...\n"
362"\n"
363"This usage is for managing the component devices within an array.\n"
364"The --manage option is not needed and is assumed if the first argument\n"
365"is a device name or a management option.\n"
366"The first device listed will be taken to be an md array device, and\n"
367"subsequent devices are (potential) components of that array.\n"
368"\n"
369"Options that are valid with management mode are:\n"
370" --add -a : hotadd subsequent devices to the array\n"
371" --remove -r : remove subsequent devices, which must not be active\n"
372" --fail -f : mark subsequent devices a faulty\n"
373" --set-faulty : same as --fail\n"
374" --run -R : start a partially built array\n"
5787fa49 375" --stop -S : deactivate array, releasing all resources\n"
e0d19036
NB
376" --readonly -o : mark array as readonly\n"
377" --readwrite -w : mark array as readwrite\n"
378;
379
380char Help_misc[] =
381"Usage: mdadm misc_option devices...\n"
382"\n"
383"This usage is for performing some task on one or more devices, which\n"
384"may be arrays or components, depending on the task.\n"
385"The --misc option is not needed (though it is allowed) and is assumed\n"
386"if the first argument in a misc option.\n"
387"\n"
388"Options that are valid with the miscellaneous mode are:\n"
389" --query -Q : Display general information about how a\n"
390" device relates to the md driver\n"
391" --detail -D : Display details of an array\n"
5787fa49 392" --examine -E : Examine superblock on an array component\n"
e0d19036
NB
393" --zero-superblock : erase the MD superblock from a device.\n"
394" --run -R : start a partially built array\n"
5787fa49 395" --stop -S : deactivate array, releasing all resources\n"
e0d19036
NB
396" --readonly -o : mark array as readonly\n"
397" --readwrite -w : mark array as readwrite\n"
feb716e9 398" --test -t : exit status 0 if ok, 1 if degrade, 2 if dead, 4 if missing\n"
e0d19036
NB
399;
400
401char Help_monitor[] =
402"Usage: mdadm --monitor options devices\n"
403"\n"
404"This usage causes mdadm to monitor a number of md arrays by periodically\n"
405"polling their status and acting on any changes.\n"
406"If any devices are listed then those devices are monitored, otherwise\n"
407"all devices listed in the config file are monitored.\n"
408"The address for mailing advisories to, and the program to handle\n"
409"each change can be specified in the config file or on the command line.\n"
410"If no mail address or program are specified, then mdadm reports all\n"
411"state changes to stdout.\n"
412"\n"
dd0781e5 413"Options that are valid with the monitor (-F --follow) mode are:\n"
e0d19036
NB
414" --mail= -m : Address to mail alerts of failure to\n"
415" --program= -p : Program to run when an event is detected\n"
416" --alert= : same as --program\n"
417" --delay= -d : seconds of delay between polling state. default=60\n"
418" --config= -c : specify a different config file\n"
419" --scan -s : find mail-address/program in config file\n"
d013a55e 420" --daemonise -f : Fork and continue in child, parent exits\n"
aa88f531 421" --oneshot -1 : Check for degraded arrays, then exit\n"
98c6faba 422" --test -t : Generate a TestMessage event against each array at startup\n"
e0d19036
NB
423;
424
dd0781e5
NB
425char Help_grow[] =
426"Usage: mdadm --grow device options\n"
427"\n"
428"This usage causes mdadm to attempt to reconfigure a running array.\n"
429"This is only possibly if the kernel being used supports a particular\n"
430"reconfiguration. This version only supports changing the number of\n"
431"devices in a RAID1, and changing the active size of all devices in\n"
432"a RAID1/4/5/6.\n"
433"\n"
434"Options that are valid with the grow (-F --grow) mode are:\n"
435" --size= -z : Change the active size of devices in an array.\n"
436" : This is useful if all devices have been replaced\n"
437" : with larger devices.\n"
438" --raid-disks= -n : Change the number of active devices in a RAID1\n"
439" : array.\n"
440;
e0d19036
NB
441
442
443
444char Help_config[] =
445"The /etc/mdadm.conf config file:\n\n"
446" The config file contains, apart from blank lines and comment lines that\n"
447" start with a hash(#), four sorts of configuration lines: array lines, \n"
448" device lines, mailaddr lines and program lines.\n"
449" Each configuration line is constructed of a number of space separated\n"
450" words, and can be continued on subsequent physical lines by indenting\n"
451" those lines.\n"
452"\n"
453" A device line starts with the word 'device' and then has a number of words\n"
454" which identify devices. These words should be names of devices in the\n"
455" filesystem, and can contain wildcards. There can be multiple words or each\n"
456" device line, and multiple device lines. All devices so listed are checked\n"
457" for relevant super blocks when assembling arrays.\n"
458"\n"
459" An array line start with the word 'array'. This is followed by the name of\n"
460" the array device in the filesystem, e.g. '/dev/md2'. Subsequent words\n"
461" describe the identity of the array, used to recognise devices to include in the\n"
462" array. The identity can be given as a UUID with a word starting 'uuid=', or\n"
463" as a minor-number stored in the superblock using 'super-minor=', or as a list\n"
464" of devices. This is given as a comma separated list of names, possibly\n"
5787fa49 465" containing wildcards, preceded by 'devices='. If multiple critea are given,\n"
e0d19036
NB
466" than a device must match all of them to be considered.\n"
467"\n"
468" A mailaddr line starts with the word 'mailaddr' and should contain exactly\n"
469" one Email address. 'mdadm --monitor --scan' will send alerts of failed drives\n"
470" to this Email address."
471"\n"
472" A program line starts with the word 'program' and should contain exactly\n"
473" one program name. 'mdadm --monitor --scan' will run this program when any\n"
474" event is detected.\n"
64c4757e
NB
475"\n"
476;
682c7051
NB
477
478
479/* name/number mappings */
480
481mapping_t r5layout[] = {
cd29a5c8
NB
482 { "left-asymmetric", 0},
483 { "right-asymmetric", 1},
484 { "left-symmetric", 2},
485 { "right-symmetric", 3},
682c7051
NB
486
487 { "default", 2},
488 { "la", 0},
489 { "ra", 1},
490 { "ls", 2},
491 { "rs", 3},
492 { NULL, 0}
493};
494
495mapping_t pers[] = {
496 { "linear", -1},
497 { "raid0", 0},
498 { "0", 0},
499 { "stripe", 0},
500 { "raid1", 1},
501 { "1", 1},
502 { "mirror", 1},
503 { "raid4", 4},
504 { "4", 4},
505 { "raid5", 5},
506 { "5", 5},
e0d19036
NB
507 { "multipath", -4},
508 { "mp", -4},
98c6faba
NB
509 { "raid6", 6},
510 { "6", 6},
682c7051
NB
511 { NULL, 0}
512};
e0d19036
NB
513
514
515mapping_t modes[] = {
516 { "assemble", ASSEMBLE},
517 { "build", BUILD},
518 { "create", CREATE},
519 { "manage", MANAGE},
520 { "misc", MISC},
521 { "monitor", MONITOR},
dd0781e5 522 { "grow", GROW},
e0d19036 523};