DNS tasksel never ends in bind9 install when no NIC found

Bug #145505 reported by Nick Barcet on 2007-09-27
Affects Status Importance Assigned to Milestone
bind9 (Ubuntu)
LaMont Jones

Bug Description

Binary package hint: tasksel

Installed Ubuntu 64 bit Gutsy Beta1 server on a VMWare where the NIC did not get reognized (see bug#145503)
Selected DNS in the tasksel selector in the installer
Install of bind9 never ended...

Colin Watson (cjwatson) wrote :

This is bind9's fault, not tasksel's.

LaMont Jones (lamont) on 2007-11-07
Changed in bind9:
assignee: nobody → lamont
importance: Undecided → Low
milestone: none → ubuntu-8.04
status: New → In Progress
LaMont Jones (lamont) wrote :

Actually, it's the kernel's fault that the timeout is longer than the submitter's patience. Don't run network daemons on unnetworked hosts.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers