At 11:05 AM 8/6/02 +0200, Robert Muench wrote: >However, IIRC you can have a lot of streams in a NTFS file. BTW: The >stream feature is AFAIK available since NT 3.1 (1994). What you see in a >directory listing is the so called "default" stream. This stream has the >form of <filename>:$DATA
Isn't that supposed to be <filename>::$DATA ? The three fields are: <filename>:<stream>:<attribute> The default stream name is "" (without the quotes). The default attribute is $DATA. All attributes start with $ . Oh wait, I just remembered that since all attributes start with $, you can skip the stream name if you are just using the default and want to specify the attribute. So I guess that <filename>:$DATA would work after all :) > > In other words, <BFS> completelly smokes NTFS out. :) > >NTFS is not that bad. I like some features of BFS as well but IMO the >NTFS is really a nice thing. I don't remember the title of a book (if >you know it let me know it too) that tells the story about the NT >development. Very good read! Not very technical, instead it tells about >the people and up & downs while developing NT. There is a section about >the development efforts that went into NTFS etc. Robert The database search capabilities of BFS are where it smokes NTFS. But not for long: Future versions on Windows are slated to have the filesystem built on top of the SQL Server engine, rather than the other way around. When that happens, the smoke will definitely be blowing in the other direction! Brian -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
