From 71e79815316c857fa273d51f19ee7cf702cce65e Mon Sep 17 00:00:00 2001 From: Frans Pop Date: Mon, 10 Apr 2006 11:28:03 +0000 Subject: Fix PDF build errors --- en/appendix/preseed.xml | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-) (limited to 'en/appendix') diff --git a/en/appendix/preseed.xml b/en/appendix/preseed.xml index bf02a3bb3..5187a6a45 100644 --- a/en/appendix/preseed.xml +++ b/en/appendix/preseed.xml @@ -160,8 +160,6 @@ use the same template. The following types of templates are relevant for preseeding. - - string: allows the user to type any value @@ -183,7 +181,7 @@ The following types of templates are relevant for preseeding. - + In &d-i; templates are stored in a readable file /var/cache/debconf/templates.dat. This file contains all fixed @@ -422,27 +420,32 @@ a line in a preconfiguration file is: There are a few rules to keep in mind when writing a preconfiguration file. + + - + Put only a single space or tab between type and value: any additional whitespace will be interpreted as belonging to the value. - + + A line can be split into multiple lines by appending a backslash (\) as the line continuation character. A good place to split a line is after the template name; a bad place is between type and value. - + + Most templates need to be preseeded using the values valid in English and not the translated values. However, there are some templates (for example in partman where the translated values need to be used. - + + Some templates take a code as value instead of the English text that is shown during installation. - + - + The easiest way to create a preconfiguration file is to use the example file linked in as basis and work from there. -- cgit v1.2.3