Date: Thu, 09 Apr 2009 19:58:25 -0700 From: perryh@pluto.rain.com To: freebsd@edvax.de Cc: freebsd-questions@freebsd.org Subject: Re: USB SD-card reader recognized, but not working, on 6.1 Message-ID: <49deb5d1.syt1ug/OWLKGHOGd%perryh@pluto.rain.com> In-Reply-To: <20090410003759.dede9c9e.freebsd@edvax.de> References: <49de2c9a.QlCBOleCO/iBrMcf%perryh@pluto.rain.com> <20090409181009.GA38361@slackbox.xs4all.nl> <49de50cb.gcYrr9F1eSmdUBu9%perryh@pluto.rain.com> <20090410003759.dede9c9e.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Polytropon <freebsd@edvax.de> 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 :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49deb5d1.syt1ug/OWLKGHOGd%perryh>