Bug 2035
Summary: | BOOTP doesn't work | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | rebel |
Component: | installer | Assignee: | Erik Troan <ewt> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1999-06-01 19:29:59 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
rebel
1999-04-07 15:54:56 UTC
erik, I figure this has been fixed, correct? what's the output of "rpm -q pump" The latest pump (0.5) is functinal. Only when the BOOTP protocol is used it doesn't need to stay running forever. pump shouldn't fork for bootp replies, right? but I guess it's hard to handle that case. I think it should be enough if pump could have a parameter (--nodaemon) to stop after the first init. Also is there any way to add another data to resolv.conf, such as additional searches, automatically? pump intentionally hides the differences between bootp and dhcp; as part of this it always goes into daemon mode. This doesn't hurt anything, and makes things a bit easier on our scripts. I would welcome a patch for a --nodaemon option. More flexible /etc/resolv.conf generation is on the todo list. |