Bug 4327 - Why pump is not operated in RedHat6.0?
Summary: Why pump is not operated in RedHat6.0?
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: pump
Version: 6.0
Hardware: alpha
OS: Linux
Target Milestone: ---
Assignee: Erik Troan
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-08-03 05:12 UTC by nukejun
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2000-02-15 21:40:28 UTC

Attachments (Terms of Use)

Description nukejun 1999-08-03 05:12:10 UTC
Hi, my name is Jun working for Samsung Advanced Institute of Technology.
I am using the kernel 2.2.5 including bootp request option on
Alpha 533Mhz 21164a, 164LX system.
As the kernel proceeds in booting, it receives the IP address
and hostname automatically from one server.
However, one error occurrs in "ifup" script program.
In "ifup", "pump -i eth0" is called.
Error message is "Operation failed"
so, networking is impossible.
I have experimented executing "pump" in RedHat 5.2.
There was not any problem.
Only in RedHat 6.0, "pump" was not operated.
   In RedHat6.0
   In Redhat5.2
I can guess the reason...maybe glibc problem...

Possible faults
1. glibc bug
2. pump bug
3. my mistake in kernel compiling with bootp option.
4. my mistake in network configuration files...(very low possibily)

Please, help me....~_~

Comment 1 Jay Turner 1999-08-03 15:10:59 UTC
We are aware of problems with pump on the alpha architecture and are
working to release an update which will resolve these problems.  In
the mean time, you can always make use of dhcpcd from the 6.0 package,
as it should work as before.

Comment 2 Mads Kiilerich 1999-08-13 10:50:59 UTC
I experienced similar problems after having upgraded a celeron to
kernel 2.2.11.

Perhaps I didn't include the right options, idunno...

Regards, Kiilerich

Comment 3 Erik Troan 2000-02-15 21:40:59 UTC
If these problems have persisted, please reopen this bug.

Note You need to log in before you can comment on or make changes to this bug.