Slashdot Mirror


WinFS Beta 1 Released Early

Mouldy Punk writes "Infoworld is reporting that WinFS Beta 1 has been released. The new relational file system for Windows is posted on MSDN Subscriber Downloads. This release is designed to offer developers a preview of WinFS capabilities. WinFS will be in beta when Windows Vista ships and will RTM afterwords. WinFS, when it ships, will be available for download for Windows Vista and possible support for Windows XP is being considered. The distribution mechanism for WinFS will be through an add-on download much like the .NET framework is today. Tom Rizzo also notes that there is a new blog dedicated to Win FS."

42 of 582 comments (clear)

  1. Rushed? by PunkOfLinux · · Score: 2, Insightful

    Chances are, they rushed it out the door and it's going to be absolutely terrible. In other news, Microsoft released something ahead of schedule! Unlike 'Vista' (I'll always call it longhorn)

    1. Re:Rushed? by jonadab · · Score: 3, Insightful

      > Unlike 'Vista' (I'll always call it longhorn)

      Vista is not Longhorn -- at least, not as Longhorn was envisioned at one time.

      Longhorn, it was said, will use WinFS as its native filesystem. (It will include support for fat32, ntfs, fat16, iso9660, and possibly fat12, but these will be "legacy" systems, deprecated, and probably not supported for the main filesystem where the OS is installed, only for additional filesystems, such as on removable drives.) Vista will still use ntfs as its primary native filesystem; although WinFS can be added to it later, that is an add-on.

      Longhorn, it was said, will include the new shell, Monad. Vista will not.

      Oh, and Longhorn, it was said, will ship in 2004. Vista will not.

      Vista is the Windows 98 SE of our time -- it's not the big upcoming release Microsoft has talked about for so long, and it doesn't have the capabilities that the big upcoming release was supposed to have, or in fact any new capabilities, and it's not going to be a compelling upgrade, but it has to come out, because it's just plain been *too long* since the last release and the market can't wait until the real thing is done.

      Microsoft's release cycle gets lengthier with each passing year. Nine months after they finally release Vista, they'll be talking about the next big release (not the server version of Longhorn, I mean, but the successor to Longhorn), but you won't see *that* one for a good long while. Even giving them the benefit of the doubt and assuming they manage to get Vista out the door in 2006 as they currently say they're fixed to do, that means they'll start talking about Blackcomb in 2007, and by 1Q2008 they'll be predicting they can have it out by "next year) (2009), but the earliest you might possibly see it on store shelves is 2012, and frankly 2015 is more likely.

      This is actually good news for the OSS community. It means we have a fairly good idea what the Microsoft desktop is going to look like for the next 7-10 years. Sure, there'll be add-ons, WinFS and eventually Monad, but add-ons are add-ons; if you want add-ons on an OSS system you can have Reiser4 today (though I don't know how stable it is yet -- but WinFS hasn't even been officially released, so I guess we're okay there), and Perl6 is likely to beat Monad to market, or in any case there are a number of excellent scripting languages available today; we haven't had to get by with just a bourne shell for quite some time, to say nothing of making do with the likes of cmd.exe. (Yes, there are people who advocate doing everything in old-school sh for the portability, but they're talking about portability in terms of running on fifteen-year-old systems; the Microsoft equivalent would be writing .bat files that will run under anything from DOS 5.0 upwards.)

      I guess what I'm saying is that we know what to expect. Microsoft has grown large enough to become fairly predictable. That's good for the competition.

      --
      Cut that out, or I will ship you to Norilsk in a box.
  2. Is this really a file system? by jbplou · · Score: 3, Insightful

    A file system that you get by an add-on? What good will that do, most desktops in Windows have partion set to ntfs under XP what do you do with it once you added it on. Is this really a file system or is it a indexer of files.

    1. Re:Is this really a file system? by Anonymous Coward · · Score: 3, Insightful

      You can convert ex2fs to ext3fs, and you can convert fat32 to ntfs. There is a good chance you will be able to upgrade ntfs to winfs.

    2. Re:Is this really a file system? by Tackhead · · Score: 3, Insightful
      > A file system that you get by an add-on? What good will that do, most desktops in Windows have partion set to ntfs under XP what do you do with it once you added it on. Is this really a file system or is it a indexer of files.

      The bu^H^Hfeature is that you no longer get^H^H^Hneed to know where your files are.

      Some idiot UI designer probably wrote a paper about how Windows users are confused as to where their files are located.

      Rather than addressing the root of the problem -- the even bigger idiot UI designer for Windows 95 who decided to (a) by default, hide the full path to the file and (b) again by default, also hide the file extension, and (c) when users turn off "hide file extensions", still hide some file extensions like .SHS, etc -- and whose mistake was propagated to Windows 98, 98SE, ME, NT, 2K, XP, and 2K3, effectively making it impossible for nontechnical users to ever learn where their files were located...

      Ahem. Rather than addressing the real problem of why nontechnical users had trouble finding where their files were, the idiot UI designer for WinFS decided to take idiocy to its most proper level: at no time should a user ever be able to find a file. At no time should a user ever be able to choose a file's location. Teh desktop is like teh Intarweb, the user should have to goo^H^H^Huse some sort of MSN Desktop Search tool in order to find "content".

      Microsoft UI: Dumber than advertised, and making sure our users stay that way.

    3. Re:Is this really a file system? by ciroknight · · Score: 4, Insightful

      To be honest, I rather like the model of files having no direct location, rather, just a byte-heap in a database. For a long time, this is actually how I've organized my files on my disk, but the problem is, every now and again, your mind changes how you want to lay out all of the files, and it takes a few hours to refile everything in the correct folders.

      With folders going the way of the highway, you can just heap whatever files you want, wherever you want, without all of that path confusion. Deal with namespace collisions either with longer, more descriptive file names, unique file identifiers, or a mixture of the two.

      You might find it idiotic, but I find it as the best way to organize my files and find what I want, as fast as possible. Pair it with a program that can rip my files apart for all of the metadata that it can give up, index that along side the files, and no file is ever more than a few mouseclicks away. Best yet, instead of having to delete and move files around, which thrashes the disk and makes the filesystem a disaster, the filesystem can effeciently use space because it can know exactly how big the files are, and start sticking files right up next to each other. And if I were designing the UI for this thing, you'd be able to change over to a pane, change the SQL query, and poof, the folder displays what you want.

      No more rediculous symlinks. No more folder paths, executable paths, etc. Better isolation of executable files and libraries and configurations, verses userspace files. Honestly, the advantages outweigh the disadvantages IMO.

      --
      "Victory means exit strategy, and it's important for the President to explain to us what the exit strategy is." G.W.Bush
    4. Re:Is this really a file system? by emidln · · Score: 2, Insightful

      So this is an mechanism for extended attributes and an api to access them with a front-end already authored? So how is this better than HFS+ with spotlight? Or FreeBSD's UFS2+extended attributes + KDE patches Or ReiserFS4 + scripts? (Other than the obvious that it works on Windows.)

    5. Re:Is this really a file system? by EggyToast · · Score: 2, Insightful

      That's not the case with XP. I've tested it out -- use the install disc to format to NTFS, then switch over to Linux. It'll ID it correctly as NTFS.

    6. Re:Is this really a file system? by Wonko · · Score: 2, Insightful

      That's not the case with XP. I've tested it out -- use the install disc to format to NTFS, then switch over to Linux. It'll ID it correctly as NTFS.

      Where exactly does it say that the partition ID has to match the filesystem that is currently on the drive? Did you try actually mounting it to make sure?

      I have no idea what Windows does at that point in the install process, and it really make no difference at all.

    7. Re:Is this really a file system? by UnrefinedLayman · · Score: 1, Insightful

      Windows 2000, Windows XP and Windows 2003 have always formatted the drive as NTFS if selected and installed directly onto it. There are full and quick format options available in the setup process.

      Manipulating Windows setup during the setup was the only way to get it to install on some older hardware. I used a lot of NTFSDOS to get things done. I ran into the same issues when manipulating files to have integrated SCSI drivers.

      Out of curiosity, where did you get that little factoid?

    8. Re:Is this really a file system? by Anonymous Coward · · Score: 3, Insightful
      > You might find it idiotic, but I find it as the best way to organize my files and find what I want, as fast as possible. Pair it with a program that can rip my files apart for all of the metadata that it can give up, index that along side the files, and no file is ever more than a few mouseclicks away.

      That's a reasonable solution for a technical user.

      ...to consistently and correctly enter and update the metadata about their files?

      It's hard enough to get people to ID3V1 or V2-tag their MP3 files.

      But is even the most diehard of us going to bother to add the appropriate "pr0n_actiontype=[ clothed | b00bies | fullfrontal | hardcore | facial | [single|double|triple|OMGshesahunkaswisscheese]pen etration] ]" tag to each of the images in the 100-image series we just finished downloading and group-tagging with "pr0n_model1_haircolor=blonde" pr0n_model1_b00bsize=38DD"?

      My goofy example illustrates my main point: is it reasonable to expect 100,000,000 non-technical users, the overwhelming majority of whom currently have trouble understanding metadata fields like file length, format, and name... in other words, people who store stuff like this:

      C:\Documents and Settings\Foo\My Documents\New Report.doc
      C:\Documents and Settings\Foo\My Documents\Report.doc
      C:\Documents and Settings\Foo\My Documents\Report2 .doc
      C:\Documents and Settings\Foo\Application Data\Adobe Acrobat 6.0\New Report I Said Make it a PDF.pdf
      C:\Documents and Settings\Foo\Desktop\New Report.lnk
      C:\Documents and Settings\Foo\Desktop\New Report in PDF format.lnk
      C:\Documents and Settings\Foo\Desktop\New Report I Said Make it a PDF.lnk

      ...to consistently and correctly enter (and update!) metadata about their files?

      If Grand Moff Tarkin had "I think you overestimate their chances" in response, the Death Star would still be with us.

    9. Re:Is this really a file system? by Skreems · · Score: 4, Insightful

      That post just made my day :-) Hilarious. 90% of users don't understand that the Desktop is actually a file in a heirarchical structure. If you stopped hiding that fact from them, sat them down and said "look, here's how things are structured"... you could fix all of this in about 10 minutes. Perpetuating the "hide things from the stupid user" UI philosophy only makes people less willing to learn, and thus increases the need for stupid workarounds to fix it. Vicious cycle.

      --
      Slashdot needs a "-1, Wrong" moderation option.
      The Urban Hippie
    10. Re:Is this really a file system? by NeMon'ess · · Score: 2, Insightful

      People who don't use folders correctly aren't going to use this correctly either, so for them there is no difference.

      People who use folders will instead of spending 10 seconds navigating to the right folder, spend 10 seconds clicking and typing keywords. Once a keyword is entered, it can be remembered so the Save dialog box can have multiple checkboxes for freqently used words. If I select "hardcore", several more boxes to check could appear such as "asian" "blowjob" and "threesome". Adult words could also be hidden in several ways to keep kids from stumbling upon them.

      Just as IE currently remembers the folder files were saved to, for a batch of pictures or movies, the same checkboxes could show up to speed things up.

      Anyway, how descriptive the metadata gets is up to the users. Just like in iTunes people can add Grouping data to supplement the single Genre tag.

    11. Re:Is this really a file system? by ciroknight · · Score: 2, Insightful

      Why does a human have to enter the metadata? Why not let the machine do what it can to derive what the file is about, and ask the human whether or not it's right? Such a system can be taught to "learn" when it's right or wrong, and it'd get better with time.

      People can't update their ID3 tags. But they can download a program like MusicBrainz which is a database of ID3 tags that those of us with the time do things right.

      To be truthful, the worse metadata that exists today in my opinion is that of Photos, and that of Movies. Everyone's got a solution out there that works for music, but that solution disentegrates when you point it at a collection of pictures, or a bunch of movies. It's also hard (but not impossible) to write a program which can look at a movie and tell you what movie it is, or look at a bunch of pictures and based on previous experience, tell you who's in that picture, or what that picture is of. That makes visual programs distinctly harder to categorize, verses a machine which can listen to music and instantly identify it.

      Lastly, your example more or less proves my point. Look at all of those links. Why do you need a link that points at a file, ever? If you have the damned file, you don't need someone pointing at it and saying "there it is!", you need the software saying "here's your file sir".

      --
      "Victory means exit strategy, and it's important for the President to explain to us what the exit strategy is." G.W.Bush
    12. Re:Is this really a file system? by tsa · · Score: 4, Insightful

      The root of the problem is that most people do not care where their files are located. They just want it to work.

      That attitude (of the most people you are talking about) to me is just like, for instance: ``I don't want to learn about strings and notes, I just want to play the guitar!''

      People will have to get it into their heads that computers are complicated things and you need some basic understanding of how they work before being able to use them. Have you ever seen a `My Documents' folder of someone who doesn't want to know about computers? No wonder they're always complaining that `it doesn't work.'

      --

      -- Cheers!

    13. Re:Is this really a file system? by GuyWithLag · · Score: 3, Insightful

      The thing with the underscores is that in a CLI you don't need to quote them, whereas a space needs at least an extra character to quote it.

      Some of us have grown up, and still prefer the CLI. What can you, as a person, improve easier? CLI typing speed or GUI mouse accurracy?

      The GUI's strangth is providing you with information. The CLI's strength is in receiving commands.

      Now if I could only merge gnome-terminal with nautilus...

    14. Re:Is this really a file system? by ilyaaohell · · Score: 2, Insightful

      People will have to get it into their heads that computers are complicated things and you need some basic understanding of how they work before being able to use them.

      And people like YOU will have to get it into your heads that it is the job of the technologists to take things which are inherently comlicated, and spend as much time as possibly making them less so, up to a point where interaction with the technology is as simple as pushing against a door to open it.

      Your guitar analogy is quite idiotic as well. There are only so many people who are psychologically inclined to write or perform guitar music. Usage of common household appliances, like television sets, microwaves, and computers, should NOT take any specific effort to use. And if they do, then they're either ill-conceived, poorly designed, or in an unfinished experimental stage.

      --
      UNIX: A computer user is defined as a programmer. WINDOWS: A computer user is defined as a consumer.
    15. Re:Is this really a file system? by tsa · · Score: 2, Insightful

      You have a point there.

      Usage of common household appliances, like television sets, microwaves, and computers, should NOT take any specific effort to use. And if they do, then they're either ill-conceived, poorly designed, or in an unfinished experimental stage.

      I think computer interfaces are still in the unfinished experimental stage. Until they come out of that, people will have to learn how to operate computers.

      --

      -- Cheers!

    16. Re:Is this really a file system? by ilyaaohell · · Score: 2, Insightful

      Let me put it to you this way:

      If you want to use a modern cell phone, do you need to know how it stores data, what operating system it uses, or how it's address book is stored in the phone's hardware? Or do you simply need to know that is has the capability of saving your friends' phone numbers and know the simple process of navigating through this list?

      --
      UNIX: A computer user is defined as a programmer. WINDOWS: A computer user is defined as a consumer.
    17. Re:Is this really a file system? by aconbere · · Score: 2, Insightful

      Have you dared to bring up cell phones as an example of a refined UI? My god all mighty, it's as if they were designed by a monkey's equivelent of a 13 year old boy. Some buttons do one thing in one area, and a different thing in another, and lots of times the two functions are complete opposites of eachother. And let us not mention the complete and utter breakdown of a proper menuing system.

      I understand that they are limited by size. But Christ, all I want to do is make the call and hang up, why do all the buttons do different things?! why are there two buttons, okay, and call when do I use which, under what circumstances do their functionalities overlap? Why is it different on every phone!

      I'm not saying that computers don't need to nail that UI, and I do believe that the User Interface for most computers should by default be simple with the complex underbelly easily brought forward for those of us that apreciate such things.

      Having said that, i doubt that I would agree with you on what a good, simple UI is. *changes his track in orpheus*

      ~Anders

    18. Re:Is this really a file system? by Vanders · · Score: 3, Insightful

      ..to a point where interaction with the technology is as simple as pushing against a door to open it.

      General purpose computing devices will never, ever be as simple as you wish. Notice that all the devices you list are single-function devices; they have a finite set of states and are capable of doing only one job.

      A computer is nothing like a toaster. It is a general purpose device with an almost inifinite number of states. It's "jobs" are mearly abstractions. It can do one, many, or no jobs at any one given moment. It can not and will never have a simple interface, because it's job is not simple.

      Now creating simple specific interfaces to common well understood jobs may be possible. That's still a very small subset of what a computer does though.

    19. Re:Is this really a file system? by prisoner-of-enigma · · Score: 2, Insightful

      Now creating simple specific interfaces to common well understood jobs may be possible. That's still a very small subset of what a computer does though.

      But I think that's exactly what WinFS is trying to do here. It's creating a specific, simple interface (the WinFS browser) to do a common, well-understood job (finding and organizing your files). The fact that it does so in a manner alien to you does not mean it is wrong or stupid.

      There's a very good analogy lesson here with MP3 collections. Back when I only had a few hundred MP3's, I organized them manually into folders by genre and artist. It was time consuming and sometimes conflicting, as some albums had multiple artists or multiple genres (or both). The system never really quite worked because there were too many possible ways to sort the files, yet the file system was essentially fixed.

      Then along come the MP3 managers, or MP3 players with built-in managers like WinAMP. Now, I can lump all my files into a single directory. WinAMP searches the metadata in each file (and since I rip my own, I make sure they all have proper metadata). If I want to go looking for Jazz, I can search by genre. If I want to search by decade, I can do that. Artist, ditto. Song title or even portions thereof, ditto. No matter how I want to slice and dice my MP3 collection, it works how I want it to work. And no collection of folders can duplicate this ease of use and flexibility no matter how crazy you make them.

      The "files and folders" metaphor has been with us for more than three decades. We can do better. We should do better. File systems like WinFS (and their Linux equivalents) should be embraced, not shunned.

      --
      In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
    20. Re:Is this really a file system? by zootm · · Score: 2, Insightful

      I agree that "pushing a door" is a simple analogy, but our abstraction is getting better all the time. One should not need to know how a computer works in order to undertake a task which does not directly involve "making the computer work". You shouldn't need to have to understand paths to save a file. I don't want the file with the name "letter to Bob" and last week's timestamp in the work subdirectory of the text docs folder with the correct file type. I want the letter I wrote to Bob last week. To a technical user like you or I these may be the same thing, but they're far, far from it. Another benefit that I desire is multiple membership of areas ("all the text documents" and "all the documents for work" are mutually exclusive goals of organisation with a traditional path structure, but their coexistence is both useful and not conceptually difficult).

  3. diff -u WinXP Vista by Goalie_Ca · · Score: 3, Insightful

    Seriously, if this is being backported to XP then what will be the difference between XP and Vista? Afaik all the avalon and .net libraries are being backported. All i can think of is a glass looking interface, some toolbars and a bunch of wizards?

    --

    ----
    Go canucks, habs, and sens!
  4. Re:Too complicated....... by wbren · · Score: 5, Insightful
    Why even released it at alL? 99% of those idiot windows users don't even know what the heck a partition is..... How can you expect them to reformat the drive to WinFS and re-install Windows on top of it all??? Unless you can convert NTFS into WinFS, theres no hope for most users, but of course... theres always geeksquad.
    So much to cover, so little time. Windows bashing. Windows users bashing. GeekSquad bashing. Oh my! If you take what you're saying and shift it back to 1999's context, it's like someone saying, "Windows 98 users are too dumb to use NTFS! None of them will be able to reformat their drive to NTFS and install Windows XP! There's no hope! All is lost! Run for the hills!" and so on. (And that's all before XP was even released)

    Well, of course, things went pretty smoothly. Users were able to easily convert their partitions to NTFS when upgrading (even if they didn't know what a partition was). New PCs came with NTFS by default, and Windows XP+NTFS succeeded largely (unless you're a Linux fanboy and don't want to admit it; in that case it never happened, how could it?). The (Windows) world was a better place now that FAT32 was largely a thing of the past. I'm not so sure if WinFS will be all that great, but we'll see.

    Windows Vista will be no different than the 98 to XP conversion. NTFS users will be able to easily convert their partitions. Again, they will be able to do it even if they don't know what it is exactly. As long as they know it's recommended, they will keep clicking the Next button. You're worrying about something that will clearly never happen, given Microsoft's track record.

    The add-on will likely be via Windows Update and extremely simple to apply. People who buy PCs after the add-on is released won't even have to do that. They will just have WinFS.

    I also want to touch upon the phrase "idiot windows users" that you used. Saying something like that only serves to make you sound like an idiot. Windows users are largely novices, but you can't expect everyone to be an expert user able to keep up with the quirks of Linux et al. Calling Windows users idiots is like calling people who drive car's with automatic transmissions idiots. Sure, automatics are easier to learn to use, but that doesn't make those drivers idiots.

    Now, I could go on to write a whole article bashing Geek Squad, but that would be pointless since we all know they suck and they overcharge.
    --
    -William Brendel
  5. but what about the interface to it? by Gothmolly · · Score: 5, Insightful

    Right now you can add attributes to NTFS files, but there's no decent way to do it. Likewise, ANY DB-style FS is going to be limited to the ways that the vendor (MS) provides for you to access the data. Remember those ridiculous dialogs Winword used to prompt with? Asking all that crap about the author, and topic, etc. etc. until you asked Clippy how to turn the fscking thing off?
    The "DB based FS" is only as good as the data that you put in, unless you solely want to make virtual folders of "all my MP3s that I warez'd last week from Rancid", but I'd say those sorts of things are going to be in the minority.. and again, depend on the metadata of said pirate MP3s.
    Now there will be code jocks out there who would LOVE this sort of thing, since you could probably use it as a halfway decent free CVS replacement, but I'm thinking more of Joe and Jane Sixpack. How is it going to make their AOL experience better?

    --
    I want to delete my account but Slashdot doesn't allow it.
  6. Re:Not to sound too offtopic, but... by merreborn · · Score: 3, Insightful

    There's one good reason to switch to vista: Microsoft ends support of their OSes after 5 years. Windows 2k, as much as I love it, isn't going to be much fun after a few years without a single patch. XP will go the same way before long.

  7. Re:Not to sound too offtopic, but... by DrCode · · Score: 5, Insightful

    About performance...

    It's somewhat telling that you were pleased that it ran just as fast as XP on the same system. On my Linux box, when I upgrade the kernel or even KDE, I generally expect better performance than before. I get the impression that OSX users expect the same.

  8. Re:Too complicated....... by bbrazil · · Score: 2, Insightful

    99% of windows users have no need for partitioning their hard drive. Do you know what happens most of the time when people create windows partitions? Someone thinks they are clever and creates seperate partition for their data, another for their programs, and another for a swap file, etc... This whole system quickly breaks down when one partition becomes full.

    Eh, no. Seperating user data from applications is a very good idea. It has saved me a lot of time and trouble (on Windows and Unix) when things went wrong, and I've helped other people who really wished that they'd done it too.

  9. Re:SQL for the file system doesn't sound stable to by DogDude · · Score: 2, Insightful

    Under what circumstances have you seen SQL Server be "unstable"? I've been a database guy for a *long* time and I've never seen any kind of "crashing". You're talking about a pretty prestigious database. Not quite on par with Oracle, but there's no comparison with something like MySQL.

    --
    I don't respond to AC's.
  10. early? itsn't it already late?? by Anonymous Coward · · Score: 1, Insightful

    i thought longhorn was already late

  11. about...? by __aazofn1209 · · Score: 2, Insightful
    DRM has always been about control and nothing else.

    Control? I think you mean money.

  12. Re:GNOME Storage? by ciroknight · · Score: 3, Insightful

    Beagle is a carbon-copy of Apple's Spotlight, which I noted in my original post. As far as I can tell, inotify was added to the kernel for the explicit purpose of allowing something like this to be created.

    That being said, I cannot solicit Beagle, as much as it is a part of GNOME. First of all, it's written in C#, which I am against, but even averting that point, Beagle is slow, it's very, very buggy, and for some insane reason, they decided to go with Lucene as an Index server, instead of a fully qualified SQL server which could be connected through ODBC or any other database abstraction method.

    I've said these things before and been modified as troll, with people responding with "if you could do it better, do it yourself". Well, this isn't my capacity at this point in time; I'm simply observing and reporting on the product. I understand that it's deep in alpha right now, and I do have hope that it'll get better, but in the meantime, it's connection to C#, Lucene, and fundamental archetecture problems as to where the program is allowed to index makes me doubt it's future relevance.

    My point is that we need a database file system, but that Linux as a whole will be in last place to get one. Beagle is a good attempt, but I can't see it as anything more than a graduate project. I offered to port it to C++, a database agnostic implementation, and to add Kerberos/PAM support to it as my Google Summer-of-Code entry, but as I was declined, and because I do need to stay alive and eat, I can't just code it for free.

    --
    "Victory means exit strategy, and it's important for the President to explain to us what the exit strategy is." G.W.Bush
  13. AHEM by Ayanami+Rei · · Score: 2, Insightful

    You still need an indexing service.
    All that metadata isn't just going to poof out of the thin air. Metadata where it gets entered (save dialog in office, ID3 tags, thumbnails on pictures, etc.) needs to find it's way into this API, or it needs to be programmatically extracted by background processes.

    I actually like the latter, it takes the burden off the applications.

    Also, it'd be nice if concepts like the "Recently Used Files" and stuff like that gets rolled into it (that is, recently used is just a metadata field and the RUF directory is a "view" or "Select" against the database with appropriate criteria).

    It's too bad WinFS isn't a real database-backed file store. Because then you could do all sorts of weird stuff... (and it's easy enough to provide a compatibility layer for a hierarchical-filesystem-assuming Win32 API)

    --
    THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
    1. Re:AHEM by PsychicX · · Score: 2, Insightful

      Here's the thing that bothers me. I have MSN Desktop Search right here, which is constructed on top of Windows Indexing Service and does a marvelous job of finding files based on metadata and contents (as good or better than GDS, I think). The only drawback I see is the indexing process, which in MSN is very efficient, both in terms of time taken as well as hard drive space consumed. My question is, what does the WinFS offer me that MSN Desktop Search doesn't already?

  14. Re:A Complete And Utter Joke by Anonymous Coward · · Score: 4, Insightful

    I worked at MS on filesystems for a dozen years, and I totally agree with you. WinFS has been kicked around (and cancelled) since OS/2 days at Microsoft. Its a conflation of abstractions that needlessly complicate the data-structure of the file system. System recovery will probably be completely impossible in WinFS. And it can only slow down the system. And what does it buy the user? Faster file search. Except it will be beyond most users comprehension; a recipe for disaster rivalled only by the registry.

  15. Re:And ... by GeorgeMcBay · · Score: 5, Insightful


    Someone will probably have at least partial support for it before it ever even gets out of beta.


    And then it will stay only partially supported for 10+ years, just like the NTFS support.

  16. Re:Don't forget DRM. by Anonymous Coward · · Score: 1, Insightful

    From reading all that, it seems that it won't yet use trusted computing hardware to provide those DRM functions. Which will make them breakable.

    NGSCB will come into full swing post-Vista.

    Anyway, I sure as hell hope the Mac doesn't go that way. Of course, if web sites start refusing access without remote atestation certificates (that are immensly difficult to forge), then the Mac may have to adapt or die.

    The Remote Atestation feature seems to be the most worrying. It will become very difficult to lie to other machines about what software you're running.

    Not to mention, if say, MS Word decides that it is the only program authorised to read .doc files on your computer. How the hell are you supposed to move to third party office suites?

  17. Re:Is Linux Trailing? by Lost+Found · · Score: 2, Insightful

    Hans... I use your wonderful reiser3 filesystem. I really do support your innovations and hope that a happy medium can be met with the guys at LKML (I do understand their concerns).

    When I first read about Reiser4, I knew immediately that it would blow the pants off all competition. Please don't stop innovating -- even if getting Reiser4 merged is a long battle, I think it's going to be better for computing and humanity as a whole.

  18. Re:Is Linux Trailing? by team99parody · · Score: 3, Insightful
    adding semantic enhancements to Linux namespaces is mixed at best......If the filesystems were free to compete in semantics, we could have one or several of the Linux filesystems leading them instead.

    I could not agree more. I would very much like to see more advances/innovation/inventions out the F/OSS, and here's a place where it has happened but apparently is at the risk of stagnating.

    Is there a recommended place (hopefully one of the big distros) where we can get a kernel that supports the hooks you need?

    Personally, I'd speculate that these benefits would be a nice point of differentiation for one of the commercial distros; and its proven success in that environment could be a big motivation for the kernel to approve the changes.

  19. Re:Is Linux Trailing? by diegocgteleline.es · · Score: 2, Insightful

    Notice that linux kernel developers haven't neccesarily opposed to reiser 4 ideas, but how they have been implemented. Hell, Linus even likes the "files-as-directories" thing, a idea which makes many UNIX zealots vomit...

    The problem with reiser 4 being merged (as I've seen it in the flam^Wdiscussions) is that they seem to implement things that should be implemented at VFS level, not in the reiser 4 code like they're doing now. It's that what is stopping reiser 4 from being merged, not the "ideas" themselves. Some people don't like reiser 4 ideas, but as long as they're not forced to use them and the features are well implemented they won't oppose to it.

  20. Rob Pike's opinion by diegocgteleline.es · · Score: 2, Insightful

    From Rob Pike's slashdot interview:

    5) Database filesystems - by defile The buzz around filesystems research nowadays is making the UNIX filesystem more database-ish. The buzz around database research nowadays is making the relational database more OOP-ish.

    This research to me sounds like the original designers growing tired of the limitations of their "creations" now that they're commodities and going back to the drawing board to "do things right this time". I predict the reinvented versions will never catch on because they'll be too complex and inaccessible.

    Of course, this second system syndrome isn't just limited to systems. It happens to bands, directors, probably in every creative art.

    I think what we've got in the modern filesystem and RDBMS is about as good as it gets and we should move on. What do you think?

    Pike: " This is not the first time databases and file systems have collided, merged, argued, and split up, and it won't be the last. The specifics of whether you have a file system or a database is a rather dull semantic dispute, a contest to see who's got the best technology, rigged in a way that neither side wins. Well, as with most technologies, the solution depends on the problem; there is no single right answer.

    What's really interesting is how you think about accessing your data. File systems and databases provide different ways of organizing data to help find structure and meaning in what you've stored, but they're not the only approaches possible. Moreover, the structure they provide is really for one purpose: to simplify accessing it. Once you realize it's the access, not the structure, that matters, the whole debate changes character.

    One of the big insights in the last few years, through work by the internet search engines but also tools like Udi Manber's glimpse, is that data with no meaningful structure can still be very powerful if the tools to help you search the data are good. In fact, structure can be bad if the structure you have doesn't fit the problem you're trying to solve today, regardless of how well it fit the problem you were solving yesterday. So I don't much care any more how my data is stored; what matters is how to retrieve the relevant pieces when I need them.

    Grep was the definitive Unix tool early on; now we have tools that could be characterized as `grep my machine' and `grep the Internet'. GMail, Google's mail product, takes that idea and applies it to mail: don't bother organizing your mail messages; just put them away for searching later. It's quite liberating if you can let go your old file-and-folder-oriented mentality. Expect more liberation as searching replaces structure as the way to handle data.