The DHCPACK or BOOTP packet received by pump may contain information about
network services, such as timeservers (usable by xntpd) and outgoing mail
servers. It doesn't, however, make this information available to
applications, even though it contains a script-invoking function.
In these days of secure mail servers, it's a big deal for portable users to
be able to use the SMTP server directed by the ISP this way. Similarly,
again for portable users, it's a big win to be able to integrate other
services with DHCP this way.
I suggest saving the DHCP packet in a file (say, /var/run/pump.eth0.pkt)
and let client programs parse the DHCP client options themselves; this is a
lot more generic than trying to parse them inside pump.
Perhaps an even better option would be to have loadable modules (.so files)
invokable by pump. If so, they can pass the packet data in memory.
Created attachment 13284 [details]
Patch to correct nisdomain setting and to include some dhcp info in script environment
Hmm, dhcpcd replaces pump in rawhide - can you look into reinterpreting the
concept in light of that?
I haven't played with dhcpcd, so I can't comment; I have mentioned to a few
RedHat people that you may want to consider using dhclient, which is part of the
reference DHCP distribution, and can be customized to obtain all kinds of