View Single Post
Old 11-08-2023, 12:58 PM   #59
nabsltd
Fanatic
nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.
 
Posts: 528
Karma: 9529956
Join Date: Aug 2013
Location: Hamden, CT
Device: Kindle Paperwhite (11th gen), Scribe, Kindle 4 Touch
Quote:
Originally Posted by Quoth View Post
Mapping a share to a drive letter absolutely doesn't make it the same as a local drive mount.
"Mapping a share to a drive letter"...how quaint.

That said, if the target of a file operation is not local, but is on a Windows machine, you still get all the same semantics as if it were local. File locking, security, delete, rename, open, read, etc., all behave in exactly the same way. You have full access to the details of the NTFS file system (multiple streams, sparse files, compression, etc.). What you can't access are objects that deal with the volume itself (e.g., the MFT).

And, unless you trace from the top of the path all the way to the bottom, examining every step for reparse points, it's very hard to know if the file is not on a local drive.
nabsltd is offline   Reply With Quote