From owner-freebsd-current Wed Dec 15 12:44:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 946CE15573 for ; Wed, 15 Dec 1999 12:44:51 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA77822; Wed, 15 Dec 1999 13:44:44 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA63531; Wed, 15 Dec 1999 13:44:44 -0700 (MST) Message-Id: <199912152044.NAA63531@harmony.village.org> To: Poul-Henning Kamp Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) Cc: current@FreeBSD.ORG In-reply-to: Your message of "Wed, 15 Dec 1999 19:25:26 +0100." <11260.945282326@critter.freebsd.dk> References: <11260.945282326@critter.freebsd.dk> Date: Wed, 15 Dec 1999 13:44:44 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <11260.945282326@critter.freebsd.dk> Poul-Henning Kamp writes: : A "devd" program would solve 98% of what devfs could solve. It cannot : solve the homebrew-a-vnode-for-the-root-fs problem. FreeBSD needs a : "devd" program *anyway* because what good is dynamic devices if you : can't do something intelligent with them when they appear (mount/ifconfig : etc etc etc). Yes. I'd like to see this in the future. There is no reason to have pccardd after the cut over to the new code. I don't think there is a reason to have both devd and usbd. They all just do things when devices come and go. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message