On 18/12/2018 13:19, Hendrik Boom wrote:
> On Mon, Dec 17, 2018 at 10:51:53PM -0500, Steve Litt wrote:
>> On Sun, 16 Dec 2018 13:28:43 +0100
>> KatolaZ <katolaz@???> wrote:
>
>> Also, Hendrik is right: If the bootable installer
>> finds information, it should be saved for the secondary installer to
>> use.
>
> It would be enough if the software the bootable installer used were
> still available after the minimal installation to find out the same
> information again. And if it were clearly documented how the user
> could go about this.

The concept I have in mind is that the questions answered and steps taken
during install are saved as a dual purpose log\preseed file.

Both the installer and customiser would support acting upon (unattended)
and generating these files.

This is nothing new, Red Hat did (still do?) this with Anaconda Installer.


To support your view, the customiser 'could' be written to also parse the
installer log\preseed and extract relevant information from it.


>
>> But no need for the bootable installer to go out of its way to
>> find these things out.
>>
>> SteveT
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>