From owner-freebsd-stable@FreeBSD.ORG Sun Sep 3 23:57:39 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9FFC016A4DA for ; Sun, 3 Sep 2006 23:57:39 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 611EE43D46 for ; Sun, 3 Sep 2006 23:57:39 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id HGI05339; Sun, 03 Sep 2006 16:57:39 -0700 Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id AF0E64504D; Sun, 3 Sep 2006 16:57:38 -0700 (PDT) X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Michael Abbott In-Reply-To: Your message of "Sun, 03 Sep 2006 20:28:14 -0000." <20060903202404.W40698@saturn.araneidae.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1157327858_58588P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Sun, 03 Sep 2006 16:57:38 -0700 From: "Kevin Oberman" Message-Id: <20060903235738.AF0E64504D@ptavv.es.net> Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD bemused by USB card reader X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Sep 2006 23:57:39 -0000 --==_Exmh_1157327858_58588P Content-Type: text/plain; charset=us-ascii > > On Sun, 3 Sep 2006, Kevin Oberman wrote: > >> From: Michael Abbott > >> # ls /dev/da* > >> /dev/da0 /dev/da1 /dev/da1 /dev/da2 /dev/da2 /dev/da3 /dev/da3 > >> How very very strange. > > Strange, yes. Surprising, no. > > > > umass (and USB support) is not in the best of shape in FreeBSD. > > Does this phenomenon also point to a problem with devfs, or is the set of > device names completely delegated to the corresponding driver (umass) by > devfs? Almost certainly. The creation of devfs entries is done by the driver (or at least the calls to the devfs to do so) are in the driver. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1157327858_58588P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFE+2vykn3rs5h7N1ERAmxoAJ9JbAHpqa8MhfbrXLX/Z5wt+JMxogCbBPf/ AgpquCx8DMv4QHlpDR6YRcc= =Epde -----END PGP SIGNATURE----- --==_Exmh_1157327858_58588P--