Message-Id: <3.0.1.32.19971128092837.007e4c80@yacker.xiotech.com>
Date: Fri, 28 Nov 1997 09:28:37 -0600
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
From: Randy Maas <randym AT acm DOT org>
Subject: Re: proposed fsext changes
Cc: djgpp-workers AT delorie DOT com
In-Reply-To: <Pine.SUN.3.91.971127132351.5743E-100000@is>
References: <3 DOT 0 DOT 1 DOT 32 DOT 19971126114818 DOT 007eb680 AT yacker DOT xiotech DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Precedence: bulk

At 01:24 PM 11/27/97 +0200, Eli Zaretskii wrote:
>Shouldn't `fstat' also have a hook?

Probably.  How important is it?  (I'm still figuring out the proper
procedure for contributions.... 8-)  

more technically:
-- is there any concern about how the inode number is assigned by a fsext?
Otherwise... I'd be all too tempted to use the state pointer.  
-- should fsext be encouraged to ignore group and user id? (open and creat
seem to ignore this at the moment)... Or is there some some posixish
concerns, despite dos's best attempts to defeat us?
-- currently the device field is the drive letter.... what should be
recommended to fsext developpers for this field?  Maybe a pointer to the
fsext's entry point?
-- can fstat help template these fields in (and the fsext modify them if it
wants)?  Or is this a no-no?
-- What are the most important fields anyway?  My guess is st_mode and
st_mtime. 
-- Anything I forgot?

Randy