On Thu, May 13, 2004 at 07:11:26PM -0700, Joshua Kwan wrote:
> (I also note that the binary is GIGANTIC compared to dhcp-client-udeb's!
> Can anything be done about that?)
And it grows horrible if built against a shared uclibc. At least I don't
think that mipsel binaries are 3 times as large than
On Tue, 11 May 2004 08:43:44 -0700, Matt Zimmerman wrote:
> 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
Update for debian-boot... This bug will be fixed by adding resolvconf
support to dhcp-client. A patch has been prepared and fixed the
problem for the submitter of #248399.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PRO
Processing commands for [EMAIL PROTECTED]:
> clone 248399 -1
Bug#248399: dhcp-client installed instead of dhcp3-client
Bug 248399 cloned as bug 248578.
> reassign -1 debootstrap
Bug#248578: dhcp-client installed instead of dhcp3-client
Bug reassigned from package `debian-installer' to `debootstra
> I just installed dhcpcd 1:1.3.22pl4-10 and dpkg -s reports:
>
> Conflicts: dhcpcd-sv, dhcp-client
>
> so I don't see how you could have both dhcpcd and dhcp-client
> (or any other DHCP client that Provides dhcp-client) installed.
You're right, dhcpcd is not installed. I have dhcp-client 2
Hi Thomas,
On Tue, May 11, 2004 at 03:48:03PM +0200, Thomas Hood wrote:
> I wondered why dhcp-client is still being installed, rather than
> dhcp3-client.
>
> On Tue, 2004-05-11 at 13:48, Anthony Towns wrote:
> > That's easy: dhcp3-client didn't used to exist.
>
> So the question is: Why is debo
On Tue, 2004-05-11 at 20:43, Scott Webster wrote:
> I likely selected the Broadband task in tasksel. I may have dhcpcd
> installed. I can't check now unfortunately, as the box is at home,
> and apparently the dynamic IP has changed. If I remember correctly,
> it is installed, and presumably it w
On Tue, May 11, 2004 at 09:34:45AM -0700, Scott Webster wrote:
> 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?
Maybe.
> Doesn't this affect everyone using dhcp?
No? It certainly works fi
On Tue, May 11, 2004 at 08:07:00PM +0200, Thomas Hood wrote:
> Is resolvconf installed by default? If so then it's news to me.
> (I knew that resolvconf was installed as part of the Broadband
> and Dialup tasks; however Broadband includes dhcpcd and that does
> work with resolvconf.)
I likely se
On Tue, 2004-05-11 at 18:34, Scott Webster wrote:
> 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?
Is resolvconf installed by default? If so then it
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
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 ex
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?
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subj
On Tue, May 11, 2004 at 09:48:35PM +1000, Anthony Towns wrote:
> On Tue, May 11, 2004 at 11:46:48AM +0100, Colin Watson wrote:
> > > I don't know why the installer is installing dhcp-client rather than
> > > dhcp3-client. I'll reassign this to debian-installer.
>
> That's easy: dhcp3-client di
I wondered why dhcp-client is still being installed, rather than
dhcp3-client.
On Tue, 2004-05-11 at 13:48, Anthony Towns wrote:
> That's easy: dhcp3-client didn't used to exist.
So the question is: Why is debootstrap _still_ installing dhcp-client?
> (If dhcp3-client is to replace dhcp-client,
On Tue, May 11, 2004 at 11:46:48AM +0100, Colin Watson wrote:
> > I don't know why the installer is installing dhcp-client rather than
> > dhcp3-client. I'll reassign this to debian-installer.
That's easy: dhcp3-client didn't used to exist.
(If dhcp3-client is to replace dhcp-client, why isn't
reassign 248399 debootstrap
thanks
On Tue, May 11, 2004 at 11:43:28AM +0200, Thomas Hood wrote:
> reassign 248399 debian-installer
> retitle 248399 dhcp-client installed instead of dhcp3-client
> thanks
>
> On Tue, 2004-05-11 at 00:41, Scott Webster wrote:
> > I do not have dhcp3-client installed
reassign 248399 debian-installer
retitle 248399 dhcp-client installed instead of dhcp3-client
thanks
On Tue, 2004-05-11 at 00:41, Scott Webster wrote:
> I do not have dhcp3-client installed, only dhcp-client.
That's the problem. Resolvconf doesn't support dhcp-client -- only
dhcp3-client. Pleas
Processing commands for [EMAIL PROTECTED]:
> reassign 248399 debian-installer
Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
Bug reassigned from package `resolvconf' to `debian-installer'.
> retitle 248399 dhcp-client installed instead of
19 matches
Mail list logo
