From owner-freebsd-current Sat Dec 11 13:48:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [207.167.3.130]) by hub.freebsd.org (Postfix) with ESMTP id 72A1614F50 for ; Sat, 11 Dec 1999 13:48:17 -0800 (PST) (envelope-from lyndon@orthanc.ab.ca) Received: from orthanc.ab.ca (localhost.orthanc.ab.ca [127.0.0.1]) by orthanc.ab.ca (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id dBBLmCQ85894 for ; Sat, 11 Dec 1999 14:48:13 -0700 (MST) Message-Id: <199912112148.dBBLmCQ85894@orthanc.ab.ca> To: freebsd-current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Sat, 11 Dec 1999 11:41:22 +0100." Date: Sat, 11 Dec 1999 14:48:12 -0700 From: Lyndon Nerenberg Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Dieter" == Dieter Rothacker writes: Dieter> Why would you want to define "correct" numbering the Dieter> non-spread-out numbering? Or did I misunderstand you? I Dieter> have all my disks as master drives on the channels. Now, Dieter> when I hook up another disk for backup or maintenance Dieter> purposes, my numbering is messed up. Or worse, on a file server where you lose a low-numbered disk, not only does that one go away, but everything higher numbered loses as well. This "feature" does nothing other than introduce a gratuitous backwards-incompatibility. There is nothing wrong with the "old" scheme. I've loathed this behaviour since it was introduced into SCSI/CAM, and would rejoice at its removal. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message