On 8/21/2012 6:34 AM, John Baldwin wrote:
> Humm. devd is the more common case, and we explicitly don't use devd to
> start
> dhclient on boot even when devd is enabled (so out of the box dhcp would
> first
> be started by rc, but would be restarted by devd).
That sounds reasonable. People who choose not to run devd can be
responsible for restarting dhclient themselves.
> Another option is to rework dhclient to work like it does on OpenBSD where it
> renews its lease if the link bounces, but to not exit when the link goes down.
That would be preferable.
> That case would fix the currently broken case that you unplug your cable,
> take
> your laptop over to another network (e.g. take it home if suspend/resume
> works), then plug it back in and are still stuck with your old IP.
I do think it's important to fix this case. However I agree with the
chorus of responders that it is more important to maintain our historic
resilience to temporary loss of connectivity.
Doug
--
I am only one, but I am one. I cannot do everything, but I can do
something. And I will not let what I cannot do interfere with what
I can do.
-- Edward Everett Hale, (1822 - 1909)
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
