I've been experimenting with "Using preseeding to change default
values"
[https://www.debian.org/releases/stable/i386/apbs05.html.en#preseed-seenflag]
.
I've discovered that it does not work unless "priority=critical"
is changed to "priority=high" in boot parameters.
I see several problems:
1. "B.5.2. Using preseeding to change default values" makes no
mention that
this is required.
2. "5.3.2. Debian Installer Parameters" states:
'The default installation uses priority=high. This
means that both high
and critical priority messages are shown, but medium
and low priority
messages are skipped. If problems are encountered,
the installer adjusts
the priority as needed.'
There are two problems there:
A. If automatic is chosen from install menu,
"priority=critical" is the
default is actually for Squeeze and Wheezy [Unable to
verify for Jessie].
B. the above statement would suggest use of "d-i foo/bar
seen false" should
force priority to be lowered.
3. Chapter 2 of "Debian Installer internals" also states:
'In some situations the debconf priority is
automatically changed. It
is reduced when the execution of a component fails,
or when the user
uses the <Go Back> button to back out all the way to
the menu. In these
cases it will also be increased back to the original
level when the next
component executed finishes successfully.'
Should this bug be reported against installer or the documentation?
Having only dialup and thus unable to download Jessie, is it
correct to report it as a possible bug in Jessie also?
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53963c2a.3070...@cloud85.net
