From owner-freebsd-scsi Thu Apr 23 18:18:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29838 for freebsd-scsi-outgoing; Thu, 23 Apr 1998 18:18:10 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA29811 for ; Thu, 23 Apr 1998 18:17:44 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id UAA00373 for ; Thu, 23 Apr 1998 20:16:45 -0400 (EDT) Date: Thu, 23 Apr 1998 20:16:44 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@localhost To: scsi@FreeBSD.ORG Subject: CAM drivers Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I hope this is the right place to post about the cam stuff ... Anyhow, I just went ahead and applied the CAM patches, and booted a CAM kernel. No explosions yet, but some observations here. Like, the instructions to install cam didn't include changing the fstab stuff to use the new sdn disk devices instead of the new dan devices, so I figured that was the reason that the bootup messsages said sd0, sd1, etc. After that, I changed my fstab to use the new devices, rebooted, and whala!, it *still* used the sdn names in boot. Uhh, ok, when getting ready to post this message, I checked my dmesg, where the mountable filesystem stuff showed up as dan, the swap spaces as sdn, and I'm pretty sure there were *no* dan messages in the actual onscreen boot messages. The messages for the swap partitions used the old sdn names both in the dmesg and the onscreen message. Like I said, this was from a fstab that had been edited to use the new dan names only. I occurs to me, since all the discussions of a complete cutover fromt eh old drivers to the new, that I can't understand why there needs to be any new name for the disks at all ... can't the sdn names just be reused, if the new and old stuff is never going to coexist? One last point ... the initial boot prompt still talked about wd0 or sd0. Make world ain't going to change that one .... so folks better get ready for a lot of confused newbie questions, from folks wondering why they have to specify a non-existent disk device. Overall, ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message