From owner-freebsd-arch Sat Jan 9 12:54:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12578 for freebsd-arch-outgoing; Sat, 9 Jan 1999 12:54:07 -0800 (PST) (envelope-from owner-freebsd-arch@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12569 for ; Sat, 9 Jan 1999 12:54:01 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id VAA05275 for ; Sat, 9 Jan 1999 21:53:27 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id VAA24995 for freebsd-arch@freebsd.org; Sat, 9 Jan 1999 21:53:26 +0100 (MET) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA03276 for ; Tue, 5 Jan 1999 19:26:10 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zxjbE-0004dj-00; Tue, 5 Jan 1999 20:25:36 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id UAA19841 for ; Tue, 5 Jan 1999 20:23:37 -0700 (MST) Message-Id: <199901060323.UAA19841@harmony.village.org> Subject: Re: DEVFS, the time has come... To: freebsd-arch@FreeBSD.ORG In-reply-to: Your message of "Tue, 05 Jan 1999 19:42:02 +0100." <20686.915561722@critter.freebsd.dk> References: <20686.915561722@critter.freebsd.dk> Date: Tue, 05 Jan 1999 20:23:37 -0700 From: Warner Losh Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20686.915561722@critter.freebsd.dk> Poul-Henning Kamp writes: > Well, that might be a usable model for embedded environments, but > since you wouldn't offer PCCARD support, PnP support, or any of > the other dynamic technologies which need high-level intelligence > support, you wouldn't really be much better off than by using a > shell script, so I don't think what you describe will be a much > wanted solution... I don't think that matters at all. pccard support is provided by pccardd while pnp support is provided by controller pnp0 in your config file. I disgree that you'd need more intellegence than what I've proposed. It will easily handle all the dynamic stuff that I can think of, of devices coming and going, etc. I don't see what pnp, pccard, etc have to do with this. They are orthoginal to the problem. My devfsd dynamically deals with devices coming and going. I also disagree that it won't buy you much beyond the shell script. It buys you two things: 1) the ability to chmod /dev/ttyd1 imp and have that change persist w/o any further action. This is certainly POLA for thise case. 2) The ability to insert a modem card and have it have its old permissions and ownerships restored. When the new device arrives in the tree, the daemon will set its meta data properly. However, this does raise an interesting question, which is what is the scope of this daemon? Warner [Sorry for the delay in handling this bunch of messages - technical mail-filtering error in my end. -EE] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message