From owner-freebsd-fs  Thu Sep 19 12:00:02 1996
Return-Path: owner-fs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id MAA17957
          for fs-outgoing; Thu, 19 Sep 1996 12:00:02 -0700 (PDT)
Received: from eac.iafrica.com (196-7-192-175.iafrica.com [196.7.192.175])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA17478
          for <freebsd-fs@freebsd.org>; Thu, 19 Sep 1996 11:59:05 -0700 (PDT)
Received: (from rnordier@localhost) by eac.iafrica.com (8.7.5/8.6.12) id UAA01168 for freebsd-fs@freebsd.org; Thu, 19 Sep 1996 20:59:04 +0200 (SAT)
From: Robert Nordier <rnordier@iafrica.com>
Message-Id: <199609191859.UAA01168@eac.iafrica.com>
Subject: [Q]: Is VFS_VGET filesystem-specific?
To: freebsd-fs@freebsd.org
Date: Thu, 19 Sep 1996 20:59:02 +0200 (SAT)
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-fs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Is VFS_VGET intended as a filesystem-specific function -- only for
filesystems actually using inodes -- or does it make sense to
implement it anyway, if it can be supported?

   int (*vfs_vget)(struct mount *mp, 
                   ino_t        ino, 
                   struct vnode **vpp);

The vfatfs makes use of a 'dnode' structure largely identical to
an inode, except that quota info is missing (can't be supported)
and the 'dinode' section differs (reflecting the much simpler DOS
directory entry structure).

The 'dnode' dn_number is equivalent to an inode i_number, with
ROOTDNO == ROOTINO, etc, and vfatfs_vget() is currently used in
much the same way ffs_vget() is.

Of course, it would be easy enough to rename the current vfatfs_vget(),
make it static, and just return EOPNOTSUPP.

Thanks.

-- 
Robert Nordier