| 1 |
<!-- retain these comments for translator revision tracking -->
|
| 2 |
<!-- $Id$ -->
|
| 3 |
|
| 4 |
<sect1 id="example-preseed">
|
| 5 |
<title>Preconfiguration File Example</title>
|
| 6 |
|
| 7 |
<para>
|
| 8 |
|
| 9 |
This is a complete working example of a preconfiguration file for an automated
|
| 10 |
install. Its use is explained in <xref linkend="automatic-install"/>. You
|
| 11 |
may want to uncomment some of the lines before using the file.
|
| 12 |
|
| 13 |
</para>
|
| 14 |
|
| 15 |
<note condition="sarge"><para>
|
| 16 |
|
| 17 |
In order to be able to properly present this example in the manual, we've had
|
| 18 |
to split some lines. This is indicated by the use of the line-continuation-character
|
| 19 |
<quote>\</quote> and extra indentation in the next line. In a real preconfiguration
|
| 20 |
file, these split lines have to be joined into <emphasis>one single line</emphasis>.
|
| 21 |
If you do not, preconfiguration will fail with unpredictable results.
|
| 22 |
|
| 23 |
</para><para>
|
| 24 |
|
| 25 |
A <quote>clean</quote> example file is available from &urlset-example-preseed;.
|
| 26 |
|
| 27 |
</para></note>
|
| 28 |
|
| 29 |
<para condition="etch">
|
| 30 |
|
| 31 |
The example file is also available from &urlset-example-preseed;.
|
| 32 |
|
| 33 |
</para><para>
|
| 34 |
|
| 35 |
&example-preseed-sarge.xml;
|
| 36 |
&example-preseed-etch.xml;
|
| 37 |
|
| 38 |
</para>
|
| 39 |
</sect1>
|