Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
Perhaps I'm missing something here, but doesn't this mean that the
default install with d-i is now "broken" by using both dhcp-client and
resolvconf? Doesn't this affect everyone using dhcp?
Clearly if the default install leads to a non-functioning network it
won't be getting rave reviews...
I must be confused...
On Tue, May 11, 2004 at 08:43:44AM -0700, Matt Zimmerman wrote:
> On Tue, May 11, 2004 at 05:23:06PM +0200, Thomas Hood wrote:
> > On Tue, 2004-05-11 at 17:10, Matt Zimmerman wrote:
> > > Because the debian-installer folks asked the dhcp*-client folks to leave
> > > things as they are for sarge.
> > So can & should debootstrap switch to installing dhcp3-client?
> I expect not, but ask debian-boot.
> In order for dhcp-client to be updated to v3, the various upgrade issues
> (dhcp-* v2 -> dhcp-* v3, dhcp3-* -> dhcp-* v3) need to be worked out, and I
> think it's a bit late in the game for that anyway. We asked about it some
> time ago and were told to leave it alone for d-i's sake.