dhcpcd-discuss

On Mon, 2010-12-06 at 14:11 +0100, EXTERNAL Konold Martin (Firma,
RtP2/TEF72) wrote:
> BTW: Was it too hard to keep backwards compatiblility?

Hard? No. However I am rapidly running out of command line options and
when I introduced an alternative mechanism to configuring these options,
I saw that I could remove some options for future re-use.

>  After all there is like with "-n" not always a 100% replacement possible.

The operation of -n was changed because people where using it alongside
ifplugd/wpa_supplicant when the cable/wireless network changed. The
problem here is that dhcpcd was attempting to then renew and spend a
long time timing out due to non authorative DHCP servers correctly being
silent. The solution was to make dhcpcd rebind instead of renew. Of
course, a renew vs a rebind is completely identical to the user if it
succeeds (and a faster response if it fals) so the change makes sense.

> > dhcpcd-3 and earlier the idea being that distros could then change to
> > the new world. dhcpcd-5 removed this layer. If SuSE had kept
> > up to date,
> > then it would be likey dhcpcd-5 would have just dropped in.
> 
> I am telling the OpenSUSE people: https://bugzilla.novell.com/show_bug.cgi?id=657402

I only recently got dhcpcd updated in Debian to dhcpcd-5 from dhcpcd-3.
That involves a new package the worked alongside dhcpcd-3 because
dhcpcd-5 now works as a single process on all interfaces. It can still
work per interface but not 100% the same way with dhcpcd-3. SuSE may
wish to go the same way.

Thanks

Roy