Bug#852158: Preseeding debconf/priority causes main menu to display
On Mon, Jan 23, 2017 at 08:16:02PM +0100, Philip Hands wrote:
> Josh Triplett <josh@joshtriplett.org> writes:
>
> > On Sun, Jan 22, 2017 at 06:46:14PM +0100, Philip Hands wrote:
> >> Josh Triplett <josh@joshtriplett.org> writes:
> >> > Package: main-menu
> >> > Severity: normal
> >> >
> >> > I'd like to use preseeding to pre-answer some questions in the
> >> > installer, while leaving others for the user to answer, including
> >> > questions asked with priority "high". Using "auto url=..." sets the
> >> > priority to critical, so I tried including the following in my preseed
> >> > file:
> >> >
> >> > d-i debconf/priority high
> >>
> >> Not a direct answer to the question you're asking, but you can get what
> >> you want without having to preseed the priority back down again.
> >>
> >> The 'auto' target is a shortcut that adds priority=critical and
> >> auto=true so if you don't want the priority setting just add 'auto=true'
> >> as well as the url setting to the normal target (IIRC 'install'), so:
> >>
> >> install auto=true url=...
> >
> > Yes, I managed to get that working in a VM. It's longer to type,
> > though. :)
> >
> > More importantly, leaving the priority at "high" for the initial run of
> > netcfg causes it to prompt for hostname and domain before it obtains and
> > loads the preseed file. Hence wanting to start out at "critical" and
> > then lower the priority after processing the preseed file.
>
> Good point -- does this perhaps point towards needing to make the
> setting of auto=true delay the asking of the hostname and domain until
> after preseeding, as with the keyboard/locale questions?
>
> I know it's a bit odd to ask those questions after the network comes up,
> but if one has set auto=true then you either need to set those on the
> command line or in an initrd preseed say, or you need the network to
> come up without them being set, so it makes sense to delay the
> processing of those settings until later -- IIRC this is something that
> is a bit broken anyway, since preseeding the hostname doesn't do what
> one might hope some of the time (unless that's been fixed while I wasn't
> paying attention -- I'm pretty sure it used to be the case that the
> hostname on the target would not be changed if one set these during
> network preseeding).
Yeah, I'd prefer to have those questions deferred until after
preseeding. That way, for instance, I could preseed the domain but not
the hostname, eliminating one more question.
- Josh Triplett
Reply to: