On Mon, Jun 2, 2014 at 6:22 PM, Richard Owlett wrote:
> Brian wrote:
>> On Mon 02 Jun 2014 at 15:13:24 -0500, Richard Owlett wrote:
>>>
>>> The problem actually revolves around the installer (both Squeeze and
>>> Wheezy) default boot line including "priority=critical" for an
>>> automatic install.
Brian wrote:
On Mon 02 Jun 2014 at 15:13:24 -0500, Richard Owlett wrote:
The problem actually revolves around the installer (both Squeeze and
Wheezy) default boot line including "priority=critical" for an
automatic install. I have not satisfied myself whether that should
be reported as a bug ag
On Mon 02 Jun 2014 at 15:13:24 -0500, Richard Owlett wrote:
> The problem actually revolves around the installer (both Squeeze and
> Wheezy) default boot line including "priority=critical" for an
> automatic install. I have not satisfied myself whether that should
> be reported as a bug against in
Curt wrote:
On 2014-05-31, Richard Owlett wrote:
tasksel tasksel/first seen false
That's one of the failures.
Has that worked for anyone?
I dunno.
How about:
tasksel tasksel/first multiselect standard, desktop
d-i preseed/early_command string . /usr/share/debconf/confmodule; db_get
debco
On Sun 01 Jun 2014 at 08:27:09 -0500, Richard Owlett wrote:
> Richard Owlett wrote:
> >Debian GNU/Linux Installation Guide
> > Appendix B. Automating the installation using preseeding
> > B.5.2. Using preseeding to change default values
> >AND
> > B.2.2. Using
Richard Owlett wrote:
Debian GNU/Linux Installation Guide
Appendix B. Automating the installation using preseeding
B.5.2. Using preseeding to change default values
AND
B.2.2. Using boot parameters to preseed questions
suggest that I should be able to accom
On 2014-05-31, Richard Owlett wrote:
>>
>> tasksel tasksel/first seen false
>
> That's one of the failures.
> Has that worked for anyone?
I dunno.
How about:
tasksel tasksel/first multiselect standard, desktop
d-i preseed/early_command string . /usr/share/debconf/confmodule; db_get
debconf/prio
[My headache is turning into a migraine.]
On Sat 31 May 2014 at 16:20:38 -0500, Richard Owlett wrote:
> Brian wrote:
> >[Please don't shout. I've got a headache.]
> >
> >Do you think it might help if we had details of the tests done?
>
> No!
>
> Only one of the tests was relevant to my stated g
Curt wrote:
On 2014-05-27, Richard Owlett wrote:
My goal is to force the menu which asks to chose among typical
uses (i.e. Desktop|print server|laptop|etc).
Have you tried
# set the default
tasksel tasksel/first multiselect standard, desktop
# have the question asked anyway
tasksel tasksel
Brian wrote:
[Please don't shout. I've got a headache.]
On Sat 31 May 2014 at 06:35:55 -0500, Richard Owlett wrote:
Brian wrote:
Using preseeding to set a default answer for a question but still have
the question asked is described. Is there anything there which is not
amenable to a quick te
On 2014-05-27, Richard Owlett wrote:
>
> My goal is to force the menu which asks to chose among typical
> uses (i.e. Desktop|print server|laptop|etc).
>
Have you tried
# set the default
tasksel tasksel/first multiselect standard, desktop
# have the question asked anyway
tasksel tasksel/first se
[Please don't shout. I've got a headache.]
On Sat 31 May 2014 at 06:35:55 -0500, Richard Owlett wrote:
> Brian wrote:
> >
> >Using preseeding to set a default answer for a question but still have
> >the question asked is described. Is there anything there which is not
> >amenable to a quick test
Brian wrote:
On Tue 27 May 2014 at 08:19:24 -0500, Richard Owlett wrote:
Debian GNU/Linux Installation Guide
Appendix B. Automating the installation using preseeding
B.5.2. Using preseeding to change default values
AND
B.2.2. Using boot parameters to pre
On Tue 27 May 2014 at 08:19:24 -0500, Richard Owlett wrote:
> Debian GNU/Linux Installation Guide
> Appendix B. Automating the installation using preseeding
> B.5.2. Using preseeding to change default values
>AND
> B.2.2. Using boot parameters to preseed quest
14 matches
Mail list logo
