| To: | David T Hollis <dhollis@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [ANNOUNCE] netplug, a daemon that handles network cables getting plugged in and out |
| From: | "Bryan O'Sullivan" <bos@xxxxxxxxxxxxxxx> |
| Date: | 29 Aug 2003 10:43:13 -0700 |
| Cc: | Aaron Lehmann <aaronl@xxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <3F4EB641.3040107@davehollis.com> |
| References: | <1062105712.12285.78.camel@serpentine.internal.keyresearch.com> <20030829003426.GF12249@vitelus.com> <3F4EB641.3040107@davehollis.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Thu, 2003-08-28 at 19:11, David T Hollis wrote:
> Hmm, that seems to raise the question - why doesn't dhclient just handle
> that?
Because it has as little knowledge of how the OS works as possible.
It's intended to run on all kinds of Unix platforms, not just Linux.
> On a DHCP interface, it's running anyway. if it paid attention
> to link status, it would know when to re-request an IP.
There are no cross-platform standards for this kind of thing, so they'd
need modules for Linux, FreeBSD, Solaris, AIX, etc., etc. I'm sure
they'd be happy to accept patches.
<b
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | forcing bottom half to a specific processor on numa, chas williams |
|---|---|
| Next by Date: | [PATCH] (2/3) llc - need to set owner on created sockets., Stephen Hemminger |
| Previous by Thread: | Re: [ANNOUNCE] netplug, a daemon that handles network cables getting plugged in and out, David T Hollis |
| Next by Thread: | Please help, Two simple questions regarding Linux TCP codes, John Zeng |
| Indexes: | [Date] [Thread] [Top] [All Lists] |