Bug#57111: Forced network install

[Stefan Gybas <stefan@gybas.com>]

Ross Boylan wrote:

> [I had just prepared this when I saw 57111.  I think it's the same problem.]

No, they are not. 57111 is about a problem in base with contained an
outdated /etc/init.d/network script. This is fixed now, although sysvinit
still creates this file on an upgrade (I've filed an important bug for
this).

> I have a system with an ethernet card which is not connected to anything.
> The installation routines (at the network setup step) force me into an
> ethernet/LAN oriented configuration.  I never get asked "Is your system
> connected to a network?"  (The dialog which comes up, asking about DHCP,
> says it's "automatic").

If there are network interfaces (e.g. because of loaded modules) netconf
assumes that you want to configure one of these interfaces. I will commit
a patch that allows you to enter an empty IP adress to skip configuration.

> I mentioned this in passing in an earlier bug report (57701), but implied
> the problem was a result of my having selected an ethernet driver.  I made
> no such selection this time, and get the same problem.

There must still be a network interface. If there are no network interfaces
besides lo netconf asks if you want to continue the network configuration
of first load some modules. If you say continue it creates a configuration
for just the loopback interface.

-- 
Stefan Gybas