this would be very helpful! either that or
the actual debconf-get-selection keys in raw text somewhere on the installer
(maybe on the top line), maybe not by default, but with some boot kernel
paramater
to activate...
Yours
Gurkan
--
To UNSUBSCRIBE, email to
also sprach Philip Hands p...@hands.com [2009.10.29.1303 +]:
If we were to add some hints to the question templates to indicate how
relevant a question is to preseeding, along with perhaps a udeb for
asking the intent questions that are vital to an auto-install, but will
never get asked in
also sprach Holger Levsen hol...@layer-acht.org [2009.10.28.1121 +0100]:
On Dienstag, 27. Oktober 2009, martin f krafft wrote:
Since debconf-get-selections is not the appropriate way to create
preseed.cfg files,
why not? because you think it's hackish, suboptimal or..?
So says the
On Wed, Oct 28, 2009 at 03:08:50PM +0100, martin f krafft wrote:
also sprach Holger Levsen hol...@layer-acht.org [2009.10.28.1121 +0100]:
On Dienstag, 27. Oktober 2009, martin f krafft wrote:
Since debconf-get-selections is not the appropriate way to create
preseed.cfg files,
why
On Tuesday 27 October 2009, martin f krafft wrote:
Since debconf-get-selections is not the appropriate way to create
preseed.cfg files, but d-i should know what keys to save (or not to
save), why not extend d-i so that it automatically drops
a preseed.cfg file into /root (next to the
Hi Martin,
On Dienstag, 27. Oktober 2009, martin f krafft wrote:
Since debconf-get-selections is not the appropriate way to create
preseed.cfg files,
why not? because you think it's hackish, suboptimal or..?
regards,
Holger
signature.asc
Description: This is a digitally signed
Package: debian-installer
Version: 20091026-1
Severity: wishlist
Usertags: debianbook
Since debconf-get-selections is not the appropriate way to create
preseed.cfg files, but d-i should know what keys to save (or not to
save), why not extend d-i so that it automatically drops
a preseed.cfg file
7 matches
Mail list logo
