> The 0 inode numbers will slowly disappear. You don't need to worry
> too much about them I think.

I am surprised that Coda would ever reveal illegal or incorrect
filesystem entries to an application.  Applications deserve to lose
when they don't trap file-related errors.  But giving them illegal and
nonexistant inode numbers (zero) to work with is unfair.

I think I would prefer to get an error back, such as EIO, whenever I
tried to do a file system call whose results would be outside the
guarantees my filesystem provides.  What has been your experience and
how have your users felt about the application view of errors?


Another member of the League for Programming Freedom (LPF) www.lpf.org
-------------------------------------------------------------------------------
Brian Bartholomew - bb_at_wv.com - www.wv.com - Working Version, Cambridge, MA