From owner-freebsd-current@FreeBSD.ORG Sat Jun 27 14:42:59 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41CA31065697; Sat, 27 Jun 2009 14:42:59 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id E8B498FC0A; Sat, 27 Jun 2009 14:42:58 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.local (pooker.samsco.org [168.103.85.57]) by pooker.samsco.org (8.14.2/8.14.2) with ESMTP id n5REgtk3035284; Sat, 27 Jun 2009 08:42:55 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4A462FEF.3040601@samsco.org> Date: Sat, 27 Jun 2009 08:42:55 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Kamigishi Rei References: <4A4517BE.9040504@FreeBSD.org> <20090627141412.GN31709@acme.spoerlein.net> <4A462A7A.20005@haruhiism.net> In-Reply-To: <4A462A7A.20005@haruhiism.net> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.5 required=3.8 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: Alexander Motin , FreeBSD-Current Subject: Re: RFC: ATA to CAM integration patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jun 2009 14:42:59 -0000 Kamigishi Rei wrote: > Hello, hope you're having a nice day, > > Ulrich Spörlein wrote: >> I, personally, think this is not very good idea. People are used to >> CAM-devices getting enumerated as da0, da1, etc. All the documentation >> talks about ad0 for ATA and da0 (plus camcontrol) for SCSI, USB, >> Firewire devices. We also have fd0 and cd0 and should stick to >> two-letter-plus-number codes. So either make them all ad0 or da0. I'd >> vote for the latter, as that is what Linux is doing (more or less) and >> people are already familiar with USB drives or new SATA drives showing >> up as "SCSI drives, so they get the SCSI names". >> > This poses the question of daXX enumeration order. I've already had some > 'fun' with an IBM server which has an LVD/320 SCSI controller. While the > controller's bus was enumerated properly, somehow if you attach an USB > mass storage device before the system boot that said mass storage could > suddenly appear earlier than one of the SCSI disks (that was on > 7.0-RELEASE) thus breaking the boot process sometimes (when it appeared > as da0). > CAM allows you to statically set the enumeration order via hints in either the kernel config file or in /boot/loader.conf. /sys/conf/NOTES contains information and examples of this. Scott