From owner-freebsd-hardware Fri Nov 9 17:30:20 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 9C26437B422; Fri, 9 Nov 2001 17:30:18 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fAA1VfP05200; Fri, 9 Nov 2001 17:31:41 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200111100131.fAA1VfP05200@mass.dis.org> To: Brooks Davis Cc: Mike Smith , clefevre@citeweb.net, Erin Fortenberry , "'Thomas Coppens'" , freebsd-hardware@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: Installing FreeBSD on a RAID0 array with onboard RAID In-Reply-To: Message from Brooks Davis of "Fri, 09 Nov 2001 17:00:35 PST." <20011109170035.A30173@Odin.AC.HMC.Edu> Date: Fri, 09 Nov 2001 17:31:41 -0800 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > There is no risk of conflict, since neither driver uses > > devclass_find(), and the actual name of the driver is otherwise irrelevan= > t. > >=20 > > You could (almost) legitimately call all disk drivers 'disk' and get > > away with it. > > Isn't there a problem on devfs systems? It looks (to my rather limited > knowledge) like both should try to create /dev entries. Not until jlemon added device nodes for network devices, no. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message