From owner-freebsd-arch Wed Feb 28 14: 8:25 2001 Delivered-To: freebsd-arch@freebsd.org Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80]) by hub.freebsd.org (Postfix) with ESMTP id 5D39B37B718 for ; Wed, 28 Feb 2001 14:08:23 -0800 (PST) (envelope-from scott_long@btc.adaptec.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id OAA22216 for ; Wed, 28 Feb 2001 14:08:23 -0800 (PST) Received: from btc.btc.adaptec.com (btc.btc.adaptec.com [162.62.64.10]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id OAA22500 for ; Wed, 28 Feb 2001 14:00:39 -0800 (PST) Received: from btcexc01.btc.adaptec.com (btcexc01 [162.62.147.10]) by btc.btc.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id PAA25883 for ; Wed, 28 Feb 2001 15:08:20 -0700 (MST) Received: by btcexc01.btc.adaptec.com with Internet Mail Service (5.5.2650.21) id ; Wed, 28 Feb 2001 15:08:21 -0700 Message-ID: From: "Long, Scott" To: "'freebsd-arch@freebsd.org'" Subject: Arch question for a UDF FS driver Date: Wed, 28 Feb 2001 15:08:21 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've starting writing a UDF FS driver for FreeBSD, and am coming to a decision point. UDF is somewhat similar to ufs in that a File Entry is analogous to an inode, so I'd like to implement the filesystem using the vget vfsop. Problem is that vget uses ino_t which is a uint32_t, while the Unique Id (aka inode number) for UDF is a uint64_t. Unique Id's are numbered sequentially starting at 16 (0 is the root dir, 1-15 are reserved), and may be sparse. So what color should I paint the bikeshed? Pink: Just pretend the UniqueId is 32 bits. If it is ever more than 32 bits, panic. Advantage: it's pretty hard to roll over 32 bits on a CD or DVD. Disadvantage: it's a gross hack. Muave: Don't implemenet it with vget. Advantage: no need to worry about the UniqueId. Disadvantage: harder to support some of the filesystem features, like hardlinks, once write support is done. Orange: Get ino_t bumped up to a uint64_t and modify all the other filesystems to deal with it accordingly. Advantage: no hackery needed for UDF. Disadvantage: may be the mother of all bikesheds. I prefer orange. Thanks for the advice. Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message