From owner-freebsd-current@FreeBSD.ORG Sat Sep 13 15:49:31 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D18A16A4BF; Sat, 13 Sep 2003 15:49:31 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE8D543F3F; Sat, 13 Sep 2003 15:49:29 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.9/8.12.3) with ESMTP id h8DMnRTX057362; Sat, 13 Sep 2003 16:49:28 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 13 Sep 2003 16:49:27 -0600 (MDT) Message-Id: <20030913.164927.81895915.imp@bsdimp.com> To: DougB@freebsd.org From: "M. Warner Losh" In-Reply-To: <20030913144105.K85817@12-234-22-23.pyvrag.nggov.pbz> References: <20030913142107.V85817@12-234-22-23.pyvrag.nggov.pbz> <20030913.153658.43409469.imp@bsdimp.com> <20030913144105.K85817@12-234-22-23.pyvrag.nggov.pbz> X-Mailer: Mew version 2.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: refugee@vt.edu cc: freebsd-current@freebsd.org Subject: Re: devd/devctl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Sep 2003 22:49:31 -0000 In message: <20030913144105.K85817@12-234-22-23.pyvrag.nggov.pbz> Doug Barton writes: : On Sat, 13 Sep 2003, M. Warner Losh wrote: : : > In message: <20030913142107.V85817@12-234-22-23.pyvrag.nggov.pbz> : > Doug Barton writes: : > : That functionality is being ported back to the vendor, if it hasn't been : > : already. If we want really cool whizbang features that are more specific : > : to us, we _should_ be looking at stuff like devd. The trick is definig : > : which problem space we're addressing at any given moment. :) : > : > You can't do it in devd. You must be able to either (a) tell a : > running dhclient about arrival/departures of interfaces : : Ok, maybe I misunderstand, but wouldn't _this_ be the right thing for : devd to do? In other words, devd should be able to notice this, and : devd.conf should be able to define what I want to do with this like : sending a signal to dhclient. Then we can move to the dhclient problem : space, and define behavior in dhclient that says "when X happens, I need : to do Y." You misundestand. devd *CANNOT* do this. I have a laptop that has a builtin rl0 interface. I plug in a wi0 interface. somehow we gotta deal. and you cannot tell dhclient that interfaces have arrived. : > or (b) run multiple dhclients. : : This is evil, and basically undoable with the current state of things, : but it might be possible down the road, although I still think it's evil : for other reasons. why is this evil? dhclient can and does run on mulitple interfaces. it fails now because it specifically precludes it, but for no other good reasons. Warner