merge in ex-base-config branch

1 files changed, 0 insertions, 65 deletions

diff --git a/en/install-methods/automatic-install.xml b/en/install-methods/automatic-install.xml
index f15c936b4..8cc630867 100644
--- a/en/install-methods/automatic-install.xml
+++ b/en/install-methods/automatic-install.xml
@@ -29,71 +29,6 @@ installation process.
 Full documentation on preseeding including a working example that you can
 edit is in <xref linkend="appendix-preseed"/>.
 
-</para><para condition="sarge">
-
-Although most dialogs used by &d-i; can be preseeded using this method,
-there are some notable exceptions. You can (re)partition an entire disk
-or use available free space on a disk; it is not possible to use existing
-partitions. You currently cannot use preseeding to set up RAID and LVM.
-Also, with the exception of network driver modules, it is not possible
-to preconfigure kernel module parameters.
-
-</para><para condition="sarge">
-
-The preconfiguration file is in the format used by the
-debconf-set-selections command. A well documented and working example
-that you can edit is in <xref linkend="example-preseed"/>.
-
-</para><para condition="sarge">
-
-Alternatively, one way to get a complete file listing
-all the values that can be preseeded is to do a manual install,
-and then use <filename>debconf-get-selections</filename>,
-from the <classname>debconf-utils</classname> package,
-to dump both the debconf database and the cdebconf
-database in /var/log/debian-installer/cdebconf to a single file:
-
-<informalexample><screen>
-$ debconf-get-selections --installer &gt; <replaceable>file</replaceable>
-$ debconf-get-selections &gt;&gt; <replaceable>file</replaceable>
-</screen></informalexample>
-
-However, a file generated in this manner will have some items that should
-not be preseeded, and the file in <xref linkend="example-preseed"/> is a
-better starting place for most users.
-
-</para><para condition="sarge">
-
-Once you have a preconfiguration file, you can edit it if necessary, and
-place it on a web server, or copy it onto the installer's boot media. Wherever
-you place the file, you need to pass a parameter to the installer at boot
-time to tell it to use the file.
-
-</para><para condition="sarge">
-
-To make the installer use a preconfiguration file downloaded from the
-network, add preseed/url=http://url/to/preseed.cfg to the kernel boot
-parameters. Of course the preconfiguration will not take effect until the
-installer manages to set up the network to download the file, so this is
-most useful if the installer can set up the network via DHCP without asking
-any questions. You may want to set the installation priority to critical to
-avoid any questions while the network is being configured. See
-<xref linkend="installer-args"/>.
-
-</para><para condition="sarge">
-
-To place a preconfiguration file on a CD, you would need to remaster the
-ISO image to include your preconfiguration file. See the manual page for
-mkisofs for details. Alternatively, put the preseed file on a floppy, and
-use preseed/file=/floppy/preseed.cfg
-
-</para><para arch="i386" condition="sarge">
-
-If you'll be booting from a USB memory stick, then you can simply copy your
-preconfiguration file onto the memory stick's filesystem, and edit the
-syslinux.cfg file to add preseed/file=/hd-media/preseed.cfg to the kernel boot
-parameters.
-
 </para>
   </sect2>
  </sect1>