From owner-freebsd-questions Thu Jan 9 7:43: 9 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 49B1237B401 for ; Thu, 9 Jan 2003 07:43:07 -0800 (PST) Received: from mired.org (dsl-64-192-6-133.telocity.com [64.192.6.133]) by mx1.FreeBSD.org (Postfix) with SMTP id E50B343F6D for ; Thu, 9 Jan 2003 07:43:00 -0800 (PST) (envelope-from mwm-dated-1042558970.649101@mired.org) Received: (qmail 32699 invoked from network); 9 Jan 2003 15:42:50 -0000 Received: from localhost.mired.org (HELO guru.mired.org) (127.0.0.1) by localhost.mired.org with SMTP; 9 Jan 2003 15:42:50 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15901.39034.215782.907972@guru.mired.org> Date: Thu, 9 Jan 2003 09:42:50 -0600 To: Stijn Hoop Cc: freebsd-questions@freebsd.org Subject: device probe order (Was: attaching a umass device?) In-Reply-To: <20030109153701.GF938@pcwin002.win.tue.nl> References: <20030109021324.GU32176@thingy.apana.org.au> <20030109051549.GA480@lulu.bad.dog> <15901.36243.349994.838981@guru.mired.org> <20030109153701.GF938@pcwin002.win.tue.nl> X-Mailer: VM 7.07 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ From: Mike Meyer X-Delivery-Agent: TMDA/0.68 (Shut Out) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In <20030109153701.GF938@pcwin002.win.tue.nl>, Stijn Hoop typed: > On Thu, Jan 09, 2003 at 08:56:19AM -0600, Mike Meyer wrote: > > In <20030109051549.GA480@lulu.bad.dog>, Robin Damm typed: > > > On Thu, Jan 09, 2003 at 01:13:24PM +1100, David Gerard wrote: > > > > This is probably really simple, but I couldn't see it in the handbook ... > > > > I've plugged a umass device (a camera) into a USB port. What do I do now to > > > > get access to the data? > > > I have no usb toys myself, but I gather it should be as easy as > > > "mount -t msdos /dev/$foo /mnt/$bar". Then access the camera as a > > > regular filesystem. Grep dmesg or syslog for "umass" to find out the > > > device name. > > It's probably da0s1. Even if you have real SCSI devices, it tends to > > be da0 until you tweak the kernel to reorder them so you can boot :-(. > I'm 'lucky' I only use my CF reader with ATA devices then... My long term > goal was to use SCSI disks in my home desktop, so thanks for the headsup > when I'm able to do that... > > I think this bug should be fixed, but I'm guessing it will be kind of hard > to devise a 'device probe order', or is this already in the kernel? You can work around this by hardwiring the device names in. I.e., I have: device ahc0 # AHA2940 and onboard AIC7xxx devices device scbus0 at ahc0 # SCSI bus (required) as the umass device defaults to scbus0, meaning the things on it get lower numbers than the things on the ahc. I didn't treat this as a bug, just an unpleasantness. It would be nice if it changed, but I'm not going to initiate it happening. The correct place to talk about this would be scsi@freebsd.org. If you bring it up there, please include me on the to: line. http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message