From owner-freebsd-questions@FreeBSD.ORG Fri Apr 10 03:13:18 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 48A10106564A for ; Fri, 10 Apr 2009 03:13:18 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [199.26.172.34]) by mx1.freebsd.org (Postfix) with ESMTP id 224D88FC14 for ; Fri, 10 Apr 2009 03:13:18 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id n3A3DDOi030624 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 9 Apr 2009 20:13:14 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id n3A3DDgF030623; Thu, 9 Apr 2009 20:13:13 -0700 (PDT) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA01877; Thu, 9 Apr 09 20:00:19 PDT Date: Thu, 09 Apr 2009 19:58:25 -0700 From: perryh@pluto.rain.com To: freebsd@edvax.de Message-Id: <49deb5d1.syt1ug/OWLKGHOGd%perryh@pluto.rain.com> References: <49de2c9a.QlCBOleCO/iBrMcf%perryh@pluto.rain.com> <20090409181009.GA38361@slackbox.xs4all.nl> <49de50cb.gcYrr9F1eSmdUBu9%perryh@pluto.rain.com> <20090410003759.dede9c9e.freebsd@edvax.de> In-Reply-To: <20090410003759.dede9c9e.freebsd@edvax.de> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: USB SD-card reader recognized, but not working, on 6.1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Apr 2009 03:13:18 -0000 Polytropon wrote: > On Thu, 09 Apr 2009 12:47:23 -0700, perryh@pluto.rain.com wrote: > > It's an SD card, not a "drive", so I had not expected it to be > > partitioned; but yes, it is: > > > > $ ls -l /dev/da0* > > crw-r----- 1 root operator 0, 244 Feb 14 15:09 /dev/da0 > > crw-r----- 1 root operator 0, 245 Feb 14 15:09 /dev/da0s1 > > Why don't you expect this? As far as I know, if something is > msdosfs-formatted (read: any "Windows" readable file system, > FAT), it always involves a "slice device". I never found a > situation where access to /dev/da0 would work. My experience is exactly the reverse. I've never before seen a removable-media device (floppy, Zip-drive, JAZ drive) that *did* have a DOS "partition" table aka BSD "slice" table. Surely you would not expect a USB floppy to show up as /dev/da0s1? AFAIK the reason for creating slices is to identify sections of the device for use by different OS -- something often needed for multi-boot from a hard drive but seldom on removable media. I sure wasn't planning to use part of this SD card for my camera to store pictures on, and the rest for FreeBSD backups :)