Date: Wed, 28 Feb 2001 15:08:21 -0700 From: "Long, Scott" <scott_long@btc.adaptec.com> To: "'freebsd-arch@freebsd.org'" <freebsd-arch@freebsd.org> Subject: Arch question for a UDF FS driver Message-ID: <E0BFB46945D5D411BB590000D11ABE9203349F@btcexc01.btc.adaptec.com>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E0BFB46945D5D411BB590000D11ABE9203349F>