From owner-freebsd-current Fri Dec 10 22:59:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 183F214BF5; Fri, 10 Dec 1999 22:59:17 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA00670; Fri, 10 Dec 1999 23:59:15 -0700 (MST) (envelope-from ken) Message-Id: <199912110659.XAA00670@panzer.kdm.org> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912110553.VAA00494@mass.cdrom.com> from Mike Smith at "Dec 10, 1999 09:53:30 pm" To: msmith@freebsd.org (Mike Smith) Date: Fri, 10 Dec 1999 23:59:15 -0700 (MST) Cc: freebsd-current@freebsd.org From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote... > > And as for the device renaming, you didn't have to change anything from > > sd->da. The old device names and nodes were supported in most every way. > > There were a lot of mis-informed people on the lists who claimed that you > > had to change your device names. That was completely untrue, and I > > attempted to correct people, but the myth and FUD continued to propagate. > > Changing the device nodes' names was the only sensible thing to do when > everything else that referred to the device by name (source files, kernel > config, boot-time messages) used the new name. Ther Looks like your mail got a little truncated. In any case, yes, it does make more sense to be consistent and use the new names, but what I was getting at is that there were some folks who said things like: "You have to change all your device names to da* in order to use CAM." That isn't true, of course, but it certainly caused some confusion and consternation. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message