From: "Bryan O'Sullivan" <bos@keyresearch.com>
To: David T Hollis <dhollis@davehollis.com>
Cc: Aaron Lehmann <aaronl@vitelus.com>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [ANNOUNCE] netplug, a daemon that handles network cables getting plugged in and out
Date: 29 Aug 2003 10:43:13 -0700 [thread overview]
Message-ID: <1062178992.12285.130.camel@serpentine.internal.keyresearch.com> (raw)
In-Reply-To: <3F4EB641.3040107@davehollis.com>
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 parent reply other threads:[~2003-08-29 17:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 21:21 [ANNOUNCE] netplug, a daemon that handles network cables getting plugged in and out Bryan O'Sullivan
2003-08-28 21:35 ` Jeff Garzik
2003-08-28 21:46 ` Christoph Hellwig
2003-08-28 21:50 ` Bryan O'Sullivan
2003-08-28 21:54 ` J.A. Magallon
2003-08-28 22:34 ` Jeff Garzik
2003-08-28 22:45 ` J.A. Magallon
2003-08-28 22:49 ` Bryan O'Sullivan
2003-09-03 8:42 ` Stefan Rompf
2003-08-29 0:34 ` Aaron Lehmann
2003-08-29 2:11 ` David T Hollis
2003-08-29 17:43 ` Bryan O'Sullivan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1062178992.12285.130.camel@serpentine.internal.keyresearch.com \
--to=bos@keyresearch.com \
--cc=aaronl@vitelus.com \
--cc=dhollis@davehollis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).