Slashdot Mirror
Tom's Hardware Looks At WinFS
Alizarin Erythrosin writes "Tom's Hardware Guide has an article about the new WinFS file system. The article talks first about some of the problems and advantages with FAT[16|32] and NTFS, then talks briefly about WinFS. Here is the summary: 'Microsoft is breaking new ground with Longhorn, successor to XP. The upcoming WinFS file system will be the first to be context-dependent, and promises to make long search times and wasted memory a thing of the past. Today, THG compares it to FAT and NTFS.' Personally, I still have reservations about using a relational database to keep track of files. Unless they can keep the overhead to a minimum, I can't see it being as efficient as a file system should be."
1st posty you homos!
This article is bullshit. There isn't a shred of new information in it. It's like watching CNN.
In Soviet America the banks rob you!
Since the release date for Longhorn's supposed to be 2005 (last time I looked, anyway), the minimum specs will probably be something like a RAID-0 array of 5 15000rpm disks, running on double-speed SATA.
[SARCASM] I'm sure it'll perform at least as well as FAT16. [/SARCASM]
That WinFS version 2 will be twice as inefficient as version 1. And so forth for subsequent versions. Maybe I'll even get a paperclip to help me manage my files!!! Yeah!!! That'd be the shit!!!!:)
Heh..at lesat MS SQL is 100 times better than MySQL, which crashes all the time with PHP and I just can't deal with MySQL anymore!!!
10 bucks says that after 6 months of making fun of this filesystem, Linux "me-too"-ism will suddenly cause Linux to suddenly start support "LinFS", which will be a database-driven type of file system. Hey, Lunis Torbalds is working full time on the source now... maybe he can do it?
The recovery characteristics of NFTS deserve special mention: Windows records in real time all modifications to the file system with checkpoints that it then uses to background-correct system errors in the event of a forced reboot.
Why are Linux filesystems still shit?
Important Stuff: Please try to keep cock in mouth. Try to attend to other people's cocks only when finished with mine. Suck other people's cocks before massaging your own to avoid simply exacerbating what has already been rubbed to rash. Use a clear lubricant that softens your anus within and without. Undersized, Inflamed, Inadequate, Artificial, or Festering cocks should still be be welcomed as that's all the sex you'll ever get. (You can suck everything, even ulcerated cocks, by adjusting your rectal pore with a shoe horn) If you want reciprocation to your cocksucking made to you, consider sucking cock somewhere where you are not regarded as dumbass biatch.
Why doesn't Microsoft adopt an open standard like ReiserFS, JFS, or XFS?
1. Cause Microsoft customers don't like losing data.
2. Hans Reiser is a dirty, dirty Kraut.
What a surprise, it is the microsoft indexer that "actually works"!
It is basically (from my point of view) a meta-data database that actaully points at the files instead of descriptors to files!! What a concept..
Realistically, if I am reading this right, it is JUST a further abstraction for 'beginners' and those that just don't care about computers or how they work. It has 0% usability / performance / availability gains by the looks of it. It is simply to make ignorant users navigation of the systems easier.
Bye!
what WinFS means.
Windows FUCKED SYSTEM..
No rocket science here Sparky..
Yeah, I'm a Linux Zealot. And I love it baby!
I'm not much of a hardware guy, but it seems like you could work this out if you had a small (50MB?) partition whose filesystem was something "known" and "simple" (FAT32? NTFS? FAT?) that lived on the boot disk. This partition could contain a boot image of a trimmed-down version of enough of the OS to just read that DB and mount/expose partitions where ever needed in order to go into "rescue" mode. I'm thinking of something like Linux's initrd preliminary root file system image for SCSI and such, with added stuff.
That would work well enough, especially if you had some bare-bones framebuffer GUI that let you view and fix partitions, use a USB mouse/keyboard, tools to move files in/out of ramdisks, etc. It could get the creature feep something fierce, but you could easily draw the line at like 100MB of compressed image data and still come away with enough tools to recover data. You could also stick all this on a bootable rescue CD (although I'd be pissed if I had to tote around a CD in order to recover from a crash).
-B
Ash and Hickory, straight-grained and true, make excellent bludgeons, dandy for the cudgeling of vegetarians.
http://saveie6.com/
T
H
A
N
T H A N
That was classic intercourse!