- * This version introduces an additional package named grml-live-db.
- The grml-live-db Debian package provides a simple way to put build
- information of grml-live into a database. By default you have to do
- nothing but install grml-live-db and during each invocation of
- grml-live you'll get an additional entry in the sqlite3 database
- /var/log/grml-live.db. If you want to customize the database logging
- check out the grml-live-db manpage.
-
- * Instead of ZERO_LOGFILE a new variable titled PRESERVE_LOGFILE has
- been introduced. By default grml-live cleans the build logfile so
- grml-live-db can work straight out-of-the-box. If you still want to
- preserve your logfiles (e.g. when you don't want to use
- grml-live-db) just enable the PRESERVE_LOGFILE option in your
- grml-live configuration file. For backwards compability reasons the
- ZERO_LOGFILE variable is still supported within grml-live but it's
- strongly recommended to adjust configuration.
+ This version introduces an additional package named grml-live-db.
+ The grml-live-db Debian package provides a simple way to put build
+ information of grml-live into a database. By default you have to do
+ nothing but install grml-live-db and during each invocation of
+ grml-live you'll get an additional entry in the sqlite3 database
+ /var/log/grml-live.db. If you want to customize the database logging
+ check out the grml-live-db manpage.
+
+ Instead of ZERO_LOGFILE a new variable titled PRESERVE_LOGFILE has
+ been introduced. By default grml-live cleans the build logfile so
+ grml-live-db can work straight out-of-the-box. If you still want to
+ preserve your logfiles (e.g. when you don't want to use
+ grml-live-db) just enable the PRESERVE_LOGFILE option in your
+ grml-live configuration file. For backwards compatibility reasons the
+ ZERO_LOGFILE variable is still supported within grml-live but it's
+ strongly recommended to adjust configuration.