[plug] persuading pump --status to print reserved/custom options?

[Craig Ringer]

> Um what about dhclient instead of pump?  Might save you some coding time.

I had a quick look and while it does appear to understand all the DHCP 
options it doesn't seem to be able to output them usefully. I expect 
it'd be easier to modify pump quickly to print:

	Option 128: <value>
	Option 210: <value>

etc on the end of a --status call rather than adding reporting 
capabilities to dhclient. I have stuff-all C coding experience, so 
extending existing code is _much_ more managable (read: possible) for me 
than adding new features/capabilities.

Unfortunately pump doesn't even seem to keep track of options it doesn't 
understand internally at the moment, so this might not be as quick as I 
was hoping. Oh well, I've been putting off learning C for ages...

-- 
Craig Ringer
GPG Key Fingerprint: AF1C ABFE 7E64 E9C8 FC27  C16E D3CE CDC0 0E93 380D
	-- if it ain't broke, add features 'till it is. (or:)
	while (! broken) { features ++ ; broken = isBroken(features) }