Package: dhcpcd
Severity: normal
I agree. There is no reason to me why dhcpcd should conflict with dhcp3-client.
I have been using my system with both of them installed at the same time for
ages and did not notice the slightest conflict or issue.
This is why I have both of them. AFAIK, dhcpcd does not support scripts
hooking, which makes dhcp3-client a better choice as a default DHCP client.
And it happens to be the default choice when both are installed. On the other
hand, dhclient does not support features that happen to be useful to me. Such
as restricting options like not updating default gateway (-G) or resolv.conf
(-R), or test option (-T) which are particularly useful when you cant to
connect to multiple networks at the same time, all requiring DHCP for
configuration.
I think a conflict would be justified of one of the two packages was
providing all the features the other does, but that is not the case. That
is why I would suggest to remove that conflict too.
Best regards.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.31.6 (SMP w/2 CPU cores; PREEMPT)
Locale: lang=fr...@euro, lc_ctype=fr...@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash
Versions of packages dhcpcd depends on:
ii bsdutils 1:2.16.2-0 Basic utilities from 4.4BSD-Lite
ii libc6 2.10.2-3 Embedded GNU C Library: Shared lib
ii procps1:3.2.8-2 /proc file system utilities
dhcpcd recommends no packages.
dhcpcd suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
