From owner-freebsd-scsi Tue Jul 14 08:45:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20743 for freebsd-scsi-outgoing; Tue, 14 Jul 1998 08:45:24 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20736 for ; Tue, 14 Jul 1998 08:45:21 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id JAA08757; Tue, 14 Jul 1998 09:44:47 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199807141544.JAA08757@panzer.plutotech.com> Subject: Re: cam/scsi include files In-Reply-To: from Cory Kempf at "Jul 13, 98 11:45:01 pm" To: ckempf@enigami.com (Cory Kempf) Date: Tue, 14 Jul 1998 09:44:47 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Cory Kempf wrote... > I could swear I have posted this at least twice now, but the original > doesn't seem to be on my machine for some reason. And if the answer > has changed with the new snapshot, well, it is downloading now. > > While perusing the SANE source, I noticed that it checks for the > existance of files under /usr/include/scsi... and if it finds them, > determines that it should use the BSD SCSI interface. There's no /usr/include/scsi directory, even with the old SCSI code. > On my machine, it finds them, and builds successfully (haven't tried > running, as the SCSI bus isn't quite working yet... see other > message). > > Is /usr/include/scsi obsolete with CAM? Assuming it is, perhaps it > might be a good idea to include a shell script to move that (and any > other obsolete files... e.g. libraries?) to say, scsi.old or some > such? It is, and isn't obsolete. It's actually "/usr/include/scsi.h". One or two people have asked for a compatibility interface with the old SCSI code under CAM. If that happens, we'll need the old code as well as the new. If you're concerned about porting stuff to CAM, I would suggest testing for the presence of /usr/include/camlib.h. That's what I did in the cdrecord, tosha and xmcd ports. > On a related note, I noticed that DEC's CAM interface stores its > include files under /usr/include/io/cam... shouldn't we also? > > Personally, I find it rather annoying when different vendor's unixes > stick things in different locations. It makes writing portable stuffs > more difficult. I don't see any real reason to stick things in the same place DEC's CAM implementation does. It isn't defined in the spec (AFAIK), and our data structures differ from theirs anyways. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message