From owner-freebsd-current Wed May 10 20:38: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id 4F57E37B7E4 for ; Wed, 10 May 2000 20:37:56 -0700 (PDT) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id KAA01413; Thu, 11 May 2000 10:37:51 +0700 (NOVST) (envelope-from nnd) Date: Thu, 11 May 2000 10:37:51 +0700 (NOVST) Message-Id: <200005110337.KAA01413@wint.itfs.nsk.su> From: Nickolay Dudorov To: current@freebsd.org Subject: Re: It seems that SCSI code still use block devices In-Reply-To: <20000511055501.A52142@nagual.pp.ru> User-Agent: tin/1.4.2-20000205 ("Possession") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <20000511055501.A52142@nagual.pp.ru> Andrey A. Chernov wrote: > Just got from recent kernel: > > Mounting root from ufs:/dev/da0s1a > Device char-major=13 minor=131072 opened in block mode, convert to char mode with /dev/MAKEDEV before 2000-07-01 > > The suggestion is strange indeed, /dev/da0s1a ALREADY IS character device. > It means that kernel mounting code itself still use block devices. Moreover I've got: Mounting root from ufs:/dev/ad0s1a ^^ Device char-major=116 minor=131072 opened in block mode, convert to char mode with /dev/MAKEDEV before 2000-07-01 So the problem is not in the SCSI code, but in the "root mounting" code. N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message