summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLoui Chang <louipc.ist@gmail.com>2009-08-04 13:56:45 +0200
committerAaron Griffin <aaronmgriffin@gmail.com>2009-08-05 19:29:21 +0200
commit8ae9a3c46d21dbf8ccb104daedbeaf2a98afb838 (patch)
treeaedb822418869a9ca95092a7fad749f024312089
parent7797debad9c55949482e111992c3cd10b221809f (diff)
downloadmkinitcpio-8ae9a3c46d21dbf8ccb104daedbeaf2a98afb838.tar.gz
mkinitcpio-8ae9a3c46d21dbf8ccb104daedbeaf2a98afb838.tar.xz
Update man page to reflect current usage of HOOKS.
Signed-off-by: Loui Chang <louipc.ist@gmail.com> Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
-rw-r--r--mkinitcpio.5.txt6
1 files changed, 4 insertions, 2 deletions
diff --git a/mkinitcpio.5.txt b/mkinitcpio.5.txt
index 868225e..92aa67d 100644
--- a/mkinitcpio.5.txt
+++ b/mkinitcpio.5.txt
@@ -59,8 +59,10 @@ Options
About Hooks
-----------
-A hook is a script that executes in the initial ramdisk. The order and which scripts are executed is found in the
-*HOOKS*=() array in the mkinitcpio configuration file. A hook will, for example, set up the udev device filesystem, load IDE modules, etc...
+A hook is a script that executes in the initial ramdisk. Scripts are
+listed in order of execution as a space separated string in the *HOOKS*
+variable in the mkinitcpio configuration file. Hooks can, for example,
+set up the udev device filesystem, load IDE modules, etc.
About Presets
-------------