From owner-freebsd-current@FreeBSD.ORG Sun Jun 28 04:21:28 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 9032B106564A for ; Sun, 28 Jun 2009 04:21:28 +0000 (UTC) (envelope-from louie@transsys.com) Received: from ringworld.transsys.com (ringworld.transsys.com [144.202.0.15]) by mx1.freebsd.org (Postfix) with ESMTP id 666908FC26 for ; Sun, 28 Jun 2009 04:21:28 +0000 (UTC) (envelope-from louie@transsys.com) Received: from PM-G5.transsys.com (c-69-141-150-106.hsd1.nj.comcast.net [69.141.150.106]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: louie) by ringworld.transsys.com (Postfix) with ESMTP id 954CF5C04 for ; Sat, 27 Jun 2009 23:56:57 -0400 (EDT) Message-Id: <4DF26D1E-B437-4FB3-B210-50ACB727101A@transsys.com> From: Louis Mamakos To: freebsd-current@freebsd.org In-Reply-To: <200906280847.59316.doconnor@gsoft.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v935.3) Date: Sat, 27 Jun 2009 23:56:56 -0400 References: <4A4517BE.9040504@FreeBSD.org> <20090627141412.GN31709@acme.spoerlein.net> <4A462A7A.20005@haruhiism.net> <200906280847.59316.doconnor@gsoft.com.au> X-Mailer: Apple Mail (2.935.3) 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: Sun, 28 Jun 2009 04:21:28 -0000 On Jun 27, 2009, at 7:17 PM, Daniel O'Connor wrote: > On Sat, 27 Jun 2009, Kamigishi Rei wrote: >> Hello, hope you're having a nice day, >> >> Ulrich Sp=F6rlein 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). > > 7.2 has UFSID in GENERIC so you can mount your disks that way which is > non-ambiguous. > > Unfortunately you can't specify swap this way because it has no ID, I > don't know how hard it would be to add such a thing (which would > require a mkswap or somesuch, and modification to the dump & swap > code..) > I use glabel to create containers with named labels that I then reference as swap devices. (e.g., /dev/label/swap0, etc.) # swapinfo Device 1024-blocks Used Avail Capacity /dev/label/swap2 1044192 0 1044192 0% /dev/label/swap3 1044192 0 1044192 0% /dev/label/swap4 1044192 0 1044192 0% Total 3132576 0 3132576 0% louie