If you have a dual-boot setup, putting shared data (music/video collection, VM disk images, etc.) on NTFS makes it readily accessible from both Windows and Linux. NTFS is also commonly used on large external HDDs for similar reasons.Quote:
Originally Posted by droidhacker
Microsoft actually had the balls to try to put a microkernel into production. NT, for very early versions, actually had a microkernel. But they figured out why Linus was right and abandoned that design.
They may retain some 'microkernel'-isms here and there, but they are not Microkernels by any stretch of the imagination.
This is a good thing as Microkernels are much larger, much more complex, and much slower then monolythic.
The alternative would be to install an ext4-capable driver on Windows. The problem with that is the only existing ext* driver on Windows only supports up to ext3, and you can't use any of the ext4 features that break the on-disk format if you want to use that driver. Other than being essentially stuck mounting my volumes as ext3, the Windows driver further has the disadvantage of having a much smaller user community and therefore less testing and a higher likelihood of breaking. Plus, I don't entirely trust third party kernel modules on my Windows box: having a "built-in" NTFS driver on Windows, and a "built-in" officially supported ntfs-3g on a Linux distro is the safer bet. And if ntfs-3g has a problem you can fall back on your distro to support it (and maybe even fix it -- it's open source!), assuming that it's in the `main' repository.
I've even used ntfsfix to un-bork an NTFS volume that wound up in a nasty state due to power failure or a BSOD while running Windows. I hear it causes fragmentation and doesn't do as good of a job at recovering things as Microsoft's chkdsk, but I haven't lost any data because of it.
Basically ntfs-3g is fast enough for me, and it's most certainly stable enough. I use it continuously via Rhythmbox for playing music on the Linux side, and I have the volume in my /etc/fstab. And sometimes I do large data writes (>1GB) through it with no ill side effects.
Of course I do own a professional copy of DiskKeeper on the Windows side, which I use to De-Frag the NTFS volume, to keep the performance steady. This is the only downside I see to using NTFS as my cross-platform filesystem for files that need to be available both for Windows and Linux. My only other viable alternative is FAT32, which is universally supported, but the data integrity there is pathetic because there's no journal, so... not happening. :)
That said, there are plenty of other good reasons not to use FAT32.
While it may be awesome, fixing the regular crashes would seem like a better idea than trying to work around them in this way.