Bug 4295

Summary: pump broke backwards compatibility with dhcpcd
Product: [Retired] Red Hat Linux Reporter: amarkel
Component: pumpAssignee: Erik Troan <ewt>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0CC: amarkel
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-02-03 16:52:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description amarkel 1999-07-31 23:27:51 UTC
As you have decided to replace dhcpcd with pump, you
have broken backwards compatibility with 5.2.

I, and probably other users, had configured ifdhcpcd-up
to perform specific activity.

It also broke the /etc/dhcp/hostinfo-{ifc} mechanism
according to which the file could be 'source-d' and
the variables used.

(Yes, I know that it is possible to accomplish the same
with 'pump', by querying pump and populating the
file with the values returned:

pump -i $IFC --status > $STATFILE

IPADDR=`grep IP: $STATFILE | sed -e 's/ IP: //'`
NETMASK=`grep Netmask: $STATFILE | sed -e 's/   Netmask:
BROADCAST=`grep Broadcast: $STATFILE | sed -e 's/
Broadcast: //'`
ROUTER=`grep Gateway: $STATFILE | sed -e 's/    Gateway:
NAMESERVERS=`grep Nameservers: $STATFILE | sed -e 's/
Nameservers: //'`


The replacement for dhcpcd - pump - broke the backwards

Furthermore, as mentioned in a previous bug I submitted,
pump (I upgraded following the errata), core dumps on
a compiled 2.2.10 kernel.


Forgive me for venting, but it appears to me that having
replaced 'pump' with a non-compatible replacement is
a cardinal sin in delivering software.

No matter how smart the replacement program may be, the
impact on the users should be evaluated first and foremost.

You screwed up.

Arieh Markel