Behavior in current Grml versions
---------------------------------
-This section applies to all Grml versions newer than release 2009.05.
+This section applies to all Grml versions newer than release 2013.02.
The central concept of grml-autoconfig is the DCS directory which holds debs,
configuration and scripts which are used during system startup.
Determination of DCS directory
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-The DCS directory defaults to the root directory of the GRML live image. If a
-file system labeled GRMLCFG is found, the DCS directory is the root directory of
-that file system. Alternatively, the myconfig boot parameter can be used to
-directly specify a device which is then taken as DCS directory
-(myconfig=/dev/sda1, for example). If your device is labeled different to
-GRMLCFG the proper label can be set via the autoconfig boot parameter
-(autoconfig=SOMELABEL, for example).
+The DCS directory defaults to the root directory of the GRML live image
+(Note: the directory is known as /lib/live/mount/medium/ on a _running_
+Grml system then!). If a file system labeled GRMLCFG is found, the DCS
+directory is the root directory of that file system. Alternatively, the
+myconfig boot parameter can be used to directly specify a device which
+is then taken as DCS directory (myconfig=/dev/sda1, for example). If
+your device is labeled different to GRMLCFG the proper label can be set
+via the autoconfig boot parameter (autoconfig=SOMELABEL, for example).
Without any additional boot parameters, the GCA at DCSDIR/config.tbz is
-automatically unpacked and DCSDIR/scrips/grml.sh is automatically executed on
+automatically unpacked and DCSDIR/scripts/grml.sh is automatically executed on
system startup. The 'noautoconfig' boot parameter disables this automatic
behavior.
device. Usage examples:
myconfig=/dev/sda1 => read DCS from usb-device
- myconfig=/dev/fd0 => read DCS from floppy-disk
autoconfig::
relative to DCSDIR. If the path points to a file, this single file is
executed. If no path is given, it defaults to scripts/grml.sh.
If the given name points to a directory, all scripts inside it are
- executed, but the run-parts name restrictions apply: script names must
- consist entirely of upper and lower case letters, digits, underscores,
- and hyphens. Usage examples:
+ executed. Usage examples:
scripts => run script DCSDIR/scripts/grml.sh
scripts=foobar.sh => run script foobar.sh in DCSDIR
noautoconfig::
Deactivate automounting. By default the scripts try to mount a device with
- label 'GRMLCFG'. If you specify the noautoconfig bootparam this automounting
- will be deactivated.
+ label 'GRMLCFG'. If you specify the noautoconfig boot parameter this
+ automounting will be deactivated.
noautoconfig => disables auto mounting of label 'GRMLCFG'
Permanently adjust boot parameters
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-As you probably know you can adjust boot parameters on the bootprompt. You want
-to set some boot parameters permanently? That's possible via adding a directory
-named 'bootparams' to the Grml ISO which has to be located at the root-directory
-/bootparams/ (note: the directory is known as /live/image/bootparams/ on a
-_running_ Grml system then). Place a textfile inside the directory containing
-the boot parameters which should be appended to default ones (this corresponds
-to booting without any special parameters).
+As you probably know you can adjust boot parameters on the bootprompt.
+You want to set some boot parameters permanently? That's possible via
+adding a directory named 'bootparams' to the Grml ISO which has to be
+located at the root-directory /bootparams/ (Note: the directory is known
+as /lib/live/mount/medium/bootparams/ on a _running_ Grml system then!).
+Place a textfile inside the directory containing the boot parameters
+which should be appended to default ones (this corresponds to booting
+without any special parameters).
mkdir bootparams
echo lang=de > bootparams/my_bootparams
projects / grml-autoconfig.git / blobdiff