On 17/06/2010 10:17, Roy Marples wrote:
The only valid reason for co-existence so far is that some flags have
been removed from the commandline that could be used by other
people/programs. dhcpcd-4 shipped with some compat code to handle the
transition from dhcpcd-123 to dhcpcd-4, to give both developers and
users time to migrate. Debian doesn't have this luxury as it skipped
dhcpcd-4 entirely! However, a patch can be maintained to add these
compat flags back again. I could not find the source to ifup my Ubuntu
to find out what flags it passes to dhcpcd - can you tell me please?
After careful perusal of the interfaces man page (still can't find the
source for ifup to ensure I'm correct), the only options passed to
dhcpcd are -h $hostname -i $vendor -I $client -l $leasetime
These options still exist and are valid.
With the removal (or just non usage) of /etc/defaults/dhcpcd any
existing user options are just ignored and the user is expected to put
any configuration into /etc/dhcpcd.conf.
I've also solved the init script vs network/interfaces issue by grepping
for iface * inet dhcp and aborting if such a match is found.
As such, I cannot justify a reason for having to maintain co-existance
with older dhcpcd versions. The only question remainig that I can see is
do we want to attempt to parse /etc/defaults/dhcpcd into
/etc/dhcpcd.conf on upgrade? That would requre bash to be installed and
I'm not sure that it's worth the time spent.
Thanks
Roy
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
