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

Bug#704881: Method to obtain minimum preseed file

Philip Hands, le Mon 08 Apr 2013 20:20:30 +0100, a écrit :
> Samuel Thibault <sthibault@debian.org> writes:
> > martin f krafft, le Sun 07 Apr 2013 06:40:37 +0200, a écrit :
> >> As far as I can tell, d-i has all the information, and even leaving
> >> a fully-commented pressed.cfg file in /var/log/installer after the
> >> installation should be doable.
> >
> > Did you read section B.3. "Creating a preconfiguration file" of the
> > installation manual?
> >
> > “
> > An alternative method is to do a manual installation and then, after
> > rebooting, use the debconf-get- selections from the debconf-utils
> > package to dump both the debconf database and the installer's cdebconf
> > database to a single file:
> Doesn't that include _all_ settings, including those that were derived
> automatically ...


> so not the minimum preseed that Martin was hoping for.

Ah, ok, I hadn't understood that.

> I've certainly wished that there was a simple way of discovering which
> questions were actually asked of the user, as a hint towards what still
> needed to be preseeded,

I'm not sure debconf actually makes a distinction between what was
provided interactively by the user, and what was provided from scripts.

> and the closest I was aware of to that would be
> to turn up debugging, and then trawl through the resulting log, but I've
> not been trying it recently, so perhaps there's a better way these days.


Reply to: