From owner-cvs-all  Mon Oct  5 04:11:03 1998
Return-Path: <owner-cvs-all>
Received: (from daemon@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id EAA22312
          for cvs-all-outgoing; Mon, 5 Oct 1998 04:11:03 -0700 (PDT)
          (envelope-from owner-cvs-all)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA22307;
          Mon, 5 Oct 1998 04:11:01 -0700 (PDT)
          (envelope-from obrien@FreeBSD.org)
From: "David E. O'Brien" <obrien@FreeBSD.ORG>
Received: (from obrien@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id EAA01782;
	Mon, 5 Oct 1998 04:10:55 -0700 (PDT)
Date: Mon, 5 Oct 1998 04:10:55 -0700 (PDT)
Message-Id: <199810051110.EAA01782@freefall.freebsd.org>
To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
Subject: cvs commit: src/sys/kern vfs_init.c
Sender: owner-cvs-all@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

obrien      1998/10/05 04:10:55 PDT

  Modified files:
    sys/kern             vfs_init.c 
  Log:
  Taking the GENERIC kernel and commenting out MSDOSFS, CD9660{,_ROOT}, PROCFS,
  NFS_ROOT will produce kernel that cannot mount a UFS /.
  
  Vfs type numbers must be distinct from VFS_GENERIC (and VFS_VFSCONF, but
  that has the same value and should go away).
  
  The problem happens because NFS is the first vfs (in sys/conf order) so it
  gets type number 0 and conflicts harmfully with VFS_GENERIC which is also 0.
  The conflict is apparently harmless in the usual case when another vfs
  gets type number 0, because nfs is the only vfs that has sysctls.
  
  Inital fix by:	Dima <dima@tejblum.dnttm.rssi.ru>
  Reason why it worked by:	bde
  
  Revision  Changes    Path
  1.34      +3 -2      src/sys/kern/vfs_init.c