From owner-freebsd-questions@FreeBSD.ORG Sun Mar 5 21:31:42 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 6375416A420 for ; Sun, 5 Mar 2006 21:31:42 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF03B43D48 for ; Sun, 5 Mar 2006 21:31:41 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id D23E91A4DF0; Sun, 5 Mar 2006 13:31:41 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 262F2544CC; Sun, 5 Mar 2006 16:31:38 -0500 (EST) Date: Sun, 5 Mar 2006 16:31:37 -0500 From: Kris Kennaway To: Duane Whitty Message-ID: <20060305213137.GA4276@xor.obsecurity.org> References: <200603041726.37525.duane@greenmeadow.ca> <20060304213050.GA57225@xor.obsecurity.org> <200603051712.36483.duane@greenmeadow.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ikeVEW9yuYc//A+q" Content-Disposition: inline In-Reply-To: <200603051712.36483.duane@greenmeadow.ca> User-Agent: Mutt/1.4.2.1i Cc: freebsd-questions@freebsd.org, Kris Kennaway Subject: Re: device atapicam not enabled in GENERIC kernel for FreeBSD 6.0-RELEASE 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: Sun, 05 Mar 2006 21:31:42 -0000 --ikeVEW9yuYc//A+q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Mar 05, 2006 at 05:12:36PM -0400, Duane Whitty wrote: > On Saturday 04 March 2006 17:30, Kris=20 > Kennaway wrote: > > On Sat, Mar 04, 2006 at 05:26:37PM=20 > -0400, Duane Whitty wrote: > > > Hi, > > > > > > Just wondering if anyone has any > > > information/opinion as to why > > > device atapicam is not enabled by > > > default in the GENERIC kernel. > > > > It's not an appropriate default, > > since it modifies the way the ata > > subsystem works in ways the > > maintainer does not wish to support, >=20 > Sorry, but do you mean the ata subsystem=20 > maintainer or the atapicam maintainer? The former. > Is atapicam part of the base? Yes. > I was=20 > under the impression it implements an=20 > abstracted SCSI interface over the ata=20 > device subsystem but maybe I'm not=20 > adequately understanding what's really=20 > happening. As the name suggests, it provides a CAM front-end to the devices, which is the same front-end used by the SCSI devices, so tools that expect to use CAM can work on the ATA devices too. > Just an observation but it seems as=20 > though there is a great deal of use=20 > being made of the atapicam subsystem. =20 > I noticed for instance that in addition=20 > to /dev/cd0 that /dev/pass0=20 > and /dev/da0 also did not show up until=20 > I rebuilt with atapicam or did I just=20 > miss them? The equivalent devices have different names under atapicam than ata, but why do you think they are necessary? > Unless I'm wrong doesn't this mean that=20 > usb drives and those types of devices=20 > need the atapicam subsystem? I suspect you're wrong. Kris --ikeVEW9yuYc//A+q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (FreeBSD) iD8DBQFEC1i5Wry0BWjoQKURAn2kAJ9wMaisu5b80AvTkwA5rtKmIwlBkgCfQEYd Ik0ugzzmj2T+zqcS7Siq3ck= =MExv -----END PGP SIGNATURE----- --ikeVEW9yuYc//A+q--