[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Problems and questions with preseeding



On Mon, Apr 08, 2013 at 10:20:51AM +0100, Philip Hands wrote:
> Hi Regid,
> 
> Regid Ichira <regid23@nt1.in> writes:
> > 1. The auto alias doesn't work.  auto=true does work.  In fact, the
> >    installation guide has contradictory saying on this issue.
> >    http://d-i.debian.org/manual/en.i386/apbs02.html, B.2. Using 
> >    preseeding, has examples with only auto, without a value.  And
> >    further down that page, it is written that a value is always
> >    required.
> 
> The problem here is that in one context, it's talking about a syslinux
> label "auto" which allows you to select a kernel command line that
> includes the kernel parameters:
> 
>   auto=true priority=critical
> 
> when compared to the other labels (i.e. expert, rescue, install, ...)
> 
> This can been seen looking at i.e.:
> 
>   debian-svn/d-i/installer/build/boot/x86/adtxt.cfg
> 
> which includes:
> 
> =-=-=-=-
> label auto
>         menu label ^Automated install
>         kernel ${KERNEL}
>         append desktop=%desktop% auto=true priority=critical ${VIDEO_MODE} initrd=${INITRD} -- quiet ${CONSOLE}
> =-=-=-=-
> 
> In the other context it's talking about preseed aliases, where if one
> specifies a parameter on the kernel command line (so at the end of the
> line, rather than at the start) then if you put auto=true, it gets
> expanded to auto-install/enable=true, which is then used for preseeding
> the value.
> 
> Assuming that that explanation makes sense, and is true as far as you're
> concerned, perhaps you would be kind enough to suggest some way of
> improving the documentation, since this is not the first time it has
> caused this confusion.
> 


1. auto=true with priority=critical took care of not being asked to
   verify the host and domain name.  The dhcp server serves them.
2. My suggestion to improve the documentation is to move a paragrph
   that is alreay there more close to the example.  Along with adding
   a few lines about when auto is taken from the syslinux boot label.

diff -Naurp apbs02.html*:

--- apbs02.html	2013-04-09 15:53:43.000000000 +0300
+++ apbs02.html.mod	2013-04-09 19:56:06.000000000 +0300
@@ -207,7 +207,28 @@ auto url=autoserver
 </pre></div>
 <p>
 
-This relies on there being a DHCP server that will get the machine to
+The <code class="literal">auto</code> boot label is not yet defined everywhere. 
+Here it is actually a syslinux boot label. As such, it is meant to be consumed by syslinux.
+All the other boot parameters that are mentioned in this page are recognized either
+by the installer or by the kernel, and are meant to be consumed by them.
+Users with a crafted installer, crafted syslinux settings, or where syslinux is not used, might fall into 
+the group where a plain <code class="literal">auto</code>, as opposed to
+<code class="literal">auto=true</code>, will be silently ignored. 
+The same effect of the syslinux <code class="literal">auto</code> boot label may be achieved by simply adding the two
+parameters <code class="literal">auto=true priority=critical</code> to the kernel
+command line.  The <code class="literal">auto</code> parameter is an alias for
+<code class="literal">auto-install/enable</code> and setting it to
+<code class="literal">true</code> delays the
+locale and keyboard questions until after there has been a chance to
+preseed them, while <code class="literal">priority</code> is an alias for
+<code class="literal">debconf/priority</code> and setting it to
+<code class="literal">critical</code> stops any questions with a lower priority
+from being asked.
+
+</p>
+<p>
+
+Obvoiusly, using <code class="literal">url=autoserver</code> here also relies on there being a DHCP server that will get the machine to
 the point where <code class="literal">autoserver</code> can be resolved by DNS,
 perhaps after adding the local domain if that was provided by DHCP.
 If this was done at a site where the domain is
@@ -301,21 +322,6 @@ for you.
 
 </p>
 <p>
-
-The <code class="literal">auto</code> boot label is not yet defined everywhere.
-The same effect may be achieved by simply adding the two
-parameters <code class="literal">auto=true priority=critical</code> to the kernel
-command line.  The <code class="literal">auto</code> parameter is an alias for
-<code class="literal">auto-install/enable</code> and setting it to
-<code class="literal">true</code> delays the
-locale and keyboard questions until after there has been a chance to
-preseed them, while <code class="literal">priority</code> is an alias for
-<code class="literal">debconf/priority</code> and setting it to
-<code class="literal">critical</code> stops any questions with a lower priority
-from being asked.
-
-</p>
-<p>
 
 Additional options that may be of interest while attempting to
 automate an install while using DHCP are: <code class="literal">interface=auto


Reply to: