Ted,
It belongs to the file system; that’s why a FILTER cannot assume they know
what is in it (heck, as an FSD I could just free the memory.)
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
-----Original Message-----
From: Ted Hess [mailto:xxxxx@livevault.com]
Sent: Friday, January 17, 2003 4:48 PM
To: File Systems Developers
Subject: [ntfsd] Re: Determining correct rename target path for fully-
qualified rename case
Well then how come the FS can use it?
/ted
-----Original Message-----
From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
Sent: Friday, January 17, 2003 4:04 PM
To: File Systems Developers
Subject: [ntfsd] Re: Determining correct rename target path for
fully-qualified rename case
So my question is: Is it legal to use the FileObject.FileName field
in a
No. FileObject->FileName is valid only in CREATE path down, it can be
invalid even in CREATE completion.
Max
You are currently subscribed to ntfsd as: xxxxx@livevault.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com