From owner-freebsd-current  Sun Jul 28 09:24:13 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id JAA29283
          for current-outgoing; Sun, 28 Jul 1996 09:24:13 -0700 (PDT)
Received: from spinner.DIALix.COM (spinner.DIALix.COM [192.203.228.67])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA29267
          for <current@freebsd.org>; Sun, 28 Jul 1996 09:24:10 -0700 (PDT)
Received: from spinner.DIALix.COM (localhost.DIALix.oz.au [127.0.0.1]) by spinner.DIALix.COM (8.7.5/8.7.3) with ESMTP id AAA01851 for <current@freebsd.org>; Mon, 29 Jul 1996 00:24:06 +0800 (WST)
Message-Id: <199607281624.AAA01851@spinner.DIALix.COM>
To: current@freebsd.org
Subject: DEVFS broken by last devsw_add_generic()/bdevvp() changes
Date: Mon, 29 Jul 1996 00:24:05 +0800
From: Peter Wemm <peter@spinner.DIALix.COM>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

It seems the last set of changes to the devsw creation routines and the
subsequent bdevvp() change has broken ffs_mount when trying to mount the
root filesystem on at least scsi disks.

The "new" bdevvp() is returning 0, and ffs_mount is not checking it before
passing it onto ffs_mountfs.

This might be because of the slice code not knowing whether or not it's
using the compatabilty slices or not, or simply because nothing has accessed
the slices in the first place to cause the slice code to create the
initial nodes in devfs.

So, if you are using "options DEVFS", beware, you may not be able to boot
anymore, regardless of whether you are mounting the filesystem.

-Peter