Starting with Grml release 2009.05 its possible to use root persistency on grml.
This means you can store your settings and reuse them on reboot, without having
to deal with this config framework. Visit
-link:http://wiki.grml.org/doku.php?id=persistency for further information.
+link:http://wiki.grml.org/doku.php?id=persistency[] for further information.
[[current-versions]]
include::grml-autoconfig.current.txt[]
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
+/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 debs/ && cp foobar.deb debs/
-Notice: This directory will be located in /live/image after burning the second
+Notice: This directory will be located in /lib/live/mount/medium after burning the second
session.
Now create the second session containing this directory:
Run your own commands on startup
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-You know that booting with 'grml service=foobar' executes /etc/init.d/foobar
+You know that booting with 'grml services=foobar' executes /etc/init.d/foobar
when booting Grml. But you want to setup a more complex network configuration,
adjust some other stuff and so on on your own? Just write a script named grml.sh
which does the job and use own of the mentioned bootparams. Let's say you have
Bugs
----
-If you find a bug please report it. See link:http://grml.org/bugs/ for details
+If you find a bug please report it. See link:http://grml.org/bugs/[] for details
about how to report bugs.
See also