From owner-freebsd-current@FreeBSD.ORG Mon Feb 9 12:34:26 2004 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 92F6316A4CE for ; Mon, 9 Feb 2004 12:34:26 -0800 (PST) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5546943D1F for ; Mon, 9 Feb 2004 12:34:26 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost.nic.fr [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id i19KYCDa081766 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK CN=khavrinen.lcs.mit.edu issuer=SSL+20Client+20CA); Mon, 9 Feb 2004 15:34:15 -0500 (EST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.9/8.12.9/Submit) id i19KYCP1081763; Mon, 9 Feb 2004 15:34:12 -0500 (EST) (envelope-from wollman) Date: Mon, 9 Feb 2004 15:34:12 -0500 (EST) From: Garrett Wollman Message-Id: <200402092034.i19KYCP1081763@khavrinen.lcs.mit.edu> To: "M. Warner Losh" In-Reply-To: <20040209.010318.89944026.imp@bsdimp.com> References: <6514.1076282830@critter.freebsd.dk> <20040209.010318.89944026.imp@bsdimp.com> X-Spam-Score: -19.8 () IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES X-Scanned-By: MIMEDefang 2.37 X-Mailman-Approved-At: Tue, 10 Feb 2004 05:09:06 -0800 cc: current@FreeBSD.ORG Subject: Re: Review/Test: Pseudo-device unit number management patch 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: Mon, 09 Feb 2004 20:34:26 -0000 < said: > s/I/we/ Others have signed off on this model. Maybe you could > explain how such a device would exist, and its exact semantics. With > a cloning device that phk is talking about, you open /dev/foo, and > /dev/foo0, /dev/foo1, etc are automatically created. This is how > things work on other systems for cloning devices. In traditional implementations of cloning devices, the master device actually exists in the namespace and can be seen and prodded without having to open it first. (E.g., /dev/pts) In really funky implementations of cloning devices, the master device magically morphs into a directory when you access it like one. (E.g., /dev/pts on AIX) -GAWollmna