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

Re: Problems and questions with preseeding



On Mon 08 Apr 2013 at 10:20:51 +0100, Philip Hands wrote:

> 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.

Hello Philip,

The documentation is concise and accurate. However, it was written for
Etch. So when it says:

   There are several features of Debian Installer that combine 
   to allow fairly simple command lines at the boot prompt to 
   result . . .

we will recollect that a user at that time would have been presented
with a visible Syslinux boot prompt on booting into d-i.

In Wheezy that prompt is "hidden" but can be accessed from the "Help" 
entry of the Boot Screen. (Section 5.1.7.)

My feeling is that a user reading

   Press ENTER to boot or TAB to edit a menu entry

may see TAB as bringing up a boot prompt, rather than simply a way of
editing the kernel command line. I suppose it actually is a boot prompt
- just not a Syslinux one.

I would suggest an interim solution of linking the term "boot prompt" in 
Section B.2.3. to Section 5.1.7. or referencing the "Help" entry.

The use of "boot prompt" throughout the Manual is unsatisfactory. For 
example, Section D.4.3:

   If you need to set parameters for kernel modules, you also 
   need to do this at the boot prompt.

Now - which boot prompt is that?

Regards,

Brian.


Reply to: