Bug#224620: dhcp & lvm problems, partconf & GRUB wishlist
Am Sam, den 20.12.2003 schrieb Martin Michlmayr um 18:33:
> Package: installation-reports
> Why do you ask for the debconf priority at the beginning? I think it
> should just be "high" by default and people who want something lower can
> pass "DEBCONF_PRIORITY". I guess/hope this is currently only asked for
> testing, and that it will be disabled later. I chose "high".
I agree with you. This dialog was not written to be the second question
of the installer and should never be asked by default. Instead we should
try to provide good defaults so that almost any computer can be
installed with priority=high.
> Apparently, it looks for DHCP automatically. While the PC had a network
> card, it was not connected anywhere. So I got the following error:
> Configure the network using dynamic addressing (DHCP)
> An error occured and the network configuration process has been aborted.
> Since I didn't chose DHCP, it would be good if a short explanation could be
> offered. What DHCP is and why we tried to use it. Some people might not
> know what DHCP is.
> Since I didn't have or want a network, I wanted to choose "Detect and mount
> CD-ROM" next. However, that would show the DHCP error again. I could only
> continue after manually configuring an IP address. Please don't assume I
> want a network just because I have a network card. Also, why is the
> "manually configure network" so much further down the menu?
Some of the problems you describe are solved in CVS. The latest upload
of netcfg is currently stuck in the new queue. If you have the time
please test with netcfg from CVS (use the netcfg udeb instead of
netcfg-static and netcfg-dhcp)
The CVS version currently shows the following message when DHCP fails:
_Description: Do you want to retry DHCP network configuration?
No IP address was offered during DHCP network configuration. DHCP
servers are sometimes really slow. If you wish, you can retry.
Do you have any suggestions on how this could be improved?
I'm not completely sure why it tries to do DHCP all over again, but i
could imagine the following: After cdrom-detect the priority is bumped
to high again and main-menu automatically chooses dhcp again because it
is the default.
Increasing the debconf-priority should be done with a smarter algorithm
that checks if the failed step now succeeded and not simply increases
the priority after some (possibly unrelated) step succeeded.