From owner-freebsd-current@FreeBSD.ORG  Sun Feb  8 00:12:10 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 C3B4D16A4CE
	for <current@freebsd.org>; Sun,  8 Feb 2004 00:12:10 -0800 (PST)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 184AE43D1D
	for <current@freebsd.org>; Sun,  8 Feb 2004 00:12:10 -0800 (PST)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id i188Bxbj016066;
	Sun, 8 Feb 2004 09:12:00 +0100 (CET)
	(envelope-from phk@phk.freebsd.dk)
To: Julian Elischer <julian@elischer.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Sat, 07 Feb 2004 23:58:47 PST."
             <Pine.BSF.4.21.0402072348240.24800-100000@InterJet.elischer.org> 
Date: Sun, 08 Feb 2004 09:11:59 +0100
Message-ID: <16065.1076227919@critter.freebsd.dk>
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Feb 2004 08:12:10 -0000

In message <Pine.BSF.4.21.0402072348240.24800-100000@InterJet.elischer.org>, Ju
lian Elischer writes:

>> I would appreciate if people would test these devices work _as
>> previously_ with this patch in place.
>
>well that depends on your definition of "as previously"
>
>Previously, nmdm started off with 4 devices visible in /dev now I don't
>see that.. The old behaviour was intuitive... You saw a device.

This new behaviour is called a "cloning device" and it doesn't allocate
any resources until they are actually needed, which I belive is the
correct behaviour for pseudo-devices.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.