Windows Alternatives to NTFS? 140
Maidjeurtam asks: "I'm a multi-OS user. Although Linux is what I use the most these days (I run it on my primary P4 box and on my iBook), I also run Mac OS X and a Windows XP on other machines. Of course, those boxes are networked, but sometimes, I just prefer to plug one machine's hard disk into another. I often work with big DV files (> 4GiB) and it looks like I have no other choice than having a different filesystem on each of my boxes. Granted, Linux can read NTFS (Macs can too) and even write to NTFS partitions thanks to tools like Captive, but I don't like the idea of running Windows code on my Linux box. In fact, I don't want my data stored on a proprietary, closed filesystem. I've googled a bit and it seems there's no modern (free-as-in-speech) filesystem I can install on Windows. I'd love to have ReiserFS running on my XP box, for example. Am I condemned to stay with NTFS, or do you guys know of a Windows-compatible, open filesystem that I can use?"
Why doesn't somebody write one? (Score:3, Interesting)
A while ago I downloaded the Windows DDK from Microsoft for something, but I didn't end up using it, uninstalled it and now I can't find the download. Unfortunately, it doesn't seem avail. for free from Microsoft's site anymore either (Microsoft WHDC DDK page [microsoft.com]). I have work to do, but this page seems like it might be of some help: OSROnline.com [osronline.com]... maybe.
Anyways, the idea still stands, why aren't there win32 branches of open source file system drivers? Of course, I know squat about writing drivers, especially filesystem drivers, so there may be a damn good reason why not. But figured I'd throw it out anywho.
Re:Give me a break... (Score:4, Interesting)
2) The poster, as you so unusefully point out, is aware of read access under Mac OS X and Linux, and is perfectly aware that he doesn't have an _access_ problem per se. He does, however, have an _access_ problem in that he can only write from one side. If he needs to write from the other he needs to move the files off box.
3) Apparently you're reading things the rest of us aren't. The poster is not complaining about things just because they're proprietary. What he is asking is if there is a way to do what he wants to do. You fail miserably to even address his issue in your brief rant.
To the moderator or called you 'insightful'. Stop smoking crack, it makes you feed the trolls.
-T
Suck my Karma Bonus.
Probably not (Score:4, Interesting)
Fortunately for you, MS does have a filesystem-abstraction mechanism known as SMB, which several projects (most notably the SAMBA project) have implemented. These systems communicate with Windows via SMB, presenting information to the OS with parameters it understands. By proxy, then, the MS OS doesn't care a whit about what back end FS it's writing to - as far as it's concerned, it's just like any other MS OS via the network.
So probably the best solution is to have a network-mounted drive connected via a high-speed link (gigabit ethernet, etc.) on a linux box running SMB. If you do it right, you should hopefully have enough bandwidth to do your video and have it hosted wherever you like.
Good luck!
Re:File size (Score:3, Interesting)
You *CAN* and *DO* create FAT32 partitions larger than 32Gb in various revisions of Windows. The largest one I have created, using Microsoft's own Windows Installer, was 200Gb. However, there are many revisions that have an added 'feature' which removes this ability. The Win2k OEM CD that came with my laptop, for instance, refuses. Yet my friend's Win2k CD happily creates FAT32 partitions as big as you like.
hey you got it! (Score:3, Interesting)
You might have just hit it.
The issue with wanting everthing OSS on windows is that it makes migration easier. Almost every company has 1 or 2 apps that have to be on windows...so the key is replacing one-at-a-time...mozilla here, openoffice.org there... It's a page right out of the MS playbook...cooperate with everything and quietly switch user bases. But with OSS you won't ever be FORCED to switch and pay more money!!!
Maybe I'm the only one who noticed... (Score:5, Interesting)
For good reason I'd say, I've been using NTFS write support for the past several revisions without a single hiccup.
First I was cautious and ginger in my handling of NTFS writes, and then more bold. Now I don't consider corruption anymore than I would with windows. I guess that comes from hundreds if not thousands of writes without a single issue *shrugs*.
In any case, if the kernel maintainers think it's safe to take off the experimental tag, and I've used it without any problems. Maybe it'll go well for you too.
NTFS write used to be horrid, and required external cleanup utils just to use. That's long long gone, if you've been afraid to touch it because of being burned in the past, seriously, it's time to try again.
Re:Why doesn't somebody write one? (Score:2, Interesting)
I've been using NTFS write support for the past several versions.
I don't know if people assume NTFS doesn't work on linux because distro's don't generally include it in their kernel builds or because the write support was horrid and corrupted filesystems once upon a time.