Chris Abbey wrote:
>
> At 15:05 11/8/99 -0800, H. Peter Anvin wrote:
> >This is true, and that's a valid request. Service information exported
> >via DHCP needs to get around.
> >
> >However, something we should think about would be if there is a better
> >way to do this than having pump edit N different random files in the
> >system (and usually getting them wrong, at least one of my machines
> >always gets its /etc/resolv.conf file trashed by pump -- then there are
> >things like interactions with nscd etc.)
>
> why is pump editing anything? why not have it spew all the info it gets
> into a file in name=value pairs and let the programms pull out what they
> want??
>
> I'll admit I don't use pump, but this scheme seems to work fine with
> the set of scripts I have for changing between three different network
> configurations.
>
The problem is that for DHCP, the configuration can change *at any
time*. Unlike BOOTP, where you get a configuration at one point and
that's it, with DHCP you need to be able to change at runtime.
-hpa
--
<[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
--
To unsubscribe:
mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
