<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_12_23_2229226</id>
	<title>Best Filesystem For External Back-Up Drives?</title>
	<author>timothy</author>
	<datestamp>1261565700000</datestamp>
	<htmltext>rufey writes <i>"I've recently embarked on a project to rip my DVD and CD collection to a pair of external USB drives.  One drive will be used on a daily basis to access the rips of music and DVDs, as well as store backups of all of my other data.   The second drive will be a copy of the first drive, to be synced up on a monthly basis and kept at a different location.  The USB drives that I purchased for this are 1 TB in size and came pre-formatted with FAT32.  While I can access this filesystem from all of my Windows and Linux machines, there are some limitations."</i> Read on for the rest, and offer your advice on the best filesystem for this application.</htmltext>
<tokenext>rufey writes " I 've recently embarked on a project to rip my DVD and CD collection to a pair of external USB drives .
One drive will be used on a daily basis to access the rips of music and DVDs , as well as store backups of all of my other data .
The second drive will be a copy of the first drive , to be synced up on a monthly basis and kept at a different location .
The USB drives that I purchased for this are 1 TB in size and came pre-formatted with FAT32 .
While I can access this filesystem from all of my Windows and Linux machines , there are some limitations .
" Read on for the rest , and offer your advice on the best filesystem for this application .</tokentext>
<sentencetext>rufey writes "I've recently embarked on a project to rip my DVD and CD collection to a pair of external USB drives.
One drive will be used on a daily basis to access the rips of music and DVDs, as well as store backups of all of my other data.
The second drive will be a copy of the first drive, to be synced up on a monthly basis and kept at a different location.
The USB drives that I purchased for this are 1 TB in size and came pre-formatted with FAT32.
While I can access this filesystem from all of my Windows and Linux machines, there are some limitations.
" Read on for the rest, and offer your advice on the best filesystem for this application.</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30553798</id>
	<title>Re:ZFS, supported equally on your OSes</title>
	<author>Anonymous</author>
	<datestamp>1261755000000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Had the exact opposite problem with bsd to solaris. I was an idiot forgot the export command. To wit: Solaris and BSD use different naming conventions.<nobr> <wbr></nobr>/dev/sda etc vs c8d1. Although in retrospect, I wonder if symlinks would have helped with this? Unfortunately I could never find a way to manually edit the vdev and change the device locations.</p><p>I eventually, in a fit of rage nuked the bloody thing. Realizing only later that there was some 300GB of data that I had shifted to the nas and then deleted from the source systems.<nobr> <wbr></nobr>:-(</p></htmltext>
<tokenext>Had the exact opposite problem with bsd to solaris .
I was an idiot forgot the export command .
To wit : Solaris and BSD use different naming conventions .
/dev/sda etc vs c8d1 .
Although in retrospect , I wonder if symlinks would have helped with this ?
Unfortunately I could never find a way to manually edit the vdev and change the device locations.I eventually , in a fit of rage nuked the bloody thing .
Realizing only later that there was some 300GB of data that I had shifted to the nas and then deleted from the source systems .
: - (</tokentext>
<sentencetext>Had the exact opposite problem with bsd to solaris.
I was an idiot forgot the export command.
To wit: Solaris and BSD use different naming conventions.
/dev/sda etc vs c8d1.
Although in retrospect, I wonder if symlinks would have helped with this?
Unfortunately I could never find a way to manually edit the vdev and change the device locations.I eventually, in a fit of rage nuked the bloody thing.
Realizing only later that there was some 300GB of data that I had shifted to the nas and then deleted from the source systems.
:-(</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540158</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542350</id>
	<title>Re:NTFS</title>
	<author>westyvw</author>
	<datestamp>1261685700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Seriously? NTFS (Nice Try at a File System)? I think I will pass on the defragging, thanks.</p></htmltext>
<tokenext>Seriously ?
NTFS ( Nice Try at a File System ) ?
I think I will pass on the defragging , thanks .</tokentext>
<sentencetext>Seriously?
NTFS (Nice Try at a File System)?
I think I will pass on the defragging, thanks.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539930</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540242</id>
	<title>Replace the WD TV thing</title>
	<author>NitroWolf</author>
	<datestamp>1259758140000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>Replace the silly little WD TV Live media player with a mITX system that's about the same size.  Install Linux and XBMC and be done with it.  You'll have the best possible media player on the planet, as much storage space in any configuration you want and the ability to expand everything when the time comes.  No hassle, you'll have constant online backups available and you'll have a killer always-on media center.</p></htmltext>
<tokenext>Replace the silly little WD TV Live media player with a mITX system that 's about the same size .
Install Linux and XBMC and be done with it .
You 'll have the best possible media player on the planet , as much storage space in any configuration you want and the ability to expand everything when the time comes .
No hassle , you 'll have constant online backups available and you 'll have a killer always-on media center .</tokentext>
<sentencetext>Replace the silly little WD TV Live media player with a mITX system that's about the same size.
Install Linux and XBMC and be done with it.
You'll have the best possible media player on the planet, as much storage space in any configuration you want and the ability to expand everything when the time comes.
No hassle, you'll have constant online backups available and you'll have a killer always-on media center.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30549650</id>
	<title>Re:I wouldn't....</title>
	<author>sammcj</author>
	<datestamp>1261771980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I had MAJOR performance issues with FreeNAS.

I spent 3 months testing it at home for work use, tried it on 3 different half decent machines.
After [x] number of days each box's network transfers would slow down to the crawl, logged several faults with the FreeNAS team and it looks like it was a problem with the BSD Kernel and Samba (Combo known for bad performance).
I shifted to Ubuntu Server x64 and haven't turned back, bloody brilliant especially after you install Webmin.</htmltext>
<tokenext>I had MAJOR performance issues with FreeNAS .
I spent 3 months testing it at home for work use , tried it on 3 different half decent machines .
After [ x ] number of days each box 's network transfers would slow down to the crawl , logged several faults with the FreeNAS team and it looks like it was a problem with the BSD Kernel and Samba ( Combo known for bad performance ) .
I shifted to Ubuntu Server x64 and have n't turned back , bloody brilliant especially after you install Webmin .</tokentext>
<sentencetext>I had MAJOR performance issues with FreeNAS.
I spent 3 months testing it at home for work use, tried it on 3 different half decent machines.
After [x] number of days each box's network transfers would slow down to the crawl, logged several faults with the FreeNAS team and it looks like it was a problem with the BSD Kernel and Samba (Combo known for bad performance).
I shifted to Ubuntu Server x64 and haven't turned back, bloody brilliant especially after you install Webmin.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539912</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539912</id>
	<title>I wouldn't....</title>
	<author>fak3r</author>
	<datestamp>1259755800000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext>I wouldn't limit myself to a certain filesystem, I'd run a dedicated NAS like FreeNAS and share it over the network via SMB (windows), AFP (apple) and whatever for Linux - all set.  Plus as mentioned above, you can run Firefly media server, a bittorrent server, a DAAP server (itunes sharing), etc (all included in FreeNAS.  <a href="http://freenas.org/" title="freenas.org">http://freenas.org/</a> [freenas.org]) on the same box.

And since filesystems don't matter in this config, you can use ZFS to make a RAIDZ pool of your drives.  It's what I do now.</htmltext>
<tokenext>I would n't limit myself to a certain filesystem , I 'd run a dedicated NAS like FreeNAS and share it over the network via SMB ( windows ) , AFP ( apple ) and whatever for Linux - all set .
Plus as mentioned above , you can run Firefly media server , a bittorrent server , a DAAP server ( itunes sharing ) , etc ( all included in FreeNAS .
http : //freenas.org/ [ freenas.org ] ) on the same box .
And since filesystems do n't matter in this config , you can use ZFS to make a RAIDZ pool of your drives .
It 's what I do now .</tokentext>
<sentencetext>I wouldn't limit myself to a certain filesystem, I'd run a dedicated NAS like FreeNAS and share it over the network via SMB (windows), AFP (apple) and whatever for Linux - all set.
Plus as mentioned above, you can run Firefly media server, a bittorrent server, a DAAP server (itunes sharing), etc (all included in FreeNAS.
http://freenas.org/ [freenas.org]) on the same box.
And since filesystems don't matter in this config, you can use ZFS to make a RAIDZ pool of your drives.
It's what I do now.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30548652</id>
	<title>Re:Please read this</title>
	<author>Anonymous</author>
	<datestamp>1261668660000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>I made a small, few-sector long 200 MB FAT-32 partition to the beginning of the drive and downloaded all the latest Win32 EXT2 drivers there from different vendors, just for the really unplausible situation that I would ever want to mount these drives in Windows. Then I just made the rest Ext3...</p></div><p>Yes! I do this all the time on my big external USB HDD.</p></div>
	</htmltext>
<tokenext>I made a small , few-sector long 200 MB FAT-32 partition to the beginning of the drive and downloaded all the latest Win32 EXT2 drivers there from different vendors , just for the really unplausible situation that I would ever want to mount these drives in Windows .
Then I just made the rest Ext3...Yes !
I do this all the time on my big external USB HDD .</tokentext>
<sentencetext>I made a small, few-sector long 200 MB FAT-32 partition to the beginning of the drive and downloaded all the latest Win32 EXT2 drivers there from different vendors, just for the really unplausible situation that I would ever want to mount these drives in Windows.
Then I just made the rest Ext3...Yes!
I do this all the time on my big external USB HDD.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541114</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30544238</id>
	<title>Historical day.</title>
	<author>Anonymous</author>
	<datestamp>1261672620000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Today, after what -- 10 years being here? -- I got my first -1 for pointing NTFS in encumbered... and nobody cared.</p><p>That's normal everywhere... except here on<nobr> <wbr></nobr>/.</p><p>Today IMHO -- after a long descent --<nobr> <wbr></nobr>/. went under the sea level.</p><p>Shall I perhaps register? (rhetorical)</p></htmltext>
<tokenext>Today , after what -- 10 years being here ?
-- I got my first -1 for pointing NTFS in encumbered... and nobody cared.That 's normal everywhere... except here on /.Today IMHO -- after a long descent -- / .
went under the sea level.Shall I perhaps register ?
( rhetorical )</tokentext>
<sentencetext>Today, after what -- 10 years being here?
-- I got my first -1 for pointing NTFS in encumbered... and nobody cared.That's normal everywhere... except here on /.Today IMHO -- after a long descent -- /.
went under the sea level.Shall I perhaps register?
(rhetorical)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540456</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539936</id>
	<title>Re:The solution..</title>
	<author>Anrego</author>
	<datestamp>1259755860000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>There isn't one.. it's basically like irrespective</p><p>Which is why I use it.. I have a gene that compels me to torture tech writers.. tis also the reason I use these half hearted ellipsis..</p></htmltext>
<tokenext>There is n't one.. it 's basically like irrespectiveWhich is why I use it.. I have a gene that compels me to torture tech writers.. t is also the reason I use these half hearted ellipsis. .</tokentext>
<sentencetext>There isn't one.. it's basically like irrespectiveWhich is why I use it.. I have a gene that compels me to torture tech writers.. tis also the reason I use these half hearted ellipsis..</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539858</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540942</id>
	<title>turn your usb drive into a NAS</title>
	<author>stilldead</author>
	<datestamp>1259763960000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>I haven't tried it but it looks like a good idea. <a href="http://www.cyberguys.com/product-details/?productid=36218&amp;sk=MC71419" title="cyberguys.com" rel="nofollow">http://www.cyberguys.com/product-details/?productid=36218&amp;sk=MC71419</a> [cyberguys.com]<br>Format it ext3 and then share it SMB for any OS.</p></htmltext>
<tokenext>I have n't tried it but it looks like a good idea .
http : //www.cyberguys.com/product-details/ ? productid = 36218&amp;sk = MC71419 [ cyberguys.com ] Format it ext3 and then share it SMB for any OS .</tokentext>
<sentencetext>I haven't tried it but it looks like a good idea.
http://www.cyberguys.com/product-details/?productid=36218&amp;sk=MC71419 [cyberguys.com]Format it ext3 and then share it SMB for any OS.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542100</id>
	<title>Re:The best is...</title>
	<author>the\_womble</author>
	<datestamp>1259780640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>its not something you want to be locked into.</p><p><a href="http://www2.mandriva.com/linux/overview/" title="mandriva.com">http://www2.mandriva.com/linux/overview/</a> [mandriva.com]</p><p>In addition, the Mandriva Control Centre is very good, the community is friendly, multiple desktop environments are properly supported (no Kubuntu style underfunded support), the repos are fairly big (but smaller than Debian/Ubuntu) and bug fixes usually happen fast.</p></htmltext>
<tokenext>its not something you want to be locked into.http : //www2.mandriva.com/linux/overview/ [ mandriva.com ] In addition , the Mandriva Control Centre is very good , the community is friendly , multiple desktop environments are properly supported ( no Kubuntu style underfunded support ) , the repos are fairly big ( but smaller than Debian/Ubuntu ) and bug fixes usually happen fast .</tokentext>
<sentencetext>its not something you want to be locked into.http://www2.mandriva.com/linux/overview/ [mandriva.com]In addition, the Mandriva Control Centre is very good, the community is friendly, multiple desktop environments are properly supported (no Kubuntu style underfunded support), the repos are fairly big (but smaller than Debian/Ubuntu) and bug fixes usually happen fast.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540138</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539946</id>
	<title>My setup is similar</title>
	<author>MichaelSmith</author>
	<datestamp>1259755980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I backup to portable USB hard disks. My backup machine is my eeepc 701. It runs ubuntu. I use this machine because it has fast USB and wifi interfaces. I have written a short shell script which runs on the eeepc. It uses rsync through ssh to copy user data from all the machines in the house to the external disk. I ignore the single windows machine in the house. If its user wants it backed up they can store their files on the server.</p><p>I initially tried backing up through a workstation runing netbsd but I found the USB interface to be too slow, by many orders of magnitude.</p></htmltext>
<tokenext>I backup to portable USB hard disks .
My backup machine is my eeepc 701 .
It runs ubuntu .
I use this machine because it has fast USB and wifi interfaces .
I have written a short shell script which runs on the eeepc .
It uses rsync through ssh to copy user data from all the machines in the house to the external disk .
I ignore the single windows machine in the house .
If its user wants it backed up they can store their files on the server.I initially tried backing up through a workstation runing netbsd but I found the USB interface to be too slow , by many orders of magnitude .</tokentext>
<sentencetext>I backup to portable USB hard disks.
My backup machine is my eeepc 701.
It runs ubuntu.
I use this machine because it has fast USB and wifi interfaces.
I have written a short shell script which runs on the eeepc.
It uses rsync through ssh to copy user data from all the machines in the house to the external disk.
I ignore the single windows machine in the house.
If its user wants it backed up they can store their files on the server.I initially tried backing up through a workstation runing netbsd but I found the USB interface to be too slow, by many orders of magnitude.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540568</id>
	<title>Windows Filesystem Support</title>
	<author>devent</author>
	<datestamp>1259760540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Why is the Windows's state of support third party file systems so bad anyway? Why does the Linux kernel supports so many file systems and Windows basically only fat32 and ntfs?</p><p>I thought because the ABI of the Windows kernel is stable it is so easy to develop drivers for it.</p><p>Oh and while am at it, when Windows will have LVM2 support? I can resize every partition on my Laptop as I wish, only the Windows partition is a static block (a too large block, btw, unable to be resized and used where the space is needed).</p></htmltext>
<tokenext>Why is the Windows 's state of support third party file systems so bad anyway ?
Why does the Linux kernel supports so many file systems and Windows basically only fat32 and ntfs ? I thought because the ABI of the Windows kernel is stable it is so easy to develop drivers for it.Oh and while am at it , when Windows will have LVM2 support ?
I can resize every partition on my Laptop as I wish , only the Windows partition is a static block ( a too large block , btw , unable to be resized and used where the space is needed ) .</tokentext>
<sentencetext>Why is the Windows's state of support third party file systems so bad anyway?
Why does the Linux kernel supports so many file systems and Windows basically only fat32 and ntfs?I thought because the ABI of the Windows kernel is stable it is so easy to develop drivers for it.Oh and while am at it, when Windows will have LVM2 support?
I can resize every partition on my Laptop as I wish, only the Windows partition is a static block (a too large block, btw, unable to be resized and used where the space is needed).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540634</id>
	<title>Re:Words of caution</title>
	<author>Anonymous</author>
	<datestamp>1259761020000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>You realize that XP has a feature allowing you to enable and disable write caching on each disk individually, right?  And that removable disks have write caching disabled by default?  Even OS X doesn't do that. (I'm not going to get into linux)</p></htmltext>
<tokenext>You realize that XP has a feature allowing you to enable and disable write caching on each disk individually , right ?
And that removable disks have write caching disabled by default ?
Even OS X does n't do that .
( I 'm not going to get into linux )</tokentext>
<sentencetext>You realize that XP has a feature allowing you to enable and disable write caching on each disk individually, right?
And that removable disks have write caching disabled by default?
Even OS X doesn't do that.
(I'm not going to get into linux)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540370</id>
	<title>Openfiler anyone?</title>
	<author>lacourem</author>
	<datestamp>1259759040000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>Personally I like Openfiler.  It can be picky about the hardware though.  With that said, the speed is great, and I can mount iscsi on linux and windows.  Has been stable as hell for me to boot.</htmltext>
<tokenext>Personally I like Openfiler .
It can be picky about the hardware though .
With that said , the speed is great , and I can mount iscsi on linux and windows .
Has been stable as hell for me to boot .</tokentext>
<sentencetext>Personally I like Openfiler.
It can be picky about the hardware though.
With that said, the speed is great, and I can mount iscsi on linux and windows.
Has been stable as hell for me to boot.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541524</id>
	<title>Re:Words of caution</title>
	<author>Anonymous</author>
	<datestamp>1259771580000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I remember there being a way to turn off delayed write for a device, or maybe it was the ability to turn it off for everything. Hmmm, maybe it was a registry trick to make it system wide, but it seems you can turn off delayed writes under the device manager. Select a storage device and get into it's properties. Then select the policies tab. There select the  "Optimize for quick removal" option. Once set it may require that you reboot. I just checked it under Vista, but I remember this being part of XP. In a side note I wonder if this setting is retained after removal of the device. It would seem so, or at least that my Vista installation disables it by default for my thumb.</p><p>Hope it helps,</p><p>AC</p></htmltext>
<tokenext>I remember there being a way to turn off delayed write for a device , or maybe it was the ability to turn it off for everything .
Hmmm , maybe it was a registry trick to make it system wide , but it seems you can turn off delayed writes under the device manager .
Select a storage device and get into it 's properties .
Then select the policies tab .
There select the " Optimize for quick removal " option .
Once set it may require that you reboot .
I just checked it under Vista , but I remember this being part of XP .
In a side note I wonder if this setting is retained after removal of the device .
It would seem so , or at least that my Vista installation disables it by default for my thumb.Hope it helps,AC</tokentext>
<sentencetext>I remember there being a way to turn off delayed write for a device, or maybe it was the ability to turn it off for everything.
Hmmm, maybe it was a registry trick to make it system wide, but it seems you can turn off delayed writes under the device manager.
Select a storage device and get into it's properties.
Then select the policies tab.
There select the  "Optimize for quick removal" option.
Once set it may require that you reboot.
I just checked it under Vista, but I remember this being part of XP.
In a side note I wonder if this setting is retained after removal of the device.
It would seem so, or at least that my Vista installation disables it by default for my thumb.Hope it helps,AC</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540804</id>
	<title>ext3</title>
	<author>Anonymous</author>
	<datestamp>1259762580000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>I format my external USB drives to ext3.  Most of my machines are Linux anyway, and I can always plug the USB drive into my storage server and backup over Samba to any kind of drive supported by the storage server.</p><p>ext3 is pretty much stable and well understood.  It just works.  That's what I want for backup drives.</p><p>And my netbook has Ubuntu Linux on it, and ext3 performs well on the external USB drive there.  I haven't tested NTFS over FUSE on the netbook, but I wonder about CPU overhead on the little Atom chip: it might be a little bit slow.</p><p>If you want a drive you can take over to your friend's house, and your friend just runs Windows or a Mac, then by all means NTFS.</p><p>steveha</p></htmltext>
<tokenext>I format my external USB drives to ext3 .
Most of my machines are Linux anyway , and I can always plug the USB drive into my storage server and backup over Samba to any kind of drive supported by the storage server.ext3 is pretty much stable and well understood .
It just works .
That 's what I want for backup drives.And my netbook has Ubuntu Linux on it , and ext3 performs well on the external USB drive there .
I have n't tested NTFS over FUSE on the netbook , but I wonder about CPU overhead on the little Atom chip : it might be a little bit slow.If you want a drive you can take over to your friend 's house , and your friend just runs Windows or a Mac , then by all means NTFS.steveha</tokentext>
<sentencetext>I format my external USB drives to ext3.
Most of my machines are Linux anyway, and I can always plug the USB drive into my storage server and backup over Samba to any kind of drive supported by the storage server.ext3 is pretty much stable and well understood.
It just works.
That's what I want for backup drives.And my netbook has Ubuntu Linux on it, and ext3 performs well on the external USB drive there.
I haven't tested NTFS over FUSE on the netbook, but I wonder about CPU overhead on the little Atom chip: it might be a little bit slow.If you want a drive you can take over to your friend's house, and your friend just runs Windows or a Mac, then by all means NTFS.steveha</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540790</id>
	<title>NTFS-3G works fine</title>
	<author>SlightOverdose</author>
	<datestamp>1259762460000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>NTFS-3G, which should come standard in most distros, should be able to read and write NTFS perfectly. It's considered very stable.

That said, my personal solution to this problem was to use EXT2 and install EXT2IFS on my windows machines. I had a small FAT32 partition on the USB disk with the EXT2 driver installers for Windows and MacOS, so if I ever need to read it on another computer I don't have to download anything.</htmltext>
<tokenext>NTFS-3G , which should come standard in most distros , should be able to read and write NTFS perfectly .
It 's considered very stable .
That said , my personal solution to this problem was to use EXT2 and install EXT2IFS on my windows machines .
I had a small FAT32 partition on the USB disk with the EXT2 driver installers for Windows and MacOS , so if I ever need to read it on another computer I do n't have to download anything .</tokentext>
<sentencetext>NTFS-3G, which should come standard in most distros, should be able to read and write NTFS perfectly.
It's considered very stable.
That said, my personal solution to this problem was to use EXT2 and install EXT2IFS on my windows machines.
I had a small FAT32 partition on the USB disk with the EXT2 driver installers for Windows and MacOS, so if I ever need to read it on another computer I don't have to download anything.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540324</id>
	<title>Re: Turn off write caching!</title>
	<author>Anonymous</author>
	<datestamp>1259758680000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Make sure you have write cache disabled! There's even a warning in Windows that having write cache on will cause data loss in this kind of case. I have it off and I've never encountered this issue. It should be set to disabled by default.</p></htmltext>
<tokenext>Make sure you have write cache disabled !
There 's even a warning in Windows that having write cache on will cause data loss in this kind of case .
I have it off and I 've never encountered this issue .
It should be set to disabled by default .</tokentext>
<sentencetext>Make sure you have write cache disabled!
There's even a warning in Windows that having write cache on will cause data loss in this kind of case.
I have it off and I've never encountered this issue.
It should be set to disabled by default.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542672</id>
	<title>btrfs &amp; data checksums</title>
	<author>zerothink</author>
	<datestamp>1261650420000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>Great feature would be data chacksums - for media collection on drive, I would like to get warning if there is any data loss.

<a href="http://en.wikipedia.org/wiki/Btrfs" title="wikipedia.org" rel="nofollow">btrfs</a> [wikipedia.org] has this feature (between many others), when it is a bit more stable, than I will use it in similar scanario.</htmltext>
<tokenext>Great feature would be data chacksums - for media collection on drive , I would like to get warning if there is any data loss .
btrfs [ wikipedia.org ] has this feature ( between many others ) , when it is a bit more stable , than I will use it in similar scanario .</tokentext>
<sentencetext>Great feature would be data chacksums - for media collection on drive, I would like to get warning if there is any data loss.
btrfs [wikipedia.org] has this feature (between many others), when it is a bit more stable, than I will use it in similar scanario.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539882</id>
	<title>Fat32 and VLC</title>
	<author>caubert</author>
	<datestamp>1259755620000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext>VLC can play rar-compressed-splitted files beautifully, So 4GB is not a very big problem</htmltext>
<tokenext>VLC can play rar-compressed-splitted files beautifully , So 4GB is not a very big problem</tokentext>
<sentencetext>VLC can play rar-compressed-splitted files beautifully, So 4GB is not a very big problem</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541558</id>
	<title>Re:The best is...</title>
	<author>Anonymous</author>
	<datestamp>1259772120000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Shovel not included...</p></htmltext>
<tokenext>Shovel not included.. .</tokentext>
<sentencetext>Shovel not included...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539888</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30546180</id>
	<title>Re:Replace the WD TV thing</title>
	<author>Anonymous</author>
	<datestamp>1261685340000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>Replace the silly little WD TV Live media player with a mITX system that's about the same size.  Install Linux and XBMC and be done with it.  You'll have the best possible media player on the planet, as much storage space in any configuration you want and the ability to expand everything when the time comes.  No hassle, you'll have constant online backups available and you'll have a killer always-on media center.</p></div><p>what is MITX ?? no link??</p><p>a google gives many sites but none consistent with this thread</p></div>
	</htmltext>
<tokenext>Replace the silly little WD TV Live media player with a mITX system that 's about the same size .
Install Linux and XBMC and be done with it .
You 'll have the best possible media player on the planet , as much storage space in any configuration you want and the ability to expand everything when the time comes .
No hassle , you 'll have constant online backups available and you 'll have a killer always-on media center.what is MITX ? ?
no link ?
? a google gives many sites but none consistent with this thread</tokentext>
<sentencetext>Replace the silly little WD TV Live media player with a mITX system that's about the same size.
Install Linux and XBMC and be done with it.
You'll have the best possible media player on the planet, as much storage space in any configuration you want and the ability to expand everything when the time comes.
No hassle, you'll have constant online backups available and you'll have a killer always-on media center.what is MITX ??
no link?
?a google gives many sites but none consistent with this thread
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540242</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539974</id>
	<title>network it</title>
	<author>Sloppy</author>
	<datestamp>1259756100000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><blockquote><div><p>I realize that there will always be some compatibility problems with whatever I end up with.</p></div></blockquote><p>Not if you use a <em>network</em> filesystem, such as Samba and NFS for the Windows and MacOS machines.  Then on the Linux fileserver side, use whatever filesystem you want, and any OS can talk to that server.</p></div>
	</htmltext>
<tokenext>I realize that there will always be some compatibility problems with whatever I end up with.Not if you use a network filesystem , such as Samba and NFS for the Windows and MacOS machines .
Then on the Linux fileserver side , use whatever filesystem you want , and any OS can talk to that server .</tokentext>
<sentencetext>I realize that there will always be some compatibility problems with whatever I end up with.Not if you use a network filesystem, such as Samba and NFS for the Windows and MacOS machines.
Then on the Linux fileserver side, use whatever filesystem you want, and any OS can talk to that server.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540076</id>
	<title>Re:I wouldn't....</title>
	<author>careysb</author>
	<datestamp>1259756880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Earlier this year I was looking into NAS drives and on at least two of the manufacturers' product info, they mentioned that some files cannot be copied to their device, e.g. MP3s.

Anybody else encounter this?</htmltext>
<tokenext>Earlier this year I was looking into NAS drives and on at least two of the manufacturers ' product info , they mentioned that some files can not be copied to their device , e.g .
MP3s . Anybody else encounter this ?</tokentext>
<sentencetext>Earlier this year I was looking into NAS drives and on at least two of the manufacturers' product info, they mentioned that some files cannot be copied to their device, e.g.
MP3s.

Anybody else encounter this?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539912</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540688</id>
	<title>NTFS-3G vs. nfsmount</title>
	<author>hduff</author>
	<datestamp>1259761560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I've used NTFS-3G successfully.
<a href="http://www.tuxera.com/community/ntfs-3g-download/" title="tuxera.com" rel="nofollow">http://www.tuxera.com/community/ntfs-3g-download/</a> [tuxera.com] </p><p>

But the nfsmount people have this to say: "The ntfs-3g driver is an obsolete fork of ntfsmount. Use ntfsmount from ntfsprogs-2.0.0"</p><p>

<a href="http://www.linux-ntfs.org/doku.php?id=ntfsmount" title="linux-ntfs.org" rel="nofollow">http://www.linux-ntfs.org/doku.php?id=ntfsmount</a> [linux-ntfs.org] </p><p>

Who is correct???</p></htmltext>
<tokenext>I 've used NTFS-3G successfully .
http : //www.tuxera.com/community/ntfs-3g-download/ [ tuxera.com ] But the nfsmount people have this to say : " The ntfs-3g driver is an obsolete fork of ntfsmount .
Use ntfsmount from ntfsprogs-2.0.0 " http : //www.linux-ntfs.org/doku.php ? id = ntfsmount [ linux-ntfs.org ] Who is correct ? ?
?</tokentext>
<sentencetext>I've used NTFS-3G successfully.
http://www.tuxera.com/community/ntfs-3g-download/ [tuxera.com] 

But the nfsmount people have this to say: "The ntfs-3g driver is an obsolete fork of ntfsmount.
Use ntfsmount from ntfsprogs-2.0.0"

http://www.linux-ntfs.org/doku.php?id=ntfsmount [linux-ntfs.org] 

Who is correct??
?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542230</id>
	<title>Re:Words of caution</title>
	<author>Anonymous</author>
	<datestamp>1259782620000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>...just had this problem with w7 two days ago, whole disk was read-only after that, but only 15\% of the files survived. TestDisk helped, but it was a nightmare.</p></htmltext>
<tokenext>...just had this problem with w7 two days ago , whole disk was read-only after that , but only 15 \ % of the files survived .
TestDisk helped , but it was a nightmare .</tokentext>
<sentencetext>...just had this problem with w7 two days ago, whole disk was read-only after that, but only 15\% of the files survived.
TestDisk helped, but it was a nightmare.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540302</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540538</id>
	<title>DVD shouldn't be an issue</title>
	<author>DJRumpy</author>
	<datestamp>1259760240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Considering DVD files are typically split at the 1 GB mark, you should have no issues with DVD. Assuming you have other files that break the 4GB barrier however, leaves you with EXT3, HPFS, or NTFS. The EXT3 support for OS X is supposed to be there using the <a href="http://sourceforge.net/projects/ext2fsx/" title="sourceforge.net">SourceForge EXT2 driver</a> [sourceforge.net], but I never managed to get them to mount. NTFS support is good on the OS X side, seems to be good on Linux and of course on Windows.</p><p>I'd go with NTFS using NTFS-3G as it gives read/write support on all 3 OS's and is open source ( <a href="http://sourceforge.net/projects/ntfs-3g/" title="sourceforge.net">http://sourceforge.net/projects/ntfs-3g/</a> [sourceforge.net] )</p></htmltext>
<tokenext>Considering DVD files are typically split at the 1 GB mark , you should have no issues with DVD .
Assuming you have other files that break the 4GB barrier however , leaves you with EXT3 , HPFS , or NTFS .
The EXT3 support for OS X is supposed to be there using the SourceForge EXT2 driver [ sourceforge.net ] , but I never managed to get them to mount .
NTFS support is good on the OS X side , seems to be good on Linux and of course on Windows.I 'd go with NTFS using NTFS-3G as it gives read/write support on all 3 OS 's and is open source ( http : //sourceforge.net/projects/ntfs-3g/ [ sourceforge.net ] )</tokentext>
<sentencetext>Considering DVD files are typically split at the 1 GB mark, you should have no issues with DVD.
Assuming you have other files that break the 4GB barrier however, leaves you with EXT3, HPFS, or NTFS.
The EXT3 support for OS X is supposed to be there using the SourceForge EXT2 driver [sourceforge.net], but I never managed to get them to mount.
NTFS support is good on the OS X side, seems to be good on Linux and of course on Windows.I'd go with NTFS using NTFS-3G as it gives read/write support on all 3 OS's and is open source ( http://sourceforge.net/projects/ntfs-3g/ [sourceforge.net] )</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540524</id>
	<title>Re:The solution..</title>
	<author>Jeff Carr</author>
	<datestamp>1259760180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>It may be that he knew exactly what he was saying, and his sentence would have been the same irrespective of whether he used that first word or... that other word I can't quite remember.  Regardless, my point still stands.</htmltext>
<tokenext>It may be that he knew exactly what he was saying , and his sentence would have been the same irrespective of whether he used that first word or... that other word I ca n't quite remember .
Regardless , my point still stands .</tokentext>
<sentencetext>It may be that he knew exactly what he was saying, and his sentence would have been the same irrespective of whether he used that first word or... that other word I can't quite remember.
Regardless, my point still stands.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540130</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30543640</id>
	<title>No matter what FS you choose, do this</title>
	<author>NevarMore</author>
	<datestamp>1261668360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>My requirements weren't as stiff, but I found myself with an external drive that was used for offsite copying/sneakernet use between my *nix box, the wifes Mac, and friends Windows boxes.</p><p>I don't recall what FS was used, but it wasn't FAT or NTFS. I did set up a FAT partition with driver installer packages for that filesystem for most major OS's along with a README file with general instructions for mounting it on Windows and OS X and Ubuntu.</p><p>As long as there are tolerable drivers for any given OS, this gives the freedom to use the right filesystem for the task without sacrificing interoperability.</p></htmltext>
<tokenext>My requirements were n't as stiff , but I found myself with an external drive that was used for offsite copying/sneakernet use between my * nix box , the wifes Mac , and friends Windows boxes.I do n't recall what FS was used , but it was n't FAT or NTFS .
I did set up a FAT partition with driver installer packages for that filesystem for most major OS 's along with a README file with general instructions for mounting it on Windows and OS X and Ubuntu.As long as there are tolerable drivers for any given OS , this gives the freedom to use the right filesystem for the task without sacrificing interoperability .</tokentext>
<sentencetext>My requirements weren't as stiff, but I found myself with an external drive that was used for offsite copying/sneakernet use between my *nix box, the wifes Mac, and friends Windows boxes.I don't recall what FS was used, but it wasn't FAT or NTFS.
I did set up a FAT partition with driver installer packages for that filesystem for most major OS's along with a README file with general instructions for mounting it on Windows and OS X and Ubuntu.As long as there are tolerable drivers for any given OS, this gives the freedom to use the right filesystem for the task without sacrificing interoperability.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542070</id>
	<title>Use Linux + Samba for home network file sharing</title>
	<author>Anonymous</author>
	<datestamp>1259780100000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>I have a LOT of my DVD collection rip'd to my computer drives. I use 1.5GB esata hard drives formatted ext3 for Linux and have a linux file server running Samba so all my Linux, Mac, and Windows machines can access the ISO images (mount as virtual DVD's) from anywhere in the house. Works great, costs very little ($0.10 USD / GB == $0.40-0.90 / DVD), and can easily be copied to a laptop for travel.</htmltext>
<tokenext>I have a LOT of my DVD collection rip 'd to my computer drives .
I use 1.5GB esata hard drives formatted ext3 for Linux and have a linux file server running Samba so all my Linux , Mac , and Windows machines can access the ISO images ( mount as virtual DVD 's ) from anywhere in the house .
Works great , costs very little ( $ 0.10 USD / GB = = $ 0.40-0.90 / DVD ) , and can easily be copied to a laptop for travel .</tokentext>
<sentencetext>I have a LOT of my DVD collection rip'd to my computer drives.
I use 1.5GB esata hard drives formatted ext3 for Linux and have a linux file server running Samba so all my Linux, Mac, and Windows machines can access the ISO images (mount as virtual DVD's) from anywhere in the house.
Works great, costs very little ($0.10 USD / GB == $0.40-0.90 / DVD), and can easily be copied to a laptop for travel.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540842</id>
	<title>Re:The solution..</title>
	<author>Anonymous</author>
	<datestamp>1259762880000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Agreed. I don't like such noncromulent words.</p></htmltext>
<tokenext>Agreed .
I do n't like such noncromulent words .</tokentext>
<sentencetext>Agreed.
I don't like such noncromulent words.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540130</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541106</id>
	<title>Re:Words of caution</title>
	<author>TooMuchToDo</author>
	<datestamp>1259765880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>That's just as bad as running SQL Server under a virtual machine (SQL Server thinks it has committed the data to disk when it hasn't). *shivers*</htmltext>
<tokenext>That 's just as bad as running SQL Server under a virtual machine ( SQL Server thinks it has committed the data to disk when it has n't ) .
* shivers *</tokentext>
<sentencetext>That's just as bad as running SQL Server under a virtual machine (SQL Server thinks it has committed the data to disk when it hasn't).
*shivers*</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541678</id>
	<title>Use a journaled file system</title>
	<author>Anonymous</author>
	<datestamp>1259773440000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Use a journaled file system - I don't care much which you choose. I prefer JFS or XFS and don't think EXT4 is ready for trusted use yet. For the live data, I'd add Linux software RAID1 or RAID5 or RAID6 protection. mdadm has never let me down even with corrupted disks. Not a single bit has been lost in 5 years. For the backup drive<nobr> <wbr></nobr>... it doesn't matter too much, but I'd stay journaled.</p><p>For media, that doesn't change much, I'd use rsync to mirror the disk file systems efficiently.</p><p>ZFS with zsend would be more efficient, but ZFS has that problem - no Linux kernel support. As much as I love ZFS, I'm not going to run a new OS on my home network just to use it.</p><p>If you really care about this data, consider adding some par2 files to ensure you can correct corruption over time - you know, bit rot (which really does exist). ZFS has data validation built-in.</p><p>At least you aren't planning to store this on DVDs for 10 years and believe all the bits will be there when you come back.</p></htmltext>
<tokenext>Use a journaled file system - I do n't care much which you choose .
I prefer JFS or XFS and do n't think EXT4 is ready for trusted use yet .
For the live data , I 'd add Linux software RAID1 or RAID5 or RAID6 protection .
mdadm has never let me down even with corrupted disks .
Not a single bit has been lost in 5 years .
For the backup drive ... it does n't matter too much , but I 'd stay journaled.For media , that does n't change much , I 'd use rsync to mirror the disk file systems efficiently.ZFS with zsend would be more efficient , but ZFS has that problem - no Linux kernel support .
As much as I love ZFS , I 'm not going to run a new OS on my home network just to use it.If you really care about this data , consider adding some par2 files to ensure you can correct corruption over time - you know , bit rot ( which really does exist ) .
ZFS has data validation built-in.At least you are n't planning to store this on DVDs for 10 years and believe all the bits will be there when you come back .</tokentext>
<sentencetext>Use a journaled file system - I don't care much which you choose.
I prefer JFS or XFS and don't think EXT4 is ready for trusted use yet.
For the live data, I'd add Linux software RAID1 or RAID5 or RAID6 protection.
mdadm has never let me down even with corrupted disks.
Not a single bit has been lost in 5 years.
For the backup drive ... it doesn't matter too much, but I'd stay journaled.For media, that doesn't change much, I'd use rsync to mirror the disk file systems efficiently.ZFS with zsend would be more efficient, but ZFS has that problem - no Linux kernel support.
As much as I love ZFS, I'm not going to run a new OS on my home network just to use it.If you really care about this data, consider adding some par2 files to ensure you can correct corruption over time - you know, bit rot (which really does exist).
ZFS has data validation built-in.At least you aren't planning to store this on DVDs for 10 years and believe all the bits will be there when you come back.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542562</id>
	<title>Filesystems are overrated.</title>
	<author>MaxToTheMax</author>
	<datestamp>1261647360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Use dd and write down all your byte offsets.


Seriously though, go for EXT3 and make sure you don't *write* anything from Windows if you don't trust the drivers. Later on you can do an in-place upgrade to btrfs if you want.</htmltext>
<tokenext>Use dd and write down all your byte offsets .
Seriously though , go for EXT3 and make sure you do n't * write * anything from Windows if you do n't trust the drivers .
Later on you can do an in-place upgrade to btrfs if you want .</tokentext>
<sentencetext>Use dd and write down all your byte offsets.
Seriously though, go for EXT3 and make sure you don't *write* anything from Windows if you don't trust the drivers.
Later on you can do an in-place upgrade to btrfs if you want.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540272</id>
	<title>IBM's HPFS</title>
	<author>Theovon</author>
	<datestamp>1259758320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>IIRC, NTFS is a descendent of something called HPFS, which is what IBM developed for OS/2.  At least as recently as Win2K, Windows would mount and use HPFS partitons, and also I recall that Linux could read/write that as well.  Look into that.</p></htmltext>
<tokenext>IIRC , NTFS is a descendent of something called HPFS , which is what IBM developed for OS/2 .
At least as recently as Win2K , Windows would mount and use HPFS partitons , and also I recall that Linux could read/write that as well .
Look into that .</tokentext>
<sentencetext>IIRC, NTFS is a descendent of something called HPFS, which is what IBM developed for OS/2.
At least as recently as Win2K, Windows would mount and use HPFS partitons, and also I recall that Linux could read/write that as well.
Look into that.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541606</id>
	<title>Re:NTFS-3G vs. nfsmount</title>
	<author>dlapine</author>
	<datestamp>1259772540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>ntfs-3g was updated on nov 14 2009</p><p>ntfsmount was last updated in 2008</p><p>you do the math.</p><p>I've used ntfs-3g for external storage. A lot. ntfs-3g won't fix a corrupted fs or bad block, and you'll need access to the windows box to do that, but since you plan on having access to windows, that shouldn't be an issue. What's nifty is that I haven't seen a large decrease in speed for reads and writes- not as fast on linux as ext3, but 25MB/s isn't out of the question.</p><p>At the moment, I trust open source linux drivers for ntfs much more than anything that has to run on a windows box to let it see ext3.</p></htmltext>
<tokenext>ntfs-3g was updated on nov 14 2009ntfsmount was last updated in 2008you do the math.I 've used ntfs-3g for external storage .
A lot .
ntfs-3g wo n't fix a corrupted fs or bad block , and you 'll need access to the windows box to do that , but since you plan on having access to windows , that should n't be an issue .
What 's nifty is that I have n't seen a large decrease in speed for reads and writes- not as fast on linux as ext3 , but 25MB/s is n't out of the question.At the moment , I trust open source linux drivers for ntfs much more than anything that has to run on a windows box to let it see ext3 .</tokentext>
<sentencetext>ntfs-3g was updated on nov 14 2009ntfsmount was last updated in 2008you do the math.I've used ntfs-3g for external storage.
A lot.
ntfs-3g won't fix a corrupted fs or bad block, and you'll need access to the windows box to do that, but since you plan on having access to windows, that shouldn't be an issue.
What's nifty is that I haven't seen a large decrease in speed for reads and writes- not as fast on linux as ext3, but 25MB/s isn't out of the question.At the moment, I trust open source linux drivers for ntfs much more than anything that has to run on a windows box to let it see ext3.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540688</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541684</id>
	<title>Oblig: XFS plug - it was made for media streaming</title>
	<author>lpq</author>
	<datestamp>1259773740000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>XFS was designed with media streaming in mind -- and designed for large file, high performance.  It had a defragmenter to keep disks in optimal condition before Windows98 had come out (was one at the request of a large, customer who had an especially pathological case -- before that there was normally not considered a need for it).</p><p>Files can be 'normal', have up to and addition 256K of resource-fork related into (extended attribute info), AND you can have a real-time section that can allow for completely bypassing the file system.  It was sufficiently fast for video even back when disks were 1/10th the speed they are now.</p><p>On it's native OS, it could handle multiple streamed data to the same disk and keep it separate by allocating the separate channels out of disparate allocation groups on disk.  I don't know how that works on linux.  Unfornately, on linux even under x64, file block sizes AFAIK, are still limited to 4K.  XFS has a 64K limit, but under linux is hamstrung to 4k.  Of course Windows NT allows 64K block sizes.  But not linux...hmmm....very weird.  XFS minimizes impact of linux's tiny allocation block size by using a extents which can be at least 256k -- but believe the actual limit is in megabytes.  Been a while since I read that stuff...</p><p>Of course -- not to be linux centric, but have heard ZFS is pretty good, but no idea of how it compares for anything.</p><p>my 2 cents...</p></htmltext>
<tokenext>XFS was designed with media streaming in mind -- and designed for large file , high performance .
It had a defragmenter to keep disks in optimal condition before Windows98 had come out ( was one at the request of a large , customer who had an especially pathological case -- before that there was normally not considered a need for it ) .Files can be 'normal ' , have up to and addition 256K of resource-fork related into ( extended attribute info ) , AND you can have a real-time section that can allow for completely bypassing the file system .
It was sufficiently fast for video even back when disks were 1/10th the speed they are now.On it 's native OS , it could handle multiple streamed data to the same disk and keep it separate by allocating the separate channels out of disparate allocation groups on disk .
I do n't know how that works on linux .
Unfornately , on linux even under x64 , file block sizes AFAIK , are still limited to 4K .
XFS has a 64K limit , but under linux is hamstrung to 4k .
Of course Windows NT allows 64K block sizes .
But not linux...hmmm....very weird .
XFS minimizes impact of linux 's tiny allocation block size by using a extents which can be at least 256k -- but believe the actual limit is in megabytes .
Been a while since I read that stuff...Of course -- not to be linux centric , but have heard ZFS is pretty good , but no idea of how it compares for anything.my 2 cents.. .</tokentext>
<sentencetext>XFS was designed with media streaming in mind -- and designed for large file, high performance.
It had a defragmenter to keep disks in optimal condition before Windows98 had come out (was one at the request of a large, customer who had an especially pathological case -- before that there was normally not considered a need for it).Files can be 'normal', have up to and addition 256K of resource-fork related into (extended attribute info), AND you can have a real-time section that can allow for completely bypassing the file system.
It was sufficiently fast for video even back when disks were 1/10th the speed they are now.On it's native OS, it could handle multiple streamed data to the same disk and keep it separate by allocating the separate channels out of disparate allocation groups on disk.
I don't know how that works on linux.
Unfornately, on linux even under x64, file block sizes AFAIK, are still limited to 4K.
XFS has a 64K limit, but under linux is hamstrung to 4k.
Of course Windows NT allows 64K block sizes.
But not linux...hmmm....very weird.
XFS minimizes impact of linux's tiny allocation block size by using a extents which can be at least 256k -- but believe the actual limit is in megabytes.
Been a while since I read that stuff...Of course -- not to be linux centric, but have heard ZFS is pretty good, but no idea of how it compares for anything.my 2 cents...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540620</id>
	<title>Fuse is the answer</title>
	<author>tambu</author>
	<datestamp>1259760960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Use NTFS and then install the Fuse ntfs-3g driver.  This works for read write in linux and OSX and makes it easy.  We all know that Windows supports Microsoft only and that leaves us to configure the other systems we have.
Your distro should have Fuse as a precomplied package and probable the ntfs-3g driver as well.  As for OSX you can find it by searching for "mac fuse" in your favorite search engine.</htmltext>
<tokenext>Use NTFS and then install the Fuse ntfs-3g driver .
This works for read write in linux and OSX and makes it easy .
We all know that Windows supports Microsoft only and that leaves us to configure the other systems we have .
Your distro should have Fuse as a precomplied package and probable the ntfs-3g driver as well .
As for OSX you can find it by searching for " mac fuse " in your favorite search engine .</tokentext>
<sentencetext>Use NTFS and then install the Fuse ntfs-3g driver.
This works for read write in linux and OSX and makes it easy.
We all know that Windows supports Microsoft only and that leaves us to configure the other systems we have.
Your distro should have Fuse as a precomplied package and probable the ntfs-3g driver as well.
As for OSX you can find it by searching for "mac fuse" in your favorite search engine.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541410</id>
	<title>Would VirtualBox (or something) help?</title>
	<author>captrb</author>
	<datestamp>1259770080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>
I'm not sure if this is possible, just throwing it out there...

Could you install a virtualized OS instance on all these hosts, with VirtualBox or VMWare, on each computer?  If so AND you were able to access the raw drives and the hosts files from the vhost (with some magic that I'm not aware of), you could use a filesystem native to the vhost but not to the metal host.</htmltext>
<tokenext>I 'm not sure if this is possible , just throwing it out there.. . Could you install a virtualized OS instance on all these hosts , with VirtualBox or VMWare , on each computer ?
If so AND you were able to access the raw drives and the hosts files from the vhost ( with some magic that I 'm not aware of ) , you could use a filesystem native to the vhost but not to the metal host .</tokentext>
<sentencetext>
I'm not sure if this is possible, just throwing it out there...

Could you install a virtualized OS instance on all these hosts, with VirtualBox or VMWare, on each computer?
If so AND you were able to access the raw drives and the hosts files from the vhost (with some magic that I'm not aware of), you could use a filesystem native to the vhost but not to the metal host.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540296</id>
	<title>Check Tuxera NTFS</title>
	<author>replicant\_deckard</author>
	<datestamp>1259758500000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>If you need Linux/Mac/Windows interoperability then we recommend NTFS for both Linux and Mac users. Instead of the old NTFS kernel driver you may want to check our open source NTFS-3G. It has read/write, and tons of options:<br><a href="http://www.tuxera.com/community/ntfs-3g-advanced/" title="tuxera.com" rel="nofollow">http://www.tuxera.com/community/ntfs-3g-advanced/</a> [tuxera.com]</p><p>If you need just high-performance NTFS read/write, this is our offering for Mac users:<br><a href="http://www.tuxera.com/products/tuxera-ntfs-for-mac/" title="tuxera.com" rel="nofollow">http://www.tuxera.com/products/tuxera-ntfs-for-mac/</a> [tuxera.com]</p><p>If you need high-performance for a commercial Linux application or device, you may want to check this:<br><a href="http://www.tuxera.com/products/tuxera-ntfs-commercial/performance/" title="tuxera.com" rel="nofollow">http://www.tuxera.com/products/tuxera-ntfs-commercial/performance/</a> [tuxera.com]</p><p>Regards,</p><p>Mikko V&#228;lim&#228;ki<br>CEO, Tuxera Ltd</p></htmltext>
<tokenext>If you need Linux/Mac/Windows interoperability then we recommend NTFS for both Linux and Mac users .
Instead of the old NTFS kernel driver you may want to check our open source NTFS-3G .
It has read/write , and tons of options : http : //www.tuxera.com/community/ntfs-3g-advanced/ [ tuxera.com ] If you need just high-performance NTFS read/write , this is our offering for Mac users : http : //www.tuxera.com/products/tuxera-ntfs-for-mac/ [ tuxera.com ] If you need high-performance for a commercial Linux application or device , you may want to check this : http : //www.tuxera.com/products/tuxera-ntfs-commercial/performance/ [ tuxera.com ] Regards,Mikko V   lim   kiCEO , Tuxera Ltd</tokentext>
<sentencetext>If you need Linux/Mac/Windows interoperability then we recommend NTFS for both Linux and Mac users.
Instead of the old NTFS kernel driver you may want to check our open source NTFS-3G.
It has read/write, and tons of options:http://www.tuxera.com/community/ntfs-3g-advanced/ [tuxera.com]If you need just high-performance NTFS read/write, this is our offering for Mac users:http://www.tuxera.com/products/tuxera-ntfs-for-mac/ [tuxera.com]If you need high-performance for a commercial Linux application or device, you may want to check this:http://www.tuxera.com/products/tuxera-ntfs-commercial/performance/ [tuxera.com]Regards,Mikko VälimäkiCEO, Tuxera Ltd</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539956</id>
	<title>NTFS is becoming the lingua franca</title>
	<author>Anonymous</author>
	<datestamp>1259755980000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>Honestly, if FAT32 won't do what you need, NTFS is pretty much where you'll need to go. <a href="http://www.tuxera.com/community/ntfs-3g-download/" title="tuxera.com">NTFS-3g</a> [tuxera.com] gives you stable read/write capability on Linux and OS X as a FUSE driver; in fact, many distributions have NTFS-3g in their repositories. There's also native NTFS write support in Snow Leopard if you want to risk turning it on. I personally haven't had any issues with it, but some people have encountered file corruption when using it, so you might want to be wary. It is worth noting, however, that many embedded devices won't read anything other than FAT. If you plan on hooking this drive up to, say, a DVD player to show pictures, NTFS won't work for you.</p><p>Like it or not, Microsoft file systems are the <i>lingua franca</i> of file transfer on portable drives these days, merely due to the installed base of Windows computers.</p></htmltext>
<tokenext>Honestly , if FAT32 wo n't do what you need , NTFS is pretty much where you 'll need to go .
NTFS-3g [ tuxera.com ] gives you stable read/write capability on Linux and OS X as a FUSE driver ; in fact , many distributions have NTFS-3g in their repositories .
There 's also native NTFS write support in Snow Leopard if you want to risk turning it on .
I personally have n't had any issues with it , but some people have encountered file corruption when using it , so you might want to be wary .
It is worth noting , however , that many embedded devices wo n't read anything other than FAT .
If you plan on hooking this drive up to , say , a DVD player to show pictures , NTFS wo n't work for you.Like it or not , Microsoft file systems are the lingua franca of file transfer on portable drives these days , merely due to the installed base of Windows computers .</tokentext>
<sentencetext>Honestly, if FAT32 won't do what you need, NTFS is pretty much where you'll need to go.
NTFS-3g [tuxera.com] gives you stable read/write capability on Linux and OS X as a FUSE driver; in fact, many distributions have NTFS-3g in their repositories.
There's also native NTFS write support in Snow Leopard if you want to risk turning it on.
I personally haven't had any issues with it, but some people have encountered file corruption when using it, so you might want to be wary.
It is worth noting, however, that many embedded devices won't read anything other than FAT.
If you plan on hooking this drive up to, say, a DVD player to show pictures, NTFS won't work for you.Like it or not, Microsoft file systems are the lingua franca of file transfer on portable drives these days, merely due to the installed base of Windows computers.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542838</id>
	<title>Re:Words of caution</title>
	<author>leuk\_he</author>
	<datestamp>1261653420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Xp is just broeken with USB and ntfs.</p><p>If a write fails you are lucky if you get a popup. It can happen that you just get a</p><p>"An error was detected on device \Device\Harddisk2\D"in the event log but never get a popup. Data will be lost, and even the entire disk might be corrupted.</p><p>Als NTFS often fails the "unplug this device"because certain unplug calls are not implmented for NTFS under XP.</p><p>However, since you need large file support NTFS is still the best option if you need to go cross platform. And the disk repair software is most advanced on windows anyway, just because it is most used. So even if windows cannot repeair the disk with chkdsk (happened to me), tools like getdataback will still be able to retreive most data from it.</p></htmltext>
<tokenext>Xp is just broeken with USB and ntfs.If a write fails you are lucky if you get a popup .
It can happen that you just get a " An error was detected on device \ Device \ Harddisk2 \ D " in the event log but never get a popup .
Data will be lost , and even the entire disk might be corrupted.Als NTFS often fails the " unplug this device " because certain unplug calls are not implmented for NTFS under XP.However , since you need large file support NTFS is still the best option if you need to go cross platform .
And the disk repair software is most advanced on windows anyway , just because it is most used .
So even if windows can not repeair the disk with chkdsk ( happened to me ) , tools like getdataback will still be able to retreive most data from it .</tokentext>
<sentencetext>Xp is just broeken with USB and ntfs.If a write fails you are lucky if you get a popup.
It can happen that you just get a"An error was detected on device \Device\Harddisk2\D"in the event log but never get a popup.
Data will be lost, and even the entire disk might be corrupted.Als NTFS often fails the "unplug this device"because certain unplug calls are not implmented for NTFS under XP.However, since you need large file support NTFS is still the best option if you need to go cross platform.
And the disk repair software is most advanced on windows anyway, just because it is most used.
So even if windows cannot repeair the disk with chkdsk (happened to me), tools like getdataback will still be able to retreive most data from it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30545074</id>
	<title>Don't buy WD "MyBook" externals!!!!!</title>
	<author>Anonymous</author>
	<datestamp>1261677900000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Western Digital apparently felt that well established power management standards were not hip enough and re-invented the wheel, only ribbed for their pleasure (not yours).</p><p>MyBook drives time out and go to sleep on non-windows systems every minute or so, and the linux and XNU kernels react to this rather poorly (in the case of linux kernels, by automagically remounting the drive RO which is actually worse than just erroring out).</p><p>They don't work right on windows systems either, unless you load the special drivers that slow down your whole OS.</p><p>Treat "MyBook" drives like the utter dogshit they are.  That's how WD has been treating their customers who have complained, so it's appropriate.  This post soon to be modded flamebait by WD staff....</p><p>Does anyone know if the other WD stuff is also non-standard crap?  I have been afraid to buy anything from else them since they burned my ass on the 1TB MyBook.</p><p><a href="http://www.google.com/search?q=western+digital+mybook+\%22times+out\%22" title="google.com" rel="nofollow">http://www.google.com/search?q=western+digital+mybook+\%22times+out\%22</a> [google.com]</p></htmltext>
<tokenext>Western Digital apparently felt that well established power management standards were not hip enough and re-invented the wheel , only ribbed for their pleasure ( not yours ) .MyBook drives time out and go to sleep on non-windows systems every minute or so , and the linux and XNU kernels react to this rather poorly ( in the case of linux kernels , by automagically remounting the drive RO which is actually worse than just erroring out ) .They do n't work right on windows systems either , unless you load the special drivers that slow down your whole OS.Treat " MyBook " drives like the utter dogshit they are .
That 's how WD has been treating their customers who have complained , so it 's appropriate .
This post soon to be modded flamebait by WD staff....Does anyone know if the other WD stuff is also non-standard crap ?
I have been afraid to buy anything from else them since they burned my ass on the 1TB MyBook.http : //www.google.com/search ? q = western + digital + mybook + \ % 22times + out \ % 22 [ google.com ]</tokentext>
<sentencetext>Western Digital apparently felt that well established power management standards were not hip enough and re-invented the wheel, only ribbed for their pleasure (not yours).MyBook drives time out and go to sleep on non-windows systems every minute or so, and the linux and XNU kernels react to this rather poorly (in the case of linux kernels, by automagically remounting the drive RO which is actually worse than just erroring out).They don't work right on windows systems either, unless you load the special drivers that slow down your whole OS.Treat "MyBook" drives like the utter dogshit they are.
That's how WD has been treating their customers who have complained, so it's appropriate.
This post soon to be modded flamebait by WD staff....Does anyone know if the other WD stuff is also non-standard crap?
I have been afraid to buy anything from else them since they burned my ass on the 1TB MyBook.http://www.google.com/search?q=western+digital+mybook+\%22times+out\%22 [google.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30576454</id>
	<title>Re:NTFS and Compress</title>
	<author>jon3k</author>
	<datestamp>1261998840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>"mp3 files are like<nobr> <wbr></nobr>.jpg image files such that they lose a little quality/data each time they are copied"
<br> <br>
Is this a joke?</htmltext>
<tokenext>" mp3 files are like .jpg image files such that they lose a little quality/data each time they are copied " Is this a joke ?</tokentext>
<sentencetext>"mp3 files are like .jpg image files such that they lose a little quality/data each time they are copied"
 
Is this a joke?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541020</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30543926</id>
	<title>Samba and Unison</title>
	<author>poolecl</author>
	<datestamp>1261670400000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>I myself wanted a setup like this several months ago and settled on setting up 2 Ubuntu systems with internal 2TB hard drive.  One at home and one at my remote location.  I share the drive over my local network with Samba.  (The drives themselves are formatted ext3 or ext4, but that hardly matters to the rest of the network once they are shared.)  (To later support Mac OS X you could try getting afp working, but it will still happily mount samba also, which is what I do with my mac.)  Which is fast enough to serve video, and means I don't have to lug a drive around the house.  And I periodically run Unison to keep the systems in sync over SSH.  Even pre-mirroring the drives, Unison takes a day or so to run the initial sync.  But after that first run, the syncs are pretty quick.  At the moment I am manually running the GUI Unison, but I plan on eventually switching to the command line version and automating it in a cron task.</p></htmltext>
<tokenext>I myself wanted a setup like this several months ago and settled on setting up 2 Ubuntu systems with internal 2TB hard drive .
One at home and one at my remote location .
I share the drive over my local network with Samba .
( The drives themselves are formatted ext3 or ext4 , but that hardly matters to the rest of the network once they are shared .
) ( To later support Mac OS X you could try getting afp working , but it will still happily mount samba also , which is what I do with my mac .
) Which is fast enough to serve video , and means I do n't have to lug a drive around the house .
And I periodically run Unison to keep the systems in sync over SSH .
Even pre-mirroring the drives , Unison takes a day or so to run the initial sync .
But after that first run , the syncs are pretty quick .
At the moment I am manually running the GUI Unison , but I plan on eventually switching to the command line version and automating it in a cron task .</tokentext>
<sentencetext>I myself wanted a setup like this several months ago and settled on setting up 2 Ubuntu systems with internal 2TB hard drive.
One at home and one at my remote location.
I share the drive over my local network with Samba.
(The drives themselves are formatted ext3 or ext4, but that hardly matters to the rest of the network once they are shared.
)  (To later support Mac OS X you could try getting afp working, but it will still happily mount samba also, which is what I do with my mac.
)  Which is fast enough to serve video, and means I don't have to lug a drive around the house.
And I periodically run Unison to keep the systems in sync over SSH.
Even pre-mirroring the drives, Unison takes a day or so to run the initial sync.
But after that first run, the syncs are pretty quick.
At the moment I am manually running the GUI Unison, but I plan on eventually switching to the command line version and automating it in a cron task.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540928</id>
	<title>NTFS-3G</title>
	<author>Lord Kano</author>
	<datestamp>1259763780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It's stable, it works, it uses Fuse so you don't have to worry about Kernel support.</p><p><a href="http://www.tuxera.com/community/ntfs-3g-download/" title="tuxera.com">Just go get it.</a> [tuxera.com]</p><p>LK</p></htmltext>
<tokenext>It 's stable , it works , it uses Fuse so you do n't have to worry about Kernel support.Just go get it .
[ tuxera.com ] LK</tokentext>
<sentencetext>It's stable, it works, it uses Fuse so you don't have to worry about Kernel support.Just go get it.
[tuxera.com]LK</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540412</id>
	<title>Re:The solution..</title>
	<author>BiggerIsBetter</author>
	<datestamp>1259759280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Really? I thought it was nonsense cause by proliferation of The Far Side cartoons.</p></htmltext>
<tokenext>Really ?
I thought it was nonsense cause by proliferation of The Far Side cartoons .</tokentext>
<sentencetext>Really?
I thought it was nonsense cause by proliferation of The Far Side cartoons.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540130</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540152</id>
	<title>Re:Ext3</title>
	<author>Anonymous</author>
	<datestamp>1259757600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Yes, or HFS+ will work too if you use HFSExplorer for windows, as Linux has very good support for HFS+.</htmltext>
<tokenext>Yes , or HFS + will work too if you use HFSExplorer for windows , as Linux has very good support for HFS + .</tokentext>
<sentencetext>Yes, or HFS+ will work too if you use HFSExplorer for windows, as Linux has very good support for HFS+.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539804</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542788</id>
	<title>Best Filesystem For External Back-Up Drives?</title>
	<author>Lost Penguin</author>
	<datestamp>1261652580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>WAFL</htmltext>
<tokenext>WAFL</tokentext>
<sentencetext>WAFL</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30546390</id>
	<title>Why has nobody suggested UDF?</title>
	<author>jesboat</author>
	<datestamp>1261687260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>FAT32: no POSIX metadata, 4GB file size limit is deadly. It's inefficient, and generally outdated and nasty.</p><p>NTFS: proprietary, sometimes complicated to get on Linux, hard to get on OSX.</p><p>ext*: bad-to-none support on non-Linux. IIRC, neither the Windows nor OSX drivers support journaling, for example.</p><p>HFS+: about the same boat as ext*, if you swap "Linux" and "OSX".</p><p>UDF: reasonably efficient, support for basic metadata (POSIX, though no EAs or forks), full support on Linux 2.6, OSX 10.5, Windows Vista/7, or (with third-party utils)</p></htmltext>
<tokenext>FAT32 : no POSIX metadata , 4GB file size limit is deadly .
It 's inefficient , and generally outdated and nasty.NTFS : proprietary , sometimes complicated to get on Linux , hard to get on OSX.ext * : bad-to-none support on non-Linux .
IIRC , neither the Windows nor OSX drivers support journaling , for example.HFS + : about the same boat as ext * , if you swap " Linux " and " OSX " .UDF : reasonably efficient , support for basic metadata ( POSIX , though no EAs or forks ) , full support on Linux 2.6 , OSX 10.5 , Windows Vista/7 , or ( with third-party utils )</tokentext>
<sentencetext>FAT32: no POSIX metadata, 4GB file size limit is deadly.
It's inefficient, and generally outdated and nasty.NTFS: proprietary, sometimes complicated to get on Linux, hard to get on OSX.ext*: bad-to-none support on non-Linux.
IIRC, neither the Windows nor OSX drivers support journaling, for example.HFS+: about the same boat as ext*, if you swap "Linux" and "OSX".UDF: reasonably efficient, support for basic metadata (POSIX, though no EAs or forks), full support on Linux 2.6, OSX 10.5, Windows Vista/7, or (with third-party utils)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970</id>
	<title>Words of caution</title>
	<author>RenHoek</author>
	<datestamp>1259756040000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p>I have ~6TB on external USB drives and I've been doing this for a few years now. I have a few words of caution about NTFS. If you get an USB drive that for example spins down or if you turn your USB drive off without properly dismounting it (or if Windows crashes), you might see this line:</p><p><b>Delayed write failed!</b></p><p>And on two occasions that meant that Windows fucked up the file allocation table or whatever it's called under NTFS and I lost the \_entire\_ disk.</p><p>Windows loves getting its fingers into that table whenever you mount a USB filesystem. It's not like it tries to keep its write cache empty. Nooo.. every file access needs to be continuously recorded in that thing.</p><p>Anyway, be careful when you use NTFS on a USB drive. Alternatively use EXT3, which you can still mount under Windows using:</p><p><a href="http://www.ext2fsd.com/" title="ext2fsd.com" rel="nofollow">http://www.ext2fsd.com/</a> [ext2fsd.com]</p><p>(Note that these experiences are under Windows XP, I have no clue if Vista or 7 does any better, I assume not.)</p></htmltext>
<tokenext>I have ~ 6TB on external USB drives and I 've been doing this for a few years now .
I have a few words of caution about NTFS .
If you get an USB drive that for example spins down or if you turn your USB drive off without properly dismounting it ( or if Windows crashes ) , you might see this line : Delayed write failed ! And on two occasions that meant that Windows fucked up the file allocation table or whatever it 's called under NTFS and I lost the \ _entire \ _ disk.Windows loves getting its fingers into that table whenever you mount a USB filesystem .
It 's not like it tries to keep its write cache empty .
Nooo.. every file access needs to be continuously recorded in that thing.Anyway , be careful when you use NTFS on a USB drive .
Alternatively use EXT3 , which you can still mount under Windows using : http : //www.ext2fsd.com/ [ ext2fsd.com ] ( Note that these experiences are under Windows XP , I have no clue if Vista or 7 does any better , I assume not .
)</tokentext>
<sentencetext>I have ~6TB on external USB drives and I've been doing this for a few years now.
I have a few words of caution about NTFS.
If you get an USB drive that for example spins down or if you turn your USB drive off without properly dismounting it (or if Windows crashes), you might see this line:Delayed write failed!And on two occasions that meant that Windows fucked up the file allocation table or whatever it's called under NTFS and I lost the \_entire\_ disk.Windows loves getting its fingers into that table whenever you mount a USB filesystem.
It's not like it tries to keep its write cache empty.
Nooo.. every file access needs to be continuously recorded in that thing.Anyway, be careful when you use NTFS on a USB drive.
Alternatively use EXT3, which you can still mount under Windows using:http://www.ext2fsd.com/ [ext2fsd.com](Note that these experiences are under Windows XP, I have no clue if Vista or 7 does any better, I assume not.
)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542162</id>
	<title>use checksumming (md5's etc...)</title>
	<author>Anonymous</author>
	<datestamp>1259781540000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Just a tip, it's really disasterous when you don't realize that data has been corrupted, and external drives can be a wee bit more susceptible than we might hope... Try setting up checksumming in appropriate places, and before deleting older versions of things, just check what you "think" you still have... (dvdsig.exe is a prog I have seen around for this purpose... - or create some scripts!)</p></htmltext>
<tokenext>Just a tip , it 's really disasterous when you do n't realize that data has been corrupted , and external drives can be a wee bit more susceptible than we might hope... Try setting up checksumming in appropriate places , and before deleting older versions of things , just check what you " think " you still have... ( dvdsig.exe is a prog I have seen around for this purpose... - or create some scripts !
)</tokentext>
<sentencetext>Just a tip, it's really disasterous when you don't realize that data has been corrupted, and external drives can be a wee bit more susceptible than we might hope... Try setting up checksumming in appropriate places, and before deleting older versions of things, just check what you "think" you still have... (dvdsig.exe is a prog I have seen around for this purpose... - or create some scripts!
)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540364</id>
	<title>FastFileSystem + DirCache</title>
	<author>frambris</author>
	<datestamp>1259759040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Works just fine on the Amiga...</p><p>Ooh, wrong century... sorry</p></htmltext>
<tokenext>Works just fine on the Amiga...Ooh , wrong century... sorry</tokentext>
<sentencetext>Works just fine on the Amiga...Ooh, wrong century... sorry</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539924</id>
	<title>Wikipedia says...</title>
	<author>Anonymous</author>
	<datestamp>1259755860000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Posting anon cuz this is TOTALLY offtopic and I hate getting negative mods, but <a href="http://en.wikipedia.org/wiki/Irregardless" title="wikipedia.org" rel="nofollow">Wikipedia sums it up pretty well in the first sentence</a> [wikipedia.org]:</p><p>"Irregardless is a term meaning regardless or irrespective, which has caused controversy since it first appeared in the early twentieth century. It is generally listed in dictionaries as 'incorrect' or 'nonstandard'."</p></htmltext>
<tokenext>Posting anon cuz this is TOTALLY offtopic and I hate getting negative mods , but Wikipedia sums it up pretty well in the first sentence [ wikipedia.org ] : " Irregardless is a term meaning regardless or irrespective , which has caused controversy since it first appeared in the early twentieth century .
It is generally listed in dictionaries as 'incorrect ' or 'nonstandard' .
"</tokentext>
<sentencetext>Posting anon cuz this is TOTALLY offtopic and I hate getting negative mods, but Wikipedia sums it up pretty well in the first sentence [wikipedia.org]:"Irregardless is a term meaning regardless or irrespective, which has caused controversy since it first appeared in the early twentieth century.
It is generally listed in dictionaries as 'incorrect' or 'nonstandard'.
"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539858</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30543588</id>
	<title>nice...</title>
	<author>ZenDragon</author>
	<datestamp>1261667820000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>This is the kind of topic that SHOULD be on slashdot. And no Im not being sarcastic. Something informational that might benefit everybody, dispite all the bickering in the subsequent posts! There's one thing you can count on with slashdot readers, dispite how arrogant most of us are, or how ignorant most are when it comes to politicial information - We usually know our shit when it comes to computer stuff!<nobr> <wbr></nobr>:)</htmltext>
<tokenext>This is the kind of topic that SHOULD be on slashdot .
And no Im not being sarcastic .
Something informational that might benefit everybody , dispite all the bickering in the subsequent posts !
There 's one thing you can count on with slashdot readers , dispite how arrogant most of us are , or how ignorant most are when it comes to politicial information - We usually know our shit when it comes to computer stuff !
: )</tokentext>
<sentencetext>This is the kind of topic that SHOULD be on slashdot.
And no Im not being sarcastic.
Something informational that might benefit everybody, dispite all the bickering in the subsequent posts!
There's one thing you can count on with slashdot readers, dispite how arrogant most of us are, or how ignorant most are when it comes to politicial information - We usually know our shit when it comes to computer stuff!
:)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30544044</id>
	<title>Re:NTFS</title>
	<author>MobyDisk</author>
	<datestamp>1261671480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Agreed.  I've been using NTFS-3G on OS X for many years and I have had no problems.  Not for trivial matters either: The NTFS drive is my primary storage, with only OS and apps on the Mac partition.  Also, I'm not sure the submitters comment about NTFS on Linux is correct at all: I've used Linux distros (Knoopix maybe?) that had full NTFS write capability out-of-the box.  I don't think it is taboo any longer.</p></htmltext>
<tokenext>Agreed .
I 've been using NTFS-3G on OS X for many years and I have had no problems .
Not for trivial matters either : The NTFS drive is my primary storage , with only OS and apps on the Mac partition .
Also , I 'm not sure the submitters comment about NTFS on Linux is correct at all : I 've used Linux distros ( Knoopix maybe ?
) that had full NTFS write capability out-of-the box .
I do n't think it is taboo any longer .</tokentext>
<sentencetext>Agreed.
I've been using NTFS-3G on OS X for many years and I have had no problems.
Not for trivial matters either: The NTFS drive is my primary storage, with only OS and apps on the Mac partition.
Also, I'm not sure the submitters comment about NTFS on Linux is correct at all: I've used Linux distros (Knoopix maybe?
) that had full NTFS write capability out-of-the box.
I don't think it is taboo any longer.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539824</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541060</id>
	<title>For my backup</title>
	<author>Anonymous</author>
	<datestamp>1259765340000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>For my backup, I use an external firewire drive that I leave turned off, except once per month, when I turn it on, mount it (linux system), and run rsync between it and another drive (my home directories).  Runs very slick.  I've also used Rsync to recover data off of a dying drive.  I could only get data off of it for about 10 minutes (and it had to be cold).  Rsync worked like a charm.  I got alll the data off after a few hours (about 85 GB, 10 minutes at a time), followed by 30 minutes of cooling down.  Rsync worked like a charm.  I would use Reiserfs to handle the large data size (easily handles 1TB and 100 TB filesystems.  I can also add encryption to it so that if the drive gets stolen, then yes, they will have to crack <a href="http://en.wikipedia.org/wiki/Skipjack\_(cipher)" title="wikipedia.org" rel="nofollow">skipjack</a> [wikipedia.org] in order to get at the data.  Its not impossible, but, good luck with that.</p></htmltext>
<tokenext>For my backup , I use an external firewire drive that I leave turned off , except once per month , when I turn it on , mount it ( linux system ) , and run rsync between it and another drive ( my home directories ) .
Runs very slick .
I 've also used Rsync to recover data off of a dying drive .
I could only get data off of it for about 10 minutes ( and it had to be cold ) .
Rsync worked like a charm .
I got alll the data off after a few hours ( about 85 GB , 10 minutes at a time ) , followed by 30 minutes of cooling down .
Rsync worked like a charm .
I would use Reiserfs to handle the large data size ( easily handles 1TB and 100 TB filesystems .
I can also add encryption to it so that if the drive gets stolen , then yes , they will have to crack skipjack [ wikipedia.org ] in order to get at the data .
Its not impossible , but , good luck with that .</tokentext>
<sentencetext>For my backup, I use an external firewire drive that I leave turned off, except once per month, when I turn it on, mount it (linux system), and run rsync between it and another drive (my home directories).
Runs very slick.
I've also used Rsync to recover data off of a dying drive.
I could only get data off of it for about 10 minutes (and it had to be cold).
Rsync worked like a charm.
I got alll the data off after a few hours (about 85 GB, 10 minutes at a time), followed by 30 minutes of cooling down.
Rsync worked like a charm.
I would use Reiserfs to handle the large data size (easily handles 1TB and 100 TB filesystems.
I can also add encryption to it so that if the drive gets stolen, then yes, they will have to crack skipjack [wikipedia.org] in order to get at the data.
Its not impossible, but, good luck with that.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541402</id>
	<title>Re:Words of caution</title>
	<author>DigiShaman</author>
	<datestamp>1259769840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I've lost files that way, but never - ever- an entire NTFS volume. Regardless, you are supposed to eject all removable storage (flushes write-back cache) prior to pulling the plug. Because you didn't do that, you got the "Delayed write failed" message.</p><p>FYI, you can create shortcut that will bring you to the eject USB device window. It's the same as the one located in the system tray. Below is the link with simple instructions.</p><p><a href="http://www.neilturner.me.uk/2007/04/05/create\_a\_safely\_remove\_ha.html" title="neilturner.me.uk">http://www.neilturner.me.uk/2007/04/05/create\_a\_safely\_remove\_ha.html</a> [neilturner.me.uk]</p></htmltext>
<tokenext>I 've lost files that way , but never - ever- an entire NTFS volume .
Regardless , you are supposed to eject all removable storage ( flushes write-back cache ) prior to pulling the plug .
Because you did n't do that , you got the " Delayed write failed " message.FYI , you can create shortcut that will bring you to the eject USB device window .
It 's the same as the one located in the system tray .
Below is the link with simple instructions.http : //www.neilturner.me.uk/2007/04/05/create \ _a \ _safely \ _remove \ _ha.html [ neilturner.me.uk ]</tokentext>
<sentencetext>I've lost files that way, but never - ever- an entire NTFS volume.
Regardless, you are supposed to eject all removable storage (flushes write-back cache) prior to pulling the plug.
Because you didn't do that, you got the "Delayed write failed" message.FYI, you can create shortcut that will bring you to the eject USB device window.
It's the same as the one located in the system tray.
Below is the link with simple instructions.http://www.neilturner.me.uk/2007/04/05/create\_a\_safely\_remove\_ha.html [neilturner.me.uk]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30544882</id>
	<title>Has anyone tried UDF</title>
	<author>Anonymous</author>
	<datestamp>1261676640000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I have been thinking about this recently and I had wondered if I could format a Harddrive as UDF like a big DVD.  This format is readable by both Windows and Linux and I believe is writable to, although I have only ever used it on write-once media.</p><p>I got as far as finding Windows and Linux formatting commands as follows:</p><p>Windows Vista or later: "format x:<nobr> <wbr></nobr>/fs:UDF" (don't use<nobr> <wbr></nobr>/q ! )<br>Linux: "mkudffs --media-type=hd<nobr> <wbr></nobr>/dev/sdx"</p><p>However, I have never actually tried it yet; so if anyone else has I would be curious as to how successful they were.</p></htmltext>
<tokenext>I have been thinking about this recently and I had wondered if I could format a Harddrive as UDF like a big DVD .
This format is readable by both Windows and Linux and I believe is writable to , although I have only ever used it on write-once media.I got as far as finding Windows and Linux formatting commands as follows : Windows Vista or later : " format x : /fs : UDF " ( do n't use /q !
) Linux : " mkudffs --media-type = hd /dev/sdx " However , I have never actually tried it yet ; so if anyone else has I would be curious as to how successful they were .</tokentext>
<sentencetext>I have been thinking about this recently and I had wondered if I could format a Harddrive as UDF like a big DVD.
This format is readable by both Windows and Linux and I believe is writable to, although I have only ever used it on write-once media.I got as far as finding Windows and Linux formatting commands as follows:Windows Vista or later: "format x: /fs:UDF" (don't use /q !
)Linux: "mkudffs --media-type=hd /dev/sdx"However, I have never actually tried it yet; so if anyone else has I would be curious as to how successful they were.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542324</id>
	<title>Re:The solution..</title>
	<author>Anonymous</author>
	<datestamp>1261685220000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Irregardless, the fact that the term was used and its meaning was understood meant that communication took place.  Regardless of the syntax and failure to comply successfully to an established protocol, this new term was processed successfully.  This is how words in language are created, irregardless of whether it conforms to conventions.  The fact that two people use the word and can understand its meaning demonstrates its validity as a term in language.  It might not be proper English, but really what is?  There are generally sub-dialects in every language and language is always evolving - it has to as the world is always changing and we always need new ways to describe what we see and experience. If ringtone and spyware are words, then hell irregardless can be to if enough people accept it.</p></htmltext>
<tokenext>Irregardless , the fact that the term was used and its meaning was understood meant that communication took place .
Regardless of the syntax and failure to comply successfully to an established protocol , this new term was processed successfully .
This is how words in language are created , irregardless of whether it conforms to conventions .
The fact that two people use the word and can understand its meaning demonstrates its validity as a term in language .
It might not be proper English , but really what is ?
There are generally sub-dialects in every language and language is always evolving - it has to as the world is always changing and we always need new ways to describe what we see and experience .
If ringtone and spyware are words , then hell irregardless can be to if enough people accept it .</tokentext>
<sentencetext>Irregardless, the fact that the term was used and its meaning was understood meant that communication took place.
Regardless of the syntax and failure to comply successfully to an established protocol, this new term was processed successfully.
This is how words in language are created, irregardless of whether it conforms to conventions.
The fact that two people use the word and can understand its meaning demonstrates its validity as a term in language.
It might not be proper English, but really what is?
There are generally sub-dialects in every language and language is always evolving - it has to as the world is always changing and we always need new ways to describe what we see and experience.
If ringtone and spyware are words, then hell irregardless can be to if enough people accept it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540130</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540372</id>
	<title>Re:Words of caution</title>
	<author>euxneks</author>
	<datestamp>1259759100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>However, it's a bitch to get ext3 mounted on OSX. - it would be better to just do something like was suggested by other posters, a freeNAS or freeBSD setup and share the drives over the network.</htmltext>
<tokenext>However , it 's a bitch to get ext3 mounted on OSX .
- it would be better to just do something like was suggested by other posters , a freeNAS or freeBSD setup and share the drives over the network .</tokentext>
<sentencetext>However, it's a bitch to get ext3 mounted on OSX.
- it would be better to just do something like was suggested by other posters, a freeNAS or freeBSD setup and share the drives over the network.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540396</id>
	<title>Re:I wouldn't....</title>
	<author>euxneks</author>
	<datestamp>1259759160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Mod parent up. Ext3 doesn't work nicely with Mac OSX (last time I checked anyway) and I hear bad things about NTFS on external drives (besides which, it's a microsoft technology - fuck em)</htmltext>
<tokenext>Mod parent up .
Ext3 does n't work nicely with Mac OSX ( last time I checked anyway ) and I hear bad things about NTFS on external drives ( besides which , it 's a microsoft technology - fuck em )</tokentext>
<sentencetext>Mod parent up.
Ext3 doesn't work nicely with Mac OSX (last time I checked anyway) and I hear bad things about NTFS on external drives (besides which, it's a microsoft technology - fuck em)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539912</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30553484</id>
	<title>I have a drive I use for that.</title>
	<author>Anonymous</author>
	<datestamp>1261749540000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Used ext3, tried to install the drivers on my Mac and gave up.  Came to a simple conclusion.  If it's not Ubuntu, **** it.</p><p>Multiplatform.  Decent.  You may pick one.  But now of course ext4 is out, which is much better than 3, so go with that instead.</p></htmltext>
<tokenext>Used ext3 , tried to install the drivers on my Mac and gave up .
Came to a simple conclusion .
If it 's not Ubuntu , * * * * it.Multiplatform .
Decent. You may pick one .
But now of course ext4 is out , which is much better than 3 , so go with that instead .</tokentext>
<sentencetext>Used ext3, tried to install the drivers on my Mac and gave up.
Came to a simple conclusion.
If it's not Ubuntu, **** it.Multiplatform.
Decent.  You may pick one.
But now of course ext4 is out, which is much better than 3, so go with that instead.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540138</id>
	<title>Re:The best is...</title>
	<author>Anonymous</author>
	<datestamp>1259757420000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext>Yeah, but it's murder getting support.</htmltext>
<tokenext>Yeah , but it 's murder getting support .</tokentext>
<sentencetext>Yeah, but it's murder getting support.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539888</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540302</id>
	<title>Re:Words of caution</title>
	<author>compro01</author>
	<datestamp>1259758560000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext><p>Turn off write caching for the drive and this problem goes away.  It's supposed to be off by default (at least on removable drives, but some IDE/SATA-to-USB bridges show up as normal fixed drives rather than removable for whatever reason), but I've found it seems to turn itself on for whatever stupid reason.</p></htmltext>
<tokenext>Turn off write caching for the drive and this problem goes away .
It 's supposed to be off by default ( at least on removable drives , but some IDE/SATA-to-USB bridges show up as normal fixed drives rather than removable for whatever reason ) , but I 've found it seems to turn itself on for whatever stupid reason .</tokentext>
<sentencetext>Turn off write caching for the drive and this problem goes away.
It's supposed to be off by default (at least on removable drives, but some IDE/SATA-to-USB bridges show up as normal fixed drives rather than removable for whatever reason), but I've found it seems to turn itself on for whatever stupid reason.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541798</id>
	<title>Re:NTFS</title>
	<author>Anonymous</author>
	<datestamp>1259776080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>NTFS-3G (and plain NTFS now too) is the best to allow Linux and Windows to both access the drive easily.</p><p>I've standardized my external drives on it because it is plug and play in both Linux and Windows.</p></htmltext>
<tokenext>NTFS-3G ( and plain NTFS now too ) is the best to allow Linux and Windows to both access the drive easily.I 've standardized my external drives on it because it is plug and play in both Linux and Windows .</tokentext>
<sentencetext>NTFS-3G (and plain NTFS now too) is the best to allow Linux and Windows to both access the drive easily.I've standardized my external drives on it because it is plug and play in both Linux and Windows.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539824</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542678</id>
	<title>Re:Words of caution</title>
	<author>Anonymous</author>
	<datestamp>1261650480000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>You evidently made no attempt to recover the data.</p><p>NTFS is a pretty good filesystem from a data recovery point of view. if you can find the MFT entry for a file then you'll get the file back (even large files) with few if any fragmentation issues.</p></htmltext>
<tokenext>You evidently made no attempt to recover the data.NTFS is a pretty good filesystem from a data recovery point of view .
if you can find the MFT entry for a file then you 'll get the file back ( even large files ) with few if any fragmentation issues .</tokentext>
<sentencetext>You evidently made no attempt to recover the data.NTFS is a pretty good filesystem from a data recovery point of view.
if you can find the MFT entry for a file then you'll get the file back (even large files) with few if any fragmentation issues.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30543022</id>
	<title>Case sensitivity</title>
	<author>Anonymous</author>
	<datestamp>1261658460000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Ext file systems are almost useless on windows because of their case sensitivity. Hard-coded file names in applications are often different from those files they refering to. So windows require at least one drive without case sensitive file system where applications and system would be stored.</p></htmltext>
<tokenext>Ext file systems are almost useless on windows because of their case sensitivity .
Hard-coded file names in applications are often different from those files they refering to .
So windows require at least one drive without case sensitive file system where applications and system would be stored .</tokentext>
<sentencetext>Ext file systems are almost useless on windows because of their case sensitivity.
Hard-coded file names in applications are often different from those files they refering to.
So windows require at least one drive without case sensitive file system where applications and system would be stored.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540418</id>
	<title>HFS</title>
	<author>countach</author>
	<datestamp>1259759340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Looks to me like HFS is the way to go since there are good solutions for all three platforms for HFS.</p></htmltext>
<tokenext>Looks to me like HFS is the way to go since there are good solutions for all three platforms for HFS .</tokentext>
<sentencetext>Looks to me like HFS is the way to go since there are good solutions for all three platforms for HFS.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539888</id>
	<title>The best is...</title>
	<author>Anonymous</author>
	<datestamp>1259755680000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>...ReiserFS. I hear it's killer.</p></htmltext>
<tokenext>...ReiserFS .
I hear it 's killer .</tokentext>
<sentencetext>...ReiserFS.
I hear it's killer.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540158</id>
	<title>Re:ZFS, supported equally on your OSes</title>
	<author>Mr. Protocol</author>
	<datestamp>1259757600000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext><p>Sadly, if you create a ZFS tank on a Solaris box and then move the tank physically to a FreeBSD 8.0-RELEASE machine, it won't even see that there's a tank out there.  Apparently GPT table layout is different on FreeBSD or something.</p><p>Won't stop you from serving ZFS over NFS/Samba/whatever, but you can't move the tank itself around.  I know, I tried.  Booted FreeBSD on a machine with a Solaris-issue ZFS tank, and it was like it wasn't there.  It saw the drives fine, just not the tank.</p></htmltext>
<tokenext>Sadly , if you create a ZFS tank on a Solaris box and then move the tank physically to a FreeBSD 8.0-RELEASE machine , it wo n't even see that there 's a tank out there .
Apparently GPT table layout is different on FreeBSD or something.Wo n't stop you from serving ZFS over NFS/Samba/whatever , but you ca n't move the tank itself around .
I know , I tried .
Booted FreeBSD on a machine with a Solaris-issue ZFS tank , and it was like it was n't there .
It saw the drives fine , just not the tank .</tokentext>
<sentencetext>Sadly, if you create a ZFS tank on a Solaris box and then move the tank physically to a FreeBSD 8.0-RELEASE machine, it won't even see that there's a tank out there.
Apparently GPT table layout is different on FreeBSD or something.Won't stop you from serving ZFS over NFS/Samba/whatever, but you can't move the tank itself around.
I know, I tried.
Booted FreeBSD on a machine with a Solaris-issue ZFS tank, and it was like it wasn't there.
It saw the drives fine, just not the tank.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539916</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542674</id>
	<title>Bubba!</title>
	<author>talornin</author>
	<datestamp>1261650420000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>I ended up doing as most in this thread did. Networking.
<br> <br>
I bought a BubbaII from <a href="http://www.excito.com/" title="excito.com" rel="nofollow">http://www.excito.com/</a> [excito.com] its a small fan less linux box with 2x usb, 2x ethernet, and 2x extSata.
<br> <br>
NB: NICs are gigEthernet, but they perform substantially slower than one expects. This according to the manufacturer, is by design to keen the temperature at a resonable level to accommodate the fan less design.</htmltext>
<tokenext>I ended up doing as most in this thread did .
Networking . I bought a BubbaII from http : //www.excito.com/ [ excito.com ] its a small fan less linux box with 2x usb , 2x ethernet , and 2x extSata .
NB : NICs are gigEthernet , but they perform substantially slower than one expects .
This according to the manufacturer , is by design to keen the temperature at a resonable level to accommodate the fan less design .</tokentext>
<sentencetext>I ended up doing as most in this thread did.
Networking.
 
I bought a BubbaII from http://www.excito.com/ [excito.com] its a small fan less linux box with 2x usb, 2x ethernet, and 2x extSata.
NB: NICs are gigEthernet, but they perform substantially slower than one expects.
This according to the manufacturer, is by design to keen the temperature at a resonable level to accommodate the fan less design.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541122</id>
	<title>Re:network it</title>
	<author>Anonymous</author>
	<datestamp>1259766060000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Samba isnt the filesystem, its called CIFS (Common Internet File System) or SMB (Server Message Block) or the new SMB2</p></htmltext>
<tokenext>Samba isnt the filesystem , its called CIFS ( Common Internet File System ) or SMB ( Server Message Block ) or the new SMB2</tokentext>
<sentencetext>Samba isnt the filesystem, its called CIFS (Common Internet File System) or SMB (Server Message Block) or the new SMB2</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539974</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539804</id>
	<title>Ext3</title>
	<author>Anonymous</author>
	<datestamp>1259755080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>It is open, and the driver is available for windows.  And I don't see it just disappearing, so nothing can read it.</htmltext>
<tokenext>It is open , and the driver is available for windows .
And I do n't see it just disappearing , so nothing can read it .</tokentext>
<sentencetext>It is open, and the driver is available for windows.
And I don't see it just disappearing, so nothing can read it.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540484</id>
	<title>Ready made solution</title>
	<author>Anonymous</author>
	<datestamp>1259759880000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>One word : FreeNAS.</p></htmltext>
<tokenext>One word : FreeNAS .</tokentext>
<sentencetext>One word : FreeNAS.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541200</id>
	<title>What about AFS ?</title>
	<author>Salsaman</author>
	<datestamp>1259766840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I am surprised that nobody has mentioned it, but what about a server running <a href="http://en.wikipedia.org/wiki/Andrew\_File\_System" title="wikipedia.org">AFS</a> [wikipedia.org] (Andrew File System).<br> <br>It has some great features:<br> <br>Scalable - you can add as many servers as you want<br>Secure - it uses kerberos by default<br>Fast - local caches are kept until another client needs them.<br>Cross platform - <a href="http://en.wikipedia.org/wiki/OpenAFS" title="wikipedia.org">openAFS</a> [wikipedia.org] supports pretty much every platform in existence.</htmltext>
<tokenext>I am surprised that nobody has mentioned it , but what about a server running AFS [ wikipedia.org ] ( Andrew File System ) .
It has some great features : Scalable - you can add as many servers as you wantSecure - it uses kerberos by defaultFast - local caches are kept until another client needs them.Cross platform - openAFS [ wikipedia.org ] supports pretty much every platform in existence .</tokentext>
<sentencetext>I am surprised that nobody has mentioned it, but what about a server running AFS [wikipedia.org] (Andrew File System).
It has some great features: Scalable - you can add as many servers as you wantSecure - it uses kerberos by defaultFast - local caches are kept until another client needs them.Cross platform - openAFS [wikipedia.org] supports pretty much every platform in existence.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542756</id>
	<title>Create different partitions on external drive</title>
	<author>MirzaD</author>
	<datestamp>1261651860000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>Create different partitions on external drive, one for example EXT3 and other FAT32. EXT3 would be large and FAT32 would be very small couple of megabytes. On smaller partition you would have EXT3 drivers for Windows machines. With this you would be able to access EXT3 from any machine.

You could also try different file systems in same way.</htmltext>
<tokenext>Create different partitions on external drive , one for example EXT3 and other FAT32 .
EXT3 would be large and FAT32 would be very small couple of megabytes .
On smaller partition you would have EXT3 drivers for Windows machines .
With this you would be able to access EXT3 from any machine .
You could also try different file systems in same way .</tokentext>
<sentencetext>Create different partitions on external drive, one for example EXT3 and other FAT32.
EXT3 would be large and FAT32 would be very small couple of megabytes.
On smaller partition you would have EXT3 drivers for Windows machines.
With this you would be able to access EXT3 from any machine.
You could also try different file systems in same way.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540916</id>
	<title>Re:Windows Filesystem Support</title>
	<author>DJRumpy</author>
	<datestamp>1259763720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I think Windows FS support is so bad simply because there isn't a lot of need for it given that they are a market leader. It's more of a need for folks like Linux and OS X to adapt to the market leader than the other way around. On top of that, MS has never been overly accepting of non-MS formats. They either buy them out and make them their own, or try to drive them to extinction. To their point of view, it simply doesn't benefit MS if Windows had a lot of FS support built in that made it potentially easier to move to another OS. In a weird sort of way, I can understand their approach as it make sense given where they started, and the market share they hold now.</p><p>Linux on the other hand, benefits greatly from a wide array of File Systems. It's one of the strengths that makes it a nice alternative in a mixed computing environment. Linux alone should have been a lesson to MS that it isn't always counter productive to be more open.</p></htmltext>
<tokenext>I think Windows FS support is so bad simply because there is n't a lot of need for it given that they are a market leader .
It 's more of a need for folks like Linux and OS X to adapt to the market leader than the other way around .
On top of that , MS has never been overly accepting of non-MS formats .
They either buy them out and make them their own , or try to drive them to extinction .
To their point of view , it simply does n't benefit MS if Windows had a lot of FS support built in that made it potentially easier to move to another OS .
In a weird sort of way , I can understand their approach as it make sense given where they started , and the market share they hold now.Linux on the other hand , benefits greatly from a wide array of File Systems .
It 's one of the strengths that makes it a nice alternative in a mixed computing environment .
Linux alone should have been a lesson to MS that it is n't always counter productive to be more open .</tokentext>
<sentencetext>I think Windows FS support is so bad simply because there isn't a lot of need for it given that they are a market leader.
It's more of a need for folks like Linux and OS X to adapt to the market leader than the other way around.
On top of that, MS has never been overly accepting of non-MS formats.
They either buy them out and make them their own, or try to drive them to extinction.
To their point of view, it simply doesn't benefit MS if Windows had a lot of FS support built in that made it potentially easier to move to another OS.
In a weird sort of way, I can understand their approach as it make sense given where they started, and the market share they hold now.Linux on the other hand, benefits greatly from a wide array of File Systems.
It's one of the strengths that makes it a nice alternative in a mixed computing environment.
Linux alone should have been a lesson to MS that it isn't always counter productive to be more open.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540568</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541224</id>
	<title>Re:The best is...</title>
	<author>Kr4u53</author>
	<datestamp>1259767200000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Well, at the least, it doesn't cost you an arm and a leg.</htmltext>
<tokenext>Well , at the least , it does n't cost you an arm and a leg .</tokentext>
<sentencetext>Well, at the least, it doesn't cost you an arm and a leg.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540138</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540560</id>
	<title>ZFS, ZFS, ZFS</title>
	<author>Anonymous</author>
	<datestamp>1259760420000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Enough said, next topic.</p></htmltext>
<tokenext>Enough said , next topic .</tokentext>
<sentencetext>Enough said, next topic.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541478</id>
	<title>FreeNAS is the was to go (was Re:I wouldn't....)</title>
	<author>Anonymous</author>
	<datestamp>1259771160000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>This is the perfect application for FreeNAS. In additional to all the benefits listed above, you've got the options of using rsync to maintain your off-site drive.</p></htmltext>
<tokenext>This is the perfect application for FreeNAS .
In additional to all the benefits listed above , you 've got the options of using rsync to maintain your off-site drive .</tokentext>
<sentencetext>This is the perfect application for FreeNAS.
In additional to all the benefits listed above, you've got the options of using rsync to maintain your off-site drive.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539912</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542454</id>
	<title>For where your treasure is...</title>
	<author>gottabeme</author>
	<datestamp>1261687740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>...there your heart is also.</p><p>Just something to think about.<nobr> <wbr></nobr>:)</p></htmltext>
<tokenext>...there your heart is also.Just something to think about .
: )</tokentext>
<sentencetext>...there your heart is also.Just something to think about.
:)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541890</id>
	<title>NTFS3G</title>
	<author>Anonymous</author>
	<datestamp>1259777280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>NTFS3G for Linux seems to work perfectly for NTFS file systems (read AND write); and, unless you're creating ISO images of your raw DVD video, the VIDEO\_TS folders should have files that are just under 1GB each (for DVD filesystem compatibility), making FAT32 usable (or are you saving raw capture from a video camera, making huge uncompressed files that are &gt;4GB?)</p></htmltext>
<tokenext>NTFS3G for Linux seems to work perfectly for NTFS file systems ( read AND write ) ; and , unless you 're creating ISO images of your raw DVD video , the VIDEO \ _TS folders should have files that are just under 1GB each ( for DVD filesystem compatibility ) , making FAT32 usable ( or are you saving raw capture from a video camera , making huge uncompressed files that are &gt; 4GB ?
)</tokentext>
<sentencetext>NTFS3G for Linux seems to work perfectly for NTFS file systems (read AND write); and, unless you're creating ISO images of your raw DVD video, the VIDEO\_TS folders should have files that are just under 1GB each (for DVD filesystem compatibility), making FAT32 usable (or are you saving raw capture from a video camera, making huge uncompressed files that are &gt;4GB?
)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30545240</id>
	<title>Which File System?</title>
	<author>olsonde</author>
	<datestamp>1261678920000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>I'd choose the file system based on the system I plan to Host it on. If the host is Windows, I'd go with NTFS. If the Host is Linux, I'd go with EXT2. Regardless of the hosting system and the drive format, you want to make sure you can access the shared contents of the drive from your other systems on your home network. Using this approach, you won't need to worry about third-party drivers.</p></htmltext>
<tokenext>I 'd choose the file system based on the system I plan to Host it on .
If the host is Windows , I 'd go with NTFS .
If the Host is Linux , I 'd go with EXT2 .
Regardless of the hosting system and the drive format , you want to make sure you can access the shared contents of the drive from your other systems on your home network .
Using this approach , you wo n't need to worry about third-party drivers .</tokentext>
<sentencetext>I'd choose the file system based on the system I plan to Host it on.
If the host is Windows, I'd go with NTFS.
If the Host is Linux, I'd go with EXT2.
Regardless of the hosting system and the drive format, you want to make sure you can access the shared contents of the drive from your other systems on your home network.
Using this approach, you won't need to worry about third-party drivers.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30554868</id>
	<title>use ntfs-3g in linux for 99\% support</title>
	<author>Anonymous</author>
	<datestamp>1261822440000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>ntfs-3g is fine for everyday use now. you can write and everything, with no silly limitations.<br>The only caveat that I know about is that occasionally (for example if the disk was not<br>cleanly unmounted) you might need to connect the disk to a windows pc once or twice to<br>let windows 'fix' it.</p><p>really, my brother and I have been using it for a couple of years now with no problems, and<br>it is the standard way of mounting ntfs partitions in any modern linux distro.</p><p>having said that, if your WD thing supports ext3, i would say try the 'ext2 ifs' driver for windows.<br>at <a href="http://www.fs-driver.org/" title="fs-driver.org" rel="nofollow">http://www.fs-driver.org/</a> [fs-driver.org]<br>it is good enough for read access in windows.<br>and it works ok for writing though in my experience it occasionally refuses to delete a file.</p></htmltext>
<tokenext>ntfs-3g is fine for everyday use now .
you can write and everything , with no silly limitations.The only caveat that I know about is that occasionally ( for example if the disk was notcleanly unmounted ) you might need to connect the disk to a windows pc once or twice tolet windows 'fix ' it.really , my brother and I have been using it for a couple of years now with no problems , andit is the standard way of mounting ntfs partitions in any modern linux distro.having said that , if your WD thing supports ext3 , i would say try the 'ext2 ifs ' driver for windows.at http : //www.fs-driver.org/ [ fs-driver.org ] it is good enough for read access in windows.and it works ok for writing though in my experience it occasionally refuses to delete a file .</tokentext>
<sentencetext>ntfs-3g is fine for everyday use now.
you can write and everything, with no silly limitations.The only caveat that I know about is that occasionally (for example if the disk was notcleanly unmounted) you might need to connect the disk to a windows pc once or twice tolet windows 'fix' it.really, my brother and I have been using it for a couple of years now with no problems, andit is the standard way of mounting ntfs partitions in any modern linux distro.having said that, if your WD thing supports ext3, i would say try the 'ext2 ifs' driver for windows.at http://www.fs-driver.org/ [fs-driver.org]it is good enough for read access in windows.and it works ok for writing though in my experience it occasionally refuses to delete a file.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540456</id>
	<title>Re:NTFS</title>
	<author>Anonymous</author>
	<datestamp>1259759700000</datestamp>
	<modclass>None</modclass>
	<modscore>-1</modscore>
	<htmltext><p>&gt; I use NTFS on both my machines (Win/OS X/Linux) without any problems.<br>&gt; NTFS-3G is also available for Linux.</p><p>For now. While M$ wants it so.</p><p>Apparently, like the dog in the fable, you only care for the food...</p><p>---</p><p>--Boy, you sure look well fed. What's the secret?<br>--No secret. I got me an owner. It gives me food, I just pay with some little errands... Come with me and I'll show you the master. But first put on this collar...<br>--What for?<br>--Sometimes the master wants me to stay in a place, so he ties a leash to my collar.<br>--WTF???!? -- said the wolf.</p></htmltext>
<tokenext>&gt; I use NTFS on both my machines ( Win/OS X/Linux ) without any problems. &gt; NTFS-3G is also available for Linux.For now .
While M $ wants it so.Apparently , like the dog in the fable , you only care for the food...-----Boy , you sure look well fed .
What 's the secret ? --No secret .
I got me an owner .
It gives me food , I just pay with some little errands... Come with me and I 'll show you the master .
But first put on this collar...--What for ? --Sometimes the master wants me to stay in a place , so he ties a leash to my collar.--WTF ? ? ? ! ?
-- said the wolf .</tokentext>
<sentencetext>&gt; I use NTFS on both my machines (Win/OS X/Linux) without any problems.&gt; NTFS-3G is also available for Linux.For now.
While M$ wants it so.Apparently, like the dog in the fable, you only care for the food...-----Boy, you sure look well fed.
What's the secret?--No secret.
I got me an owner.
It gives me food, I just pay with some little errands... Come with me and I'll show you the master.
But first put on this collar...--What for?--Sometimes the master wants me to stay in a place, so he ties a leash to my collar.--WTF???!?
-- said the wolf.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539824</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542172</id>
	<title>Re:Words of caution</title>
	<author>StarsAreAlsoFire</author>
	<datestamp>1259781540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Nope, no better. Windows 7 just likes to tell you that 'Disk cannot be removed: A file is open on one of the eighty thousand services and programs which windows starts at boot time. Please figure out which poorly written piece of shit failed to remove the file lock which it shouldn't have registered in the first place from the text file which you attached to an email sent three days ago, and try again.'<br><br>Only, were Windows even remotely close to that helpful I would have known to close Outlook. Though Outlook is FAR from the only program to lock files which it has zero business locking, and then failing to remove said locks.<br><br>I will admit that I'm surprised that WinXP enabled write-caching by default on a USB drive. Not because that would be an incredibly stupid default (Ha!), but because I thought I remembered having to turn it ON for a scratch drive a while ago.</htmltext>
<tokenext>Nope , no better .
Windows 7 just likes to tell you that 'Disk can not be removed : A file is open on one of the eighty thousand services and programs which windows starts at boot time .
Please figure out which poorly written piece of shit failed to remove the file lock which it should n't have registered in the first place from the text file which you attached to an email sent three days ago , and try again .
'Only , were Windows even remotely close to that helpful I would have known to close Outlook .
Though Outlook is FAR from the only program to lock files which it has zero business locking , and then failing to remove said locks.I will admit that I 'm surprised that WinXP enabled write-caching by default on a USB drive .
Not because that would be an incredibly stupid default ( Ha !
) , but because I thought I remembered having to turn it ON for a scratch drive a while ago .</tokentext>
<sentencetext>Nope, no better.
Windows 7 just likes to tell you that 'Disk cannot be removed: A file is open on one of the eighty thousand services and programs which windows starts at boot time.
Please figure out which poorly written piece of shit failed to remove the file lock which it shouldn't have registered in the first place from the text file which you attached to an email sent three days ago, and try again.
'Only, were Windows even remotely close to that helpful I would have known to close Outlook.
Though Outlook is FAR from the only program to lock files which it has zero business locking, and then failing to remove said locks.I will admit that I'm surprised that WinXP enabled write-caching by default on a USB drive.
Not because that would be an incredibly stupid default (Ha!
), but because I thought I remembered having to turn it ON for a scratch drive a while ago.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540714</id>
	<title>Re:I wouldn't....</title>
	<author>Anonymous</author>
	<datestamp>1259761740000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>My personal solution is to partition my external storage devices. the first, ~10GB partition is ntfs, the second, big partition is ext3. All my computers are linux, so If I ever need to share data of that harddisk with a windows-users and network would be to complicated, I can just move the needed data to the ntfs-partition.<br>Storing data on an usb-storage through ntfs-3g is just no fun at all.</p></htmltext>
<tokenext>My personal solution is to partition my external storage devices .
the first , ~ 10GB partition is ntfs , the second , big partition is ext3 .
All my computers are linux , so If I ever need to share data of that harddisk with a windows-users and network would be to complicated , I can just move the needed data to the ntfs-partition.Storing data on an usb-storage through ntfs-3g is just no fun at all .</tokentext>
<sentencetext>My personal solution is to partition my external storage devices.
the first, ~10GB partition is ntfs, the second, big partition is ext3.
All my computers are linux, so If I ever need to share data of that harddisk with a windows-users and network would be to complicated, I can just move the needed data to the ntfs-partition.Storing data on an usb-storage through ntfs-3g is just no fun at all.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539912</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541070</id>
	<title>Re:Words of caution</title>
	<author>PiSkyHi</author>
	<datestamp>1259765460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I had problems when I tried to dismount a USB drive recently, it wasn't the filesystem choice that got me though, it was the sharp corner of the coffee table.</htmltext>
<tokenext>I had problems when I tried to dismount a USB drive recently , it was n't the filesystem choice that got me though , it was the sharp corner of the coffee table .</tokentext>
<sentencetext>I had problems when I tried to dismount a USB drive recently, it wasn't the filesystem choice that got me though, it was the sharp corner of the coffee table.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30566664</id>
	<title>Re:Replace the WD TV thing</title>
	<author>Anonymous</author>
	<datestamp>1261918140000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Well that's not exactly true.  An Atom N280 paired with 945 doesn't have the horsepower to playback 1080p and maybe jerky 720p - but a WD TV Live can. Unless you go for a ION chipset, but then you're in the $300 range where as with the WD TV you're closer to $100.</p></htmltext>
<tokenext>Well that 's not exactly true .
An Atom N280 paired with 945 does n't have the horsepower to playback 1080p and maybe jerky 720p - but a WD TV Live can .
Unless you go for a ION chipset , but then you 're in the $ 300 range where as with the WD TV you 're closer to $ 100 .</tokentext>
<sentencetext>Well that's not exactly true.
An Atom N280 paired with 945 doesn't have the horsepower to playback 1080p and maybe jerky 720p - but a WD TV Live can.
Unless you go for a ION chipset, but then you're in the $300 range where as with the WD TV you're closer to $100.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540242</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540556</id>
	<title>I've been there - NTFS all the way</title>
	<author>GoatSucker</author>
	<datestamp>1259760420000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>I have been through exactly the same thing, and NTFS is the way to go. My main machine is a Mac, but I format all my USB drives as NFTS (through NTFS-3G FUSE). Though this is slower than formating as FAT or HFS+, it is so much more portable, it wins out.

Windows machines can read them.
My WD TV box can read them.
My Mac can read them.
They can store more than 4G per file (indeed, I have all my DVD isos on them).
Ok, they can't be read on other macs without installing NTFS-3G, but I've yet to need that.
For me, I've never had any problem with  NTFS-3G , it's extremely reliable.</htmltext>
<tokenext>I have been through exactly the same thing , and NTFS is the way to go .
My main machine is a Mac , but I format all my USB drives as NFTS ( through NTFS-3G FUSE ) .
Though this is slower than formating as FAT or HFS + , it is so much more portable , it wins out .
Windows machines can read them .
My WD TV box can read them .
My Mac can read them .
They can store more than 4G per file ( indeed , I have all my DVD isos on them ) .
Ok , they ca n't be read on other macs without installing NTFS-3G , but I 've yet to need that .
For me , I 've never had any problem with NTFS-3G , it 's extremely reliable .</tokentext>
<sentencetext>I have been through exactly the same thing, and NTFS is the way to go.
My main machine is a Mac, but I format all my USB drives as NFTS (through NTFS-3G FUSE).
Though this is slower than formating as FAT or HFS+, it is so much more portable, it wins out.
Windows machines can read them.
My WD TV box can read them.
My Mac can read them.
They can store more than 4G per file (indeed, I have all my DVD isos on them).
Ok, they can't be read on other macs without installing NTFS-3G, but I've yet to need that.
For me, I've never had any problem with  NTFS-3G , it's extremely reliable.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541114</id>
	<title>Please read this</title>
	<author>Anonymous</author>
	<datestamp>1259766000000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p>Dear AP,

</p><p>I was pondering with a very similiar problem two years ago, when I bought my first terabyte-class external USB hard drive to my home server (old 800 MHz Duron). I was thinking exactly like you are thinking now, and decided FAT-32 would be the way to go. <b>MISTAKE.</b> Four important things stand out, that I want you to read:

</p><ol> <li>You never really transfer that drive. Much less than you think. Chances are more than 99\% of their lifetime they will be sitting hooked to one computer, never really being moved; portability is just another nice extra feature that you hardly ever use. During the two years I have switched my drives a couple of times between the desktop machine and the server, both of which run Linux as main OS. I have never ever taken any of these drives outside of my home.</li><li>4 GB limitation is really bad! Most DVD ISOs are bigger that that. An hour of HD video in state-of-the-art H.264 is more than 4 GB. And rest assured, when you have the space and facilities to accquire gigabyte-class multimedia, the temptation will be there. As BluRay becomes the new DVD, maybe you want to RIP your fav. movies to your hard drive for quick access? NO WAY with FAT-32!</li><li>Lack of UNIX parameter support. Okay, so you just want to store back-ups? Okay.. Remember than FAT-32 doesn't support symbolic links, file ownership, user/group/others access permissions, file name character case (in Microsoft Windows, "Soviet Union" equals to "soviet union"; WILL result in a conflict when copying data from UNIX filesystems!). This information is LOST, unless you use some container format like tar (but remember the 4GB limit again). These little things are a) very helpful everyday things, value of which you realize only after loosing them (e.g. any file on extfs can be replaced/virtualized without moving files around; it can even point to a non-existstent file! And all works seamlessly, as long as the program understands symbolic links; now how valuable is that?), and b) what makes your UNIX fs work. The value of your backups is lower if they dont work "out of the box", e.g. data is lost when transfering to FAT-32. I mean, you just have a chance to save so much hassle there.. When needed, you can NFS-mount the filesystem (and its free space and contents) to your local machine from your drive, and everything works transparently to BOTH Windows and Linux (the properties of FAT-32 are a small subset of those of extfs.)</li><li>Acccess speed. Ext3 and Ext4 or just about any 21st century UNIX fs are lightyears ahead of the archaic FAT in data structures. E.g. if I "ls" a big directory on my only FAT-32 drive, it is SLOW! You can see the entries being fetched one by one. Whereas, if I do the same in a similiarly-sized directory on the ext3, the files appear immediately! Access is almous immediate even over NFS mount in LAN. This comes handy, rest assured.</li></ol><p> Okay, those are my four vocal points. They could be in any order, because all of them are equally important reasons NOT to choose FAT-32! As it happened, after using the 0.5TB drive for 6 months with FAT-32, I bought more space (a new drive). This time there was no question about the filesystem. I made a small, few-sector long 200 MB FAT-32 partition to the beginning of the drive and downloaded all the latest Win32 EXT2 drivers there from different vendors, just for the really unplausible situation that I would ever want to mount these drives in Windows. Then I just made the rest Ext3. And, I am REALLY satisfied with the decision! Ext3 just work so sparklingly faster and better with Linux than FAT-32 ever does. Since then I have bought one more drive and did the same 200MB + 1TB thing. I will probably never use these drives in Windows, but it gives me a warm feeling to the heart that there's always a way if I should, even if the computer doesn't have an Internet connection.

</p><p>Oh, one thing I forgot to mention: get a file server! It makes your life so much easier. Nowadays I am running a desktop computer with a 60 GB SSD drive and no HDD at a</p></htmltext>
<tokenext>Dear AP , I was pondering with a very similiar problem two years ago , when I bought my first terabyte-class external USB hard drive to my home server ( old 800 MHz Duron ) .
I was thinking exactly like you are thinking now , and decided FAT-32 would be the way to go .
MISTAKE. Four important things stand out , that I want you to read : You never really transfer that drive .
Much less than you think .
Chances are more than 99 \ % of their lifetime they will be sitting hooked to one computer , never really being moved ; portability is just another nice extra feature that you hardly ever use .
During the two years I have switched my drives a couple of times between the desktop machine and the server , both of which run Linux as main OS .
I have never ever taken any of these drives outside of my home.4 GB limitation is really bad !
Most DVD ISOs are bigger that that .
An hour of HD video in state-of-the-art H.264 is more than 4 GB .
And rest assured , when you have the space and facilities to accquire gigabyte-class multimedia , the temptation will be there .
As BluRay becomes the new DVD , maybe you want to RIP your fav .
movies to your hard drive for quick access ?
NO WAY with FAT-32 ! Lack of UNIX parameter support .
Okay , so you just want to store back-ups ?
Okay.. Remember than FAT-32 does n't support symbolic links , file ownership , user/group/others access permissions , file name character case ( in Microsoft Windows , " Soviet Union " equals to " soviet union " ; WILL result in a conflict when copying data from UNIX filesystems ! ) .
This information is LOST , unless you use some container format like tar ( but remember the 4GB limit again ) .
These little things are a ) very helpful everyday things , value of which you realize only after loosing them ( e.g .
any file on extfs can be replaced/virtualized without moving files around ; it can even point to a non-existstent file !
And all works seamlessly , as long as the program understands symbolic links ; now how valuable is that ?
) , and b ) what makes your UNIX fs work .
The value of your backups is lower if they dont work " out of the box " , e.g .
data is lost when transfering to FAT-32 .
I mean , you just have a chance to save so much hassle there.. When needed , you can NFS-mount the filesystem ( and its free space and contents ) to your local machine from your drive , and everything works transparently to BOTH Windows and Linux ( the properties of FAT-32 are a small subset of those of extfs .
) Acccess speed .
Ext3 and Ext4 or just about any 21st century UNIX fs are lightyears ahead of the archaic FAT in data structures .
E.g. if I " ls " a big directory on my only FAT-32 drive , it is SLOW !
You can see the entries being fetched one by one .
Whereas , if I do the same in a similiarly-sized directory on the ext3 , the files appear immediately !
Access is almous immediate even over NFS mount in LAN .
This comes handy , rest assured .
Okay , those are my four vocal points .
They could be in any order , because all of them are equally important reasons NOT to choose FAT-32 !
As it happened , after using the 0.5TB drive for 6 months with FAT-32 , I bought more space ( a new drive ) .
This time there was no question about the filesystem .
I made a small , few-sector long 200 MB FAT-32 partition to the beginning of the drive and downloaded all the latest Win32 EXT2 drivers there from different vendors , just for the really unplausible situation that I would ever want to mount these drives in Windows .
Then I just made the rest Ext3 .
And , I am REALLY satisfied with the decision !
Ext3 just work so sparklingly faster and better with Linux than FAT-32 ever does .
Since then I have bought one more drive and did the same 200MB + 1TB thing .
I will probably never use these drives in Windows , but it gives me a warm feeling to the heart that there 's always a way if I should , even if the computer does n't have an Internet connection .
Oh , one thing I forgot to mention : get a file server !
It makes your life so much easier .
Nowadays I am running a desktop computer with a 60 GB SSD drive and no HDD at a</tokentext>
<sentencetext>Dear AP,

I was pondering with a very similiar problem two years ago, when I bought my first terabyte-class external USB hard drive to my home server (old 800 MHz Duron).
I was thinking exactly like you are thinking now, and decided FAT-32 would be the way to go.
MISTAKE. Four important things stand out, that I want you to read:

 You never really transfer that drive.
Much less than you think.
Chances are more than 99\% of their lifetime they will be sitting hooked to one computer, never really being moved; portability is just another nice extra feature that you hardly ever use.
During the two years I have switched my drives a couple of times between the desktop machine and the server, both of which run Linux as main OS.
I have never ever taken any of these drives outside of my home.4 GB limitation is really bad!
Most DVD ISOs are bigger that that.
An hour of HD video in state-of-the-art H.264 is more than 4 GB.
And rest assured, when you have the space and facilities to accquire gigabyte-class multimedia, the temptation will be there.
As BluRay becomes the new DVD, maybe you want to RIP your fav.
movies to your hard drive for quick access?
NO WAY with FAT-32!Lack of UNIX parameter support.
Okay, so you just want to store back-ups?
Okay.. Remember than FAT-32 doesn't support symbolic links, file ownership, user/group/others access permissions, file name character case (in Microsoft Windows, "Soviet Union" equals to "soviet union"; WILL result in a conflict when copying data from UNIX filesystems!).
This information is LOST, unless you use some container format like tar (but remember the 4GB limit again).
These little things are a) very helpful everyday things, value of which you realize only after loosing them (e.g.
any file on extfs can be replaced/virtualized without moving files around; it can even point to a non-existstent file!
And all works seamlessly, as long as the program understands symbolic links; now how valuable is that?
), and b) what makes your UNIX fs work.
The value of your backups is lower if they dont work "out of the box", e.g.
data is lost when transfering to FAT-32.
I mean, you just have a chance to save so much hassle there.. When needed, you can NFS-mount the filesystem (and its free space and contents) to your local machine from your drive, and everything works transparently to BOTH Windows and Linux (the properties of FAT-32 are a small subset of those of extfs.
)Acccess speed.
Ext3 and Ext4 or just about any 21st century UNIX fs are lightyears ahead of the archaic FAT in data structures.
E.g. if I "ls" a big directory on my only FAT-32 drive, it is SLOW!
You can see the entries being fetched one by one.
Whereas, if I do the same in a similiarly-sized directory on the ext3, the files appear immediately!
Access is almous immediate even over NFS mount in LAN.
This comes handy, rest assured.
Okay, those are my four vocal points.
They could be in any order, because all of them are equally important reasons NOT to choose FAT-32!
As it happened, after using the 0.5TB drive for 6 months with FAT-32, I bought more space (a new drive).
This time there was no question about the filesystem.
I made a small, few-sector long 200 MB FAT-32 partition to the beginning of the drive and downloaded all the latest Win32 EXT2 drivers there from different vendors, just for the really unplausible situation that I would ever want to mount these drives in Windows.
Then I just made the rest Ext3.
And, I am REALLY satisfied with the decision!
Ext3 just work so sparklingly faster and better with Linux than FAT-32 ever does.
Since then I have bought one more drive and did the same 200MB + 1TB thing.
I will probably never use these drives in Windows, but it gives me a warm feeling to the heart that there's always a way if I should, even if the computer doesn't have an Internet connection.
Oh, one thing I forgot to mention: get a file server!
It makes your life so much easier.
Nowadays I am running a desktop computer with a 60 GB SSD drive and no HDD at a</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540530</id>
	<title>Re:Words of caution</title>
	<author>okar</author>
	<datestamp>1259760180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>This is what must have happened to one of my external drives. It took ages to recover &gt;500 GB of data to another drive, it also made me very nervous since I was considering moving all my data to external drives.. Now I know that to look out for.</p></htmltext>
<tokenext>This is what must have happened to one of my external drives .
It took ages to recover &gt; 500 GB of data to another drive , it also made me very nervous since I was considering moving all my data to external drives.. Now I know that to look out for .</tokentext>
<sentencetext>This is what must have happened to one of my external drives.
It took ages to recover &gt;500 GB of data to another drive, it also made me very nervous since I was considering moving all my data to external drives.. Now I know that to look out for.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541708</id>
	<title>after you pick a file system..</title>
	<author>Anonymous</author>
	<datestamp>1259774160000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I use a similar backup system and backup schedule to an external USB drive as well.  I used NTFS for the filesystem but I mount Truecrypt volumes on that file system to hold my backup data.  If the drive fails and I have to send it back for warranty purposes or if someone steals it, at least I know my backups were resonably protected with some type of encryption.  Another benefit is I can move my entire backup set to a new drive by simply copying that truecrypt volume file to the new destination.</p></htmltext>
<tokenext>I use a similar backup system and backup schedule to an external USB drive as well .
I used NTFS for the filesystem but I mount Truecrypt volumes on that file system to hold my backup data .
If the drive fails and I have to send it back for warranty purposes or if someone steals it , at least I know my backups were resonably protected with some type of encryption .
Another benefit is I can move my entire backup set to a new drive by simply copying that truecrypt volume file to the new destination .</tokentext>
<sentencetext>I use a similar backup system and backup schedule to an external USB drive as well.
I used NTFS for the filesystem but I mount Truecrypt volumes on that file system to hold my backup data.
If the drive fails and I have to send it back for warranty purposes or if someone steals it, at least I know my backups were resonably protected with some type of encryption.
Another benefit is I can move my entire backup set to a new drive by simply copying that truecrypt volume file to the new destination.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540978</id>
	<title>Why all those ext3 recommendations?</title>
	<author>Anonymous</author>
	<datestamp>1259764260000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext>I see quite many people here recommending ext3. Oh my. ext3 <i>sucks</i> for large files,<br>
which is exactly what the submitter wants to use his setup for. Look into the crazy structures<br>
("double indirect blocks") it uses. He should go with an FS that has sane data structures with<br>
files &gt;&gt;4GB.<br>
<br>
That kills most of the choices and leaves XFS, ext4, ZFS (only worth it if <i>not</i> used via FUSE,<br>
i.e. in Solaris), and a couple more obscure ones.
<br>
I second the "forget OS portability, use a server" suggestion. There's great low-power, low-cost<br>
hardware for this nowadays.</htmltext>
<tokenext>I see quite many people here recommending ext3 .
Oh my .
ext3 sucks for large files , which is exactly what the submitter wants to use his setup for .
Look into the crazy structures ( " double indirect blocks " ) it uses .
He should go with an FS that has sane data structures with files &gt; &gt; 4GB .
That kills most of the choices and leaves XFS , ext4 , ZFS ( only worth it if not used via FUSE , i.e .
in Solaris ) , and a couple more obscure ones .
I second the " forget OS portability , use a server " suggestion .
There 's great low-power , low-cost hardware for this nowadays .</tokentext>
<sentencetext>I see quite many people here recommending ext3.
Oh my.
ext3 sucks for large files,
which is exactly what the submitter wants to use his setup for.
Look into the crazy structures
("double indirect blocks") it uses.
He should go with an FS that has sane data structures with
files &gt;&gt;4GB.
That kills most of the choices and leaves XFS, ext4, ZFS (only worth it if not used via FUSE,
i.e.
in Solaris), and a couple more obscure ones.
I second the "forget OS portability, use a server" suggestion.
There's great low-power, low-cost
hardware for this nowadays.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542136</id>
	<title>Hybrid? FAT32 and [your-choice-of-fs-here]</title>
	<author>corychristison</author>
	<datestamp>1259781060000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext><p>I know this comment will get lost in the sea of other comments, but my recommendation to you would be a hybrid solution.</p><p>Create a small partition (1GB would be overkill) and format it FAT32.<br>Create another partition for the rest of the drive (or however you please) with your choice of FS (I prefer XFS, personally).</p><p>Store the drivers(/utilties) for the FS you chose and store them on the FAT32 drive.<br>Some popular drivers/utilties for Windows are:<br>ext2fsd for EXT2 - <a href="http://sourceforge.net/projects/ext2fsd/" title="sourceforge.net">http://sourceforge.net/projects/ext2fsd/</a> [sourceforge.net]<br>rfstool for ReiserFS - <a href="http://freshmeat.net/projects/rfstool/" title="freshmeat.net">http://freshmeat.net/projects/rfstool/</a> [freshmeat.net]<br>ltools for EXT2/EXT2/ReiserFS - <a href="http://www2.hs-esslingen.de/~zimmerma/software/ltools.html/" title="hs-esslingen.de">http://www2.hs-esslingen.de/~zimmerma/software/ltools.html/</a> [hs-esslingen.de]<br>and so on and so forth (a simple google for "[FS] Windows Compatibility" usually works.)</p><p>Just my thoughts.<nobr> <wbr></nobr>:-)</p></htmltext>
<tokenext>I know this comment will get lost in the sea of other comments , but my recommendation to you would be a hybrid solution.Create a small partition ( 1GB would be overkill ) and format it FAT32.Create another partition for the rest of the drive ( or however you please ) with your choice of FS ( I prefer XFS , personally ) .Store the drivers ( /utilties ) for the FS you chose and store them on the FAT32 drive.Some popular drivers/utilties for Windows are : ext2fsd for EXT2 - http : //sourceforge.net/projects/ext2fsd/ [ sourceforge.net ] rfstool for ReiserFS - http : //freshmeat.net/projects/rfstool/ [ freshmeat.net ] ltools for EXT2/EXT2/ReiserFS - http : //www2.hs-esslingen.de/ ~ zimmerma/software/ltools.html/ [ hs-esslingen.de ] and so on and so forth ( a simple google for " [ FS ] Windows Compatibility " usually works .
) Just my thoughts .
: - )</tokentext>
<sentencetext>I know this comment will get lost in the sea of other comments, but my recommendation to you would be a hybrid solution.Create a small partition (1GB would be overkill) and format it FAT32.Create another partition for the rest of the drive (or however you please) with your choice of FS (I prefer XFS, personally).Store the drivers(/utilties) for the FS you chose and store them on the FAT32 drive.Some popular drivers/utilties for Windows are:ext2fsd for EXT2 - http://sourceforge.net/projects/ext2fsd/ [sourceforge.net]rfstool for ReiserFS - http://freshmeat.net/projects/rfstool/ [freshmeat.net]ltools for EXT2/EXT2/ReiserFS - http://www2.hs-esslingen.de/~zimmerma/software/ltools.html/ [hs-esslingen.de]and so on and so forth (a simple google for "[FS] Windows Compatibility" usually works.
)Just my thoughts.
:-)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541422</id>
	<title>Ambiguous??</title>
	<author>Anonymous</author>
	<datestamp>1259770320000</datestamp>
	<modclass>Funny</modclass>
	<modscore>1</modscore>
	<htmltext>You're so torn between formats, why don't you just partition the external drive with like ten partitions and format each one with a different format -- that way you don't have to choose!</htmltext>
<tokenext>You 're so torn between formats , why do n't you just partition the external drive with like ten partitions and format each one with a different format -- that way you do n't have to choose !</tokentext>
<sentencetext>You're so torn between formats, why don't you just partition the external drive with like ten partitions and format each one with a different format -- that way you don't have to choose!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542068</id>
	<title>Avoid USB attached storage. (Re:Words of caution)</title>
	<author>KonoWatakushi</author>
	<datestamp>1259780040000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>The fundamental problem lies in USB bridge chips which do not properly implement the cache management commands.  Others have replied that you need to disable the write cache, and while that would be a solution, it is often impossible.  Even with bridge chips that do support the cache disable command, some hard drives will not honor it anyway.</p><p>Most USB bridges simply lie about when data has been written, which makes it very difficult for a filesystem on top of it to make any guarantees.  While it may not happen often, this can have disastrous results, as you have seen.</p><p>The copy on write nature of ZFS left it especially vulnerable to broken USB storage, and could easily leave you with a corrupted pool requiring manual intervention and a bit of luck to recover.  Thankfully, the recent bits address this, and ZFS is now the only filesystem that I would trust on top of USB storage.  Most other filesystems will survive without incident, but at the cost of some silent data corruption.</p></htmltext>
<tokenext>The fundamental problem lies in USB bridge chips which do not properly implement the cache management commands .
Others have replied that you need to disable the write cache , and while that would be a solution , it is often impossible .
Even with bridge chips that do support the cache disable command , some hard drives will not honor it anyway.Most USB bridges simply lie about when data has been written , which makes it very difficult for a filesystem on top of it to make any guarantees .
While it may not happen often , this can have disastrous results , as you have seen.The copy on write nature of ZFS left it especially vulnerable to broken USB storage , and could easily leave you with a corrupted pool requiring manual intervention and a bit of luck to recover .
Thankfully , the recent bits address this , and ZFS is now the only filesystem that I would trust on top of USB storage .
Most other filesystems will survive without incident , but at the cost of some silent data corruption .</tokentext>
<sentencetext>The fundamental problem lies in USB bridge chips which do not properly implement the cache management commands.
Others have replied that you need to disable the write cache, and while that would be a solution, it is often impossible.
Even with bridge chips that do support the cache disable command, some hard drives will not honor it anyway.Most USB bridges simply lie about when data has been written, which makes it very difficult for a filesystem on top of it to make any guarantees.
While it may not happen often, this can have disastrous results, as you have seen.The copy on write nature of ZFS left it especially vulnerable to broken USB storage, and could easily leave you with a corrupted pool requiring manual intervention and a bit of luck to recover.
Thankfully, the recent bits address this, and ZFS is now the only filesystem that I would trust on top of USB storage.
Most other filesystems will survive without incident, but at the cost of some silent data corruption.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541296</id>
	<title>Re:IBM's HPFS</title>
	<author>Hamsterdan</author>
	<datestamp>1259768160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>2GiB max file size on HPFS.<br><br>Like it or not, NTFS is here to stay, and can be read by almost all modern OSes. (write support is available trough NTFS-3G on Linux &amp; OS X)</htmltext>
<tokenext>2GiB max file size on HPFS.Like it or not , NTFS is here to stay , and can be read by almost all modern OSes .
( write support is available trough NTFS-3G on Linux &amp; OS X )</tokentext>
<sentencetext>2GiB max file size on HPFS.Like it or not, NTFS is here to stay, and can be read by almost all modern OSes.
(write support is available trough NTFS-3G on Linux &amp; OS X)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540272</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540130</id>
	<title>Re:The solution..</title>
	<author>Anonymous</author>
	<datestamp>1259757300000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext>Irregardless is nonsense caused by confusion between the words irrespective and regardless.</htmltext>
<tokenext>Irregardless is nonsense caused by confusion between the words irrespective and regardless .</tokentext>
<sentencetext>Irregardless is nonsense caused by confusion between the words irrespective and regardless.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539926</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540428</id>
	<title>Re:The solution..</title>
	<author>SEAL</author>
	<datestamp>1259759400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Irregardless is nonsense caused by confusion between the words irrespective and regardless.</p></div><p>At least people generally follow the intended meaning.  Compare that to flammable, which came into use because people misunderstand "inflammable".</p></div>
	</htmltext>
<tokenext>Irregardless is nonsense caused by confusion between the words irrespective and regardless.At least people generally follow the intended meaning .
Compare that to flammable , which came into use because people misunderstand " inflammable " .</tokentext>
<sentencetext>Irregardless is nonsense caused by confusion between the words irrespective and regardless.At least people generally follow the intended meaning.
Compare that to flammable, which came into use because people misunderstand "inflammable".
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540130</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30550530</id>
	<title>Re:The solution..</title>
	<author>Hognoxious</author>
	<datestamp>1261749960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>Al != SN</p></div></blockquote><p>Aluminium isn't equal to sulphur nitride?</p></div>
	</htmltext>
<tokenext>Al ! = SNAluminium is n't equal to sulphur nitride ?</tokentext>
<sentencetext>Al != SNAluminium isn't equal to sulphur nitride?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540686</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30552246</id>
	<title>Re:NTFS</title>
	<author>Anonymous</author>
	<datestamp>1261774020000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I've used NTFS-3G for both Mac and Linux. It's been pretty successful so far. Just a heads up, you will need MacFUSE for the port of NTFS-3G on Mac to work.</p></htmltext>
<tokenext>I 've used NTFS-3G for both Mac and Linux .
It 's been pretty successful so far .
Just a heads up , you will need MacFUSE for the port of NTFS-3G on Mac to work .</tokentext>
<sentencetext>I've used NTFS-3G for both Mac and Linux.
It's been pretty successful so far.
Just a heads up, you will need MacFUSE for the port of NTFS-3G on Mac to work.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539824</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540346</id>
	<title>Why not use a  ReadyNAS device</title>
	<author>Anonymous</author>
	<datestamp>1259758860000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>2 disks,  redundancy, heck buy a cold spare HD and you will be protected better than two USB drives</p></htmltext>
<tokenext>2 disks , redundancy , heck buy a cold spare HD and you will be protected better than two USB drives</tokentext>
<sentencetext>2 disks,  redundancy, heck buy a cold spare HD and you will be protected better than two USB drives</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541234</id>
	<title>EXT4?</title>
	<author>Anonymous</author>
	<datestamp>1259767560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Why is no one recommending ext4? Because of it lacking windows support?

Is there any reason why ext4 should not be used in a simple raid5 server?</htmltext>
<tokenext>Why is no one recommending ext4 ?
Because of it lacking windows support ?
Is there any reason why ext4 should not be used in a simple raid5 server ?</tokentext>
<sentencetext>Why is no one recommending ext4?
Because of it lacking windows support?
Is there any reason why ext4 should not be used in a simple raid5 server?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539916</id>
	<title>ZFS, supported equally on your OSes</title>
	<author>Anonymous</author>
	<datestamp>1259755800000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext><p>Via FUSE you'll get consistent features and useability across all 3 OSes.  Of course moving zfs drives between those OSes isn't something I've tried, but in theory it should work fine.</p><p>Not what your asking for, but Id put a FBSD samba server up with ZFS drives.  You can still mount them on other OSes later if need be via FUSE.</p></htmltext>
<tokenext>Via FUSE you 'll get consistent features and useability across all 3 OSes .
Of course moving zfs drives between those OSes is n't something I 've tried , but in theory it should work fine.Not what your asking for , but Id put a FBSD samba server up with ZFS drives .
You can still mount them on other OSes later if need be via FUSE .</tokentext>
<sentencetext>Via FUSE you'll get consistent features and useability across all 3 OSes.
Of course moving zfs drives between those OSes isn't something I've tried, but in theory it should work fine.Not what your asking for, but Id put a FBSD samba server up with ZFS drives.
You can still mount them on other OSes later if need be via FUSE.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539824</id>
	<title>NTFS</title>
	<author>Hamsterdan</author>
	<datestamp>1259755260000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext>THat's what I use here. for MAC, there's NTFS-3G (free) or Paragon ($ but faster on writes).<br><br>I use NTFS on both my machines (Win/OS X/Linux) without any problems.<br><br>NTFS-3G is also available for Linux.</htmltext>
<tokenext>THat 's what I use here .
for MAC , there 's NTFS-3G ( free ) or Paragon ( $ but faster on writes ) .I use NTFS on both my machines ( Win/OS X/Linux ) without any problems.NTFS-3G is also available for Linux .</tokentext>
<sentencetext>THat's what I use here.
for MAC, there's NTFS-3G (free) or Paragon ($ but faster on writes).I use NTFS on both my machines (Win/OS X/Linux) without any problems.NTFS-3G is also available for Linux.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540074</id>
	<title>Re:NTFS</title>
	<author>Anonymous</author>
	<datestamp>1259756880000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Hmm.  My experience with NTFS on OS X is that writes can be exceedingly slow, depending on the application doing the writing.  Mathematica is a principal offender, but there are many others.  This goes for both NTFS-3G and Paragon drivers.</p></htmltext>
<tokenext>Hmm .
My experience with NTFS on OS X is that writes can be exceedingly slow , depending on the application doing the writing .
Mathematica is a principal offender , but there are many others .
This goes for both NTFS-3G and Paragon drivers .</tokentext>
<sentencetext>Hmm.
My experience with NTFS on OS X is that writes can be exceedingly slow, depending on the application doing the writing.
Mathematica is a principal offender, but there are many others.
This goes for both NTFS-3G and Paragon drivers.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539824</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540512</id>
	<title>WD TV Live!</title>
	<author>Anonymous</author>
	<datestamp>1259760060000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Just use NTFS.  You say you'll be using a WD TV Live! (which is a wonderful device, I must say), which supports NTFS and can act as a fileserver on your network.  So just leave your daily drive connected to the WD TV Live!, push your backups to it over the network, and then do your monthly backups off that as you planned.  No reason to bother with anything more complex than that.</p></htmltext>
<tokenext>Just use NTFS .
You say you 'll be using a WD TV Live !
( which is a wonderful device , I must say ) , which supports NTFS and can act as a fileserver on your network .
So just leave your daily drive connected to the WD TV Live ! , push your backups to it over the network , and then do your monthly backups off that as you planned .
No reason to bother with anything more complex than that .</tokentext>
<sentencetext>Just use NTFS.
You say you'll be using a WD TV Live!
(which is a wonderful device, I must say), which supports NTFS and can act as a fileserver on your network.
So just leave your daily drive connected to the WD TV Live!, push your backups to it over the network, and then do your monthly backups off that as you planned.
No reason to bother with anything more complex than that.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540686</id>
	<title>Re:The solution..</title>
	<author>i\_want\_you\_to\_throw\_</author>
	<datestamp>1259761560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Why even discuss it? After all this is the same slashdot where the term &quot;tinfoil hat&quot; is used regularly when people really mean aluminum foil. <br>
Al != SN</htmltext>
<tokenext>Why even discuss it ?
After all this is the same slashdot where the term " tinfoil hat " is used regularly when people really mean aluminum foil .
Al ! = SN</tokentext>
<sentencetext>Why even discuss it?
After all this is the same slashdot where the term "tinfoil hat" is used regularly when people really mean aluminum foil.
Al != SN</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540130</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539926</id>
	<title>Re:The solution..</title>
	<author>Demena</author>
	<datestamp>1259755860000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Regardless is "regardless of the reason given"
Irregardless is "regardless of any possible reason"

Regardless is comparative, irregardless is superlative.

That cover it?</htmltext>
<tokenext>Regardless is " regardless of the reason given " Irregardless is " regardless of any possible reason " Regardless is comparative , irregardless is superlative .
That cover it ?</tokentext>
<sentencetext>Regardless is "regardless of the reason given"
Irregardless is "regardless of any possible reason"

Regardless is comparative, irregardless is superlative.
That cover it?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539858</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539834</id>
	<title>Uhm...</title>
	<author>Anonymous</author>
	<datestamp>1259755320000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>1</modscore>
	<htmltext><p>Have you been living under a rock? NTFS has been writable on Linux for a long time now, using NTFS-3g - most distros come pre-bundled with it nowadays, and there's a Mac version as well.</p></htmltext>
<tokenext>Have you been living under a rock ?
NTFS has been writable on Linux for a long time now , using NTFS-3g - most distros come pre-bundled with it nowadays , and there 's a Mac version as well .</tokentext>
<sentencetext>Have you been living under a rock?
NTFS has been writable on Linux for a long time now, using NTFS-3g - most distros come pre-bundled with it nowadays, and there's a Mac version as well.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540536</id>
	<title>Re:ZFS, supported equally on your OSes</title>
	<author>Anonymous</author>
	<datestamp>1259760240000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>ZFS might be nice, but it requires some nice hardware to run it properly.</p></htmltext>
<tokenext>ZFS might be nice , but it requires some nice hardware to run it properly .</tokentext>
<sentencetext>ZFS might be nice, but it requires some nice hardware to run it properly.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539916</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30543508</id>
	<title>RAID (or an external drive) is NOT a Backup</title>
	<author>Anonymous</author>
	<datestamp>1261666740000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I hate to burst everyone's bubble here, I work in enterprise sector of IT, and USB disks are NEVER used as a backup. Simply put, they fail far too frequently. You'll be plagued with bus resets, crappy USB firmware on the drive, and a lack of a true archival medium.</p><p>Hard disks are not meant to sit on a shelf and reliably store data for many years. If you truly want a BACKUP that will be usable for years to come, you should start saving up for a LTO4 tape drive.</p><p>-----------------</p><p>Now for a filesystem for [any] drive, I'd recommend ZFS. In the newer releases among many features, you get snapshots and block level deduplication.</p></htmltext>
<tokenext>I hate to burst everyone 's bubble here , I work in enterprise sector of IT , and USB disks are NEVER used as a backup .
Simply put , they fail far too frequently .
You 'll be plagued with bus resets , crappy USB firmware on the drive , and a lack of a true archival medium.Hard disks are not meant to sit on a shelf and reliably store data for many years .
If you truly want a BACKUP that will be usable for years to come , you should start saving up for a LTO4 tape drive.-----------------Now for a filesystem for [ any ] drive , I 'd recommend ZFS .
In the newer releases among many features , you get snapshots and block level deduplication .</tokentext>
<sentencetext>I hate to burst everyone's bubble here, I work in enterprise sector of IT, and USB disks are NEVER used as a backup.
Simply put, they fail far too frequently.
You'll be plagued with bus resets, crappy USB firmware on the drive, and a lack of a true archival medium.Hard disks are not meant to sit on a shelf and reliably store data for many years.
If you truly want a BACKUP that will be usable for years to come, you should start saving up for a LTO4 tape drive.-----------------Now for a filesystem for [any] drive, I'd recommend ZFS.
In the newer releases among many features, you get snapshots and block level deduplication.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540614</id>
	<title>I basically have the same setup</title>
	<author>Kappy</author>
	<datestamp>1259760900000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>My backup has been worked good for the last few years. I had a large windows tower filled with hard drives...<br>* One of my HDD was encrypted using Truecrypt.<br>* A scheduled Acronis task would image my OS drive to the encrypted drive.<br>* I have another encrypted HDD in one of these KINGWIN KF-91-BK trays (http://www.newegg.com/Product/Product.aspx?Item=N82E16817121172)<br>* After Acronis was done, I would kick off a little batch file to mount the tray drive (which was encrypted) and run SyncBack Pro to mirror the encrypted source. Then dismount.</p><p>I just bought a few extra trays. Each month I sync all the other HDD in the system (including the encrypted drive) for my off-site backup. One flaw in my system was if one of the other "data drives" crashed, I would loose at most a month of changes. They were just music/videos and didn't change very much. I accepted this fault.</p><p>I out grew the tower and recently built a cheap unRaid box. Most if it should work the same, except now I have redundancy for all my drives in the case of a crash.</p></htmltext>
<tokenext>My backup has been worked good for the last few years .
I had a large windows tower filled with hard drives... * One of my HDD was encrypted using Truecrypt .
* A scheduled Acronis task would image my OS drive to the encrypted drive .
* I have another encrypted HDD in one of these KINGWIN KF-91-BK trays ( http : //www.newegg.com/Product/Product.aspx ? Item = N82E16817121172 ) * After Acronis was done , I would kick off a little batch file to mount the tray drive ( which was encrypted ) and run SyncBack Pro to mirror the encrypted source .
Then dismount.I just bought a few extra trays .
Each month I sync all the other HDD in the system ( including the encrypted drive ) for my off-site backup .
One flaw in my system was if one of the other " data drives " crashed , I would loose at most a month of changes .
They were just music/videos and did n't change very much .
I accepted this fault.I out grew the tower and recently built a cheap unRaid box .
Most if it should work the same , except now I have redundancy for all my drives in the case of a crash .</tokentext>
<sentencetext>My backup has been worked good for the last few years.
I had a large windows tower filled with hard drives...* One of my HDD was encrypted using Truecrypt.
* A scheduled Acronis task would image my OS drive to the encrypted drive.
* I have another encrypted HDD in one of these KINGWIN KF-91-BK trays (http://www.newegg.com/Product/Product.aspx?Item=N82E16817121172)* After Acronis was done, I would kick off a little batch file to mount the tray drive (which was encrypted) and run SyncBack Pro to mirror the encrypted source.
Then dismount.I just bought a few extra trays.
Each month I sync all the other HDD in the system (including the encrypted drive) for my off-site backup.
One flaw in my system was if one of the other "data drives" crashed, I would loose at most a month of changes.
They were just music/videos and didn't change very much.
I accepted this fault.I out grew the tower and recently built a cheap unRaid box.
Most if it should work the same, except now I have redundancy for all my drives in the case of a crash.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539858</id>
	<title>Re:The solution..</title>
	<author>Anonymous</author>
	<datestamp>1259755500000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Irregardless, I think you're way better off with this approach vice trying to find the magical widely supported cross platform file system with large file capacity.</p></div><p>What's the difference between irregardless and regardless?</p></div>
	</htmltext>
<tokenext>Irregardless , I think you 're way better off with this approach vice trying to find the magical widely supported cross platform file system with large file capacity.What 's the difference between irregardless and regardless ?</tokentext>
<sentencetext>Irregardless, I think you're way better off with this approach vice trying to find the magical widely supported cross platform file system with large file capacity.What's the difference between irregardless and regardless?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539806</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542252</id>
	<title>ntfs-3g</title>
	<author>Anonymous</author>
	<datestamp>1259782980000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Works for me perfectly on Linux and Windows on an external USB-Harddisk for 3 years now.</p></htmltext>
<tokenext>Works for me perfectly on Linux and Windows on an external USB-Harddisk for 3 years now .</tokentext>
<sentencetext>Works for me perfectly on Linux and Windows on an external USB-Harddisk for 3 years now.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540868</id>
	<title>Go with EXT3 and on windows use a VM shim</title>
	<author>ZERO1ZERO</author>
	<datestamp>1259763120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Install a tiny debian virtual machine on your windows PC that can host the USB drive as a network share for the times when you have to use it via Windows.  There maybe some kind of Virtual-box-system-in-an-exe type thing where you could have it on a FAT32 partition at the start of the disk so you could run it on any windows PC without the need to pre configure a VM.  Depends on your situation.</htmltext>
<tokenext>Install a tiny debian virtual machine on your windows PC that can host the USB drive as a network share for the times when you have to use it via Windows .
There maybe some kind of Virtual-box-system-in-an-exe type thing where you could have it on a FAT32 partition at the start of the disk so you could run it on any windows PC without the need to pre configure a VM .
Depends on your situation .</tokentext>
<sentencetext>Install a tiny debian virtual machine on your windows PC that can host the USB drive as a network share for the times when you have to use it via Windows.
There maybe some kind of Virtual-box-system-in-an-exe type thing where you could have it on a FAT32 partition at the start of the disk so you could run it on any windows PC without the need to pre configure a VM.
Depends on your situation.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30543400</id>
	<title>ZFS with compression and dedup turned on</title>
	<author>Anonymous</author>
	<datestamp>1261665480000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>1</modscore>
	<htmltext><p>In my opinion, external backup drives cannot be trusted. You could work around this by mirroring the drives yourself, but I think that I have a better solution.</p><p>Use ZFS.</p><p>Here's how I plan to backup Windows files onto ZFS external drives.</p><p>1. Install Virtualbox to run OpenSolaris which will manage the ZFS drives.<br>2. Get a distro of OpenSolaris that supports dedup. The first distro with all of that was 128a so google for this filename "osol-dev-128a-x86.iso" or download a more recent OpenSolaris.<br>3. Get some USB hubs, one for each of your USB ports.<br>4. Plug in a bunch of USB drives. I am using eight 8Gb thumbdrives but that only gets me 48Gb. Use spinning hard drives to get more storage.<br>5. Decide on RAIDZ2 or RAID 1+0 (a stripe of mirrors). If you are using drives bigger than 500Gb then you probably should go for RAID 1+0 aka RAID 10. Be careful, some advice on the net gets this backwards. I am using RAIDZ2 with 2 parity drives which is why my eight drives only give me 6*8=48Gb of storage.<br>6. Install OpenSolaris in Virtualbox. If you are an uberhacker like me, do a console install on a 2G CF card. If not, then choose a 6Gb virtual drive and do the standard GUI install.<br>7 Set up your ZFS pool on the USB drives, make some filesystems and export them as CIFS shares or make some virtual devices and export them as iSCSI.<br>8. On Windows, copy your files to the network drive.<br>9. In the virtual OpenSolaris machine run a ZFS scrub.<br>10. Shutdown OpenSolaris and pack away the drives until the next backup session.</p><p>You now have a reasonably secure backup which can survive the loss of one, or maybe two drives depending on how you configured it. And if a sector on a drive goes bad, ZFS scrub will recover the data. Normally, an external drive failure means either total loss of the data, or at best, loss of some files. And an external drive may have already lost some of your files but you won't know it until you try to use them years from now. On other filesystems there is no equivalent of the ZFS scrub with sector-based checksums to automatically recover bad blocks.</p><p>Yes, I know this solution is a bit techy, but expect someone to package this up as a neat backup-in-a-box solution. I believe that you can run Virtualbox on Windows in a headless mode so the customer would never know that their Fort-Knox grade backup application is actually OpenSolaris in a VM.</p></htmltext>
<tokenext>In my opinion , external backup drives can not be trusted .
You could work around this by mirroring the drives yourself , but I think that I have a better solution.Use ZFS.Here 's how I plan to backup Windows files onto ZFS external drives.1 .
Install Virtualbox to run OpenSolaris which will manage the ZFS drives.2 .
Get a distro of OpenSolaris that supports dedup .
The first distro with all of that was 128a so google for this filename " osol-dev-128a-x86.iso " or download a more recent OpenSolaris.3 .
Get some USB hubs , one for each of your USB ports.4 .
Plug in a bunch of USB drives .
I am using eight 8Gb thumbdrives but that only gets me 48Gb .
Use spinning hard drives to get more storage.5 .
Decide on RAIDZ2 or RAID 1 + 0 ( a stripe of mirrors ) .
If you are using drives bigger than 500Gb then you probably should go for RAID 1 + 0 aka RAID 10 .
Be careful , some advice on the net gets this backwards .
I am using RAIDZ2 with 2 parity drives which is why my eight drives only give me 6 * 8 = 48Gb of storage.6 .
Install OpenSolaris in Virtualbox .
If you are an uberhacker like me , do a console install on a 2G CF card .
If not , then choose a 6Gb virtual drive and do the standard GUI install.7 Set up your ZFS pool on the USB drives , make some filesystems and export them as CIFS shares or make some virtual devices and export them as iSCSI.8 .
On Windows , copy your files to the network drive.9 .
In the virtual OpenSolaris machine run a ZFS scrub.10 .
Shutdown OpenSolaris and pack away the drives until the next backup session.You now have a reasonably secure backup which can survive the loss of one , or maybe two drives depending on how you configured it .
And if a sector on a drive goes bad , ZFS scrub will recover the data .
Normally , an external drive failure means either total loss of the data , or at best , loss of some files .
And an external drive may have already lost some of your files but you wo n't know it until you try to use them years from now .
On other filesystems there is no equivalent of the ZFS scrub with sector-based checksums to automatically recover bad blocks.Yes , I know this solution is a bit techy , but expect someone to package this up as a neat backup-in-a-box solution .
I believe that you can run Virtualbox on Windows in a headless mode so the customer would never know that their Fort-Knox grade backup application is actually OpenSolaris in a VM .</tokentext>
<sentencetext>In my opinion, external backup drives cannot be trusted.
You could work around this by mirroring the drives yourself, but I think that I have a better solution.Use ZFS.Here's how I plan to backup Windows files onto ZFS external drives.1.
Install Virtualbox to run OpenSolaris which will manage the ZFS drives.2.
Get a distro of OpenSolaris that supports dedup.
The first distro with all of that was 128a so google for this filename "osol-dev-128a-x86.iso" or download a more recent OpenSolaris.3.
Get some USB hubs, one for each of your USB ports.4.
Plug in a bunch of USB drives.
I am using eight 8Gb thumbdrives but that only gets me 48Gb.
Use spinning hard drives to get more storage.5.
Decide on RAIDZ2 or RAID 1+0 (a stripe of mirrors).
If you are using drives bigger than 500Gb then you probably should go for RAID 1+0 aka RAID 10.
Be careful, some advice on the net gets this backwards.
I am using RAIDZ2 with 2 parity drives which is why my eight drives only give me 6*8=48Gb of storage.6.
Install OpenSolaris in Virtualbox.
If you are an uberhacker like me, do a console install on a 2G CF card.
If not, then choose a 6Gb virtual drive and do the standard GUI install.7 Set up your ZFS pool on the USB drives, make some filesystems and export them as CIFS shares or make some virtual devices and export them as iSCSI.8.
On Windows, copy your files to the network drive.9.
In the virtual OpenSolaris machine run a ZFS scrub.10.
Shutdown OpenSolaris and pack away the drives until the next backup session.You now have a reasonably secure backup which can survive the loss of one, or maybe two drives depending on how you configured it.
And if a sector on a drive goes bad, ZFS scrub will recover the data.
Normally, an external drive failure means either total loss of the data, or at best, loss of some files.
And an external drive may have already lost some of your files but you won't know it until you try to use them years from now.
On other filesystems there is no equivalent of the ZFS scrub with sector-based checksums to automatically recover bad blocks.Yes, I know this solution is a bit techy, but expect someone to package this up as a neat backup-in-a-box solution.
I believe that you can run Virtualbox on Windows in a headless mode so the customer would never know that their Fort-Knox grade backup application is actually OpenSolaris in a VM.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540770</id>
	<title>Re:NTFS</title>
	<author>PhunkySchtuff</author>
	<datestamp>1259762280000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>As much as I love ZFS, one thing it's not good at is for a single removable disk. The inability for Apple to get this working without kernel panicking the machine was one of the many reasons they chose to drop it.</p></htmltext>
<tokenext>As much as I love ZFS , one thing it 's not good at is for a single removable disk .
The inability for Apple to get this working without kernel panicking the machine was one of the many reasons they chose to drop it .</tokentext>
<sentencetext>As much as I love ZFS, one thing it's not good at is for a single removable disk.
The inability for Apple to get this working without kernel panicking the machine was one of the many reasons they chose to drop it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539930</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541104</id>
	<title>Ext3 on Linux + Samba</title>
	<author>Foldarn</author>
	<datestamp>1259765880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>If your Windows PC(s) are all networked with your Linux PC, then just format it Ext3, share it out with Samba, and let Windows read it from over the network.</htmltext>
<tokenext>If your Windows PC ( s ) are all networked with your Linux PC , then just format it Ext3 , share it out with Samba , and let Windows read it from over the network .</tokentext>
<sentencetext>If your Windows PC(s) are all networked with your Linux PC, then just format it Ext3, share it out with Samba, and let Windows read it from over the network.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540466</id>
	<title>ext3</title>
	<author>solid\_liq</author>
	<datestamp>1259759760000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>I go with ext3 for this personally.  NTFS doesn't store *nix style filesystem permissions, and causes various other issues with you Linux systems.  With ext3, you can store all your files with all of your permissions intact, the filesystem is mature and trustworthy, and you can still access all of the files from any operating system by simply connecting the drives to a dedicated fileserver machine (an older computer or small device works perfectly for this).  Simply share your files via NFS, Samba and ftp (if you need ftp access for something like xmbc).  Having a dedicated machine for this means you can also script your replication to the secondary drive, so that you only have to attach the drive for the mirroring process to take place.
<br> <br>
This is the solution I've been using for about four years now, and it works great for me.</htmltext>
<tokenext>I go with ext3 for this personally .
NTFS does n't store * nix style filesystem permissions , and causes various other issues with you Linux systems .
With ext3 , you can store all your files with all of your permissions intact , the filesystem is mature and trustworthy , and you can still access all of the files from any operating system by simply connecting the drives to a dedicated fileserver machine ( an older computer or small device works perfectly for this ) .
Simply share your files via NFS , Samba and ftp ( if you need ftp access for something like xmbc ) .
Having a dedicated machine for this means you can also script your replication to the secondary drive , so that you only have to attach the drive for the mirroring process to take place .
This is the solution I 've been using for about four years now , and it works great for me .</tokentext>
<sentencetext>I go with ext3 for this personally.
NTFS doesn't store *nix style filesystem permissions, and causes various other issues with you Linux systems.
With ext3, you can store all your files with all of your permissions intact, the filesystem is mature and trustworthy, and you can still access all of the files from any operating system by simply connecting the drives to a dedicated fileserver machine (an older computer or small device works perfectly for this).
Simply share your files via NFS, Samba and ftp (if you need ftp access for something like xmbc).
Having a dedicated machine for this means you can also script your replication to the secondary drive, so that you only have to attach the drive for the mirroring process to take place.
This is the solution I've been using for about four years now, and it works great for me.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540780</id>
	<title>Re:The best is...</title>
	<author>Anonymous</author>
	<datestamp>1259762400000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Hans Reiser should not be named.  He doesn't even deserve to be the butt of a joke out of respect for his wife and her loved ones.  I think if you think about it for second, you'll realize how horrible these jokes are.</p></htmltext>
<tokenext>Hans Reiser should not be named .
He does n't even deserve to be the butt of a joke out of respect for his wife and her loved ones .
I think if you think about it for second , you 'll realize how horrible these jokes are .</tokentext>
<sentencetext>Hans Reiser should not be named.
He doesn't even deserve to be the butt of a joke out of respect for his wife and her loved ones.
I think if you think about it for second, you'll realize how horrible these jokes are.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539888</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30544410</id>
	<title>Re:Replace the WD TV thing</title>
	<author>Anonymous</author>
	<datestamp>1261673820000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>The WD TV Live isn't silly at all, and a mini (or micro) ITX system would be positively huge in comparison.  The WD is a nano-ITX.  Good luck getting equivalent value for $100.</p></htmltext>
<tokenext>The WD TV Live is n't silly at all , and a mini ( or micro ) ITX system would be positively huge in comparison .
The WD is a nano-ITX .
Good luck getting equivalent value for $ 100 .</tokentext>
<sentencetext>The WD TV Live isn't silly at all, and a mini (or micro) ITX system would be positively huge in comparison.
The WD is a nano-ITX.
Good luck getting equivalent value for $100.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540242</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541436</id>
	<title>Re:Words of caution</title>
	<author>Anonymous</author>
	<datestamp>1259770560000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>can you tell the OS to power down the drives after some period of idleness - just like you would were it your desktop ?<br>that should take them offline correctly - right ?</p></htmltext>
<tokenext>can you tell the OS to power down the drives after some period of idleness - just like you would were it your desktop ? that should take them offline correctly - right ?</tokentext>
<sentencetext>can you tell the OS to power down the drives after some period of idleness - just like you would were it your desktop ?that should take them offline correctly - right ?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30581350</id>
	<title>NAS is the way to go</title>
	<author>seangee</author>
	<datestamp>1262097060000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext>+ 1 for build a NAS. Your backup doesn't need to be very portable. I started out with FreeNAS, if you go this route ZFS would be the logical choice. I got pretty frustrated with this so rebuilt my NAS using Ubuntu and EXT3 - it made sense to me to use the native FS for the OS. I currently have 4 x 1TB internal drives in raid 5 (one spare). I use a USB drive to back this up. SMB internally and all the files are accessible by every OS I use. If I need to take files out and about there are good old USB sticks or portable drives. Mine are usually NTFS or FAT 32 because anything can read these - and of course there's always good old FTP on the NAS</htmltext>
<tokenext>+ 1 for build a NAS .
Your backup does n't need to be very portable .
I started out with FreeNAS , if you go this route ZFS would be the logical choice .
I got pretty frustrated with this so rebuilt my NAS using Ubuntu and EXT3 - it made sense to me to use the native FS for the OS .
I currently have 4 x 1TB internal drives in raid 5 ( one spare ) .
I use a USB drive to back this up .
SMB internally and all the files are accessible by every OS I use .
If I need to take files out and about there are good old USB sticks or portable drives .
Mine are usually NTFS or FAT 32 because anything can read these - and of course there 's always good old FTP on the NAS</tokentext>
<sentencetext>+ 1 for build a NAS.
Your backup doesn't need to be very portable.
I started out with FreeNAS, if you go this route ZFS would be the logical choice.
I got pretty frustrated with this so rebuilt my NAS using Ubuntu and EXT3 - it made sense to me to use the native FS for the OS.
I currently have 4 x 1TB internal drives in raid 5 (one spare).
I use a USB drive to back this up.
SMB internally and all the files are accessible by every OS I use.
If I need to take files out and about there are good old USB sticks or portable drives.
Mine are usually NTFS or FAT 32 because anything can read these - and of course there's always good old FTP on the NAS</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539930</id>
	<title>Re:NTFS</title>
	<author>elh\_inny</author>
	<datestamp>1259755860000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>I second this choice.<br>For some zealots it's hard to admit but the performance is really good, you have commercial backing of the biggest software company on the planet.</p><p>Recently a commercial company (Tuxera) was formed to provide commercial support for NTFS-3G and provide paid-for version of the driver for MacOS and Linux in addition to the free NTFS-3G.</p><p>So the future and cross platform access is looking really good.</p><p>On the other hand, if I were just a little bit more adventurous, I would much rather use Sun ZFS for storage to have even better reliability, flexibility than with equivalent hardware RAID. But this pretty much requires a separate NAS box running OpenSolaris just for that.</p><p>For me and many other garage hackers that just doesn't cut it, all I have is one laptop running a really fancy looking BSD and two external drives (NTFS) and some backup scattered over the Internet...</p><p>All I'm hoping for is that one day Apple will reintegrate ZFS support, it's already been promised, implemented and now ditched...</p></htmltext>
<tokenext>I second this choice.For some zealots it 's hard to admit but the performance is really good , you have commercial backing of the biggest software company on the planet.Recently a commercial company ( Tuxera ) was formed to provide commercial support for NTFS-3G and provide paid-for version of the driver for MacOS and Linux in addition to the free NTFS-3G.So the future and cross platform access is looking really good.On the other hand , if I were just a little bit more adventurous , I would much rather use Sun ZFS for storage to have even better reliability , flexibility than with equivalent hardware RAID .
But this pretty much requires a separate NAS box running OpenSolaris just for that.For me and many other garage hackers that just does n't cut it , all I have is one laptop running a really fancy looking BSD and two external drives ( NTFS ) and some backup scattered over the Internet...All I 'm hoping for is that one day Apple will reintegrate ZFS support , it 's already been promised , implemented and now ditched.. .</tokentext>
<sentencetext>I second this choice.For some zealots it's hard to admit but the performance is really good, you have commercial backing of the biggest software company on the planet.Recently a commercial company (Tuxera) was formed to provide commercial support for NTFS-3G and provide paid-for version of the driver for MacOS and Linux in addition to the free NTFS-3G.So the future and cross platform access is looking really good.On the other hand, if I were just a little bit more adventurous, I would much rather use Sun ZFS for storage to have even better reliability, flexibility than with equivalent hardware RAID.
But this pretty much requires a separate NAS box running OpenSolaris just for that.For me and many other garage hackers that just doesn't cut it, all I have is one laptop running a really fancy looking BSD and two external drives (NTFS) and some backup scattered over the Internet...All I'm hoping for is that one day Apple will reintegrate ZFS support, it's already been promised, implemented and now ditched...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539824</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542284</id>
	<title>Re:Avoid USB attached storage. (Re:Words of cautio</title>
	<author>greg1104</author>
	<datestamp>1259783520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The idea of using a USB drive for any sort of large storage gives me the willies for the reason you list, which is extremely important, as well as some others:</p><p>-USB bridges rarely pass any SMART data back to the host, which means that if it starts to fail you won't know until it's already lost data.  How much data?  You'll have no idea.  Well, you could if you used ZFS or other checksumming, but even then you're not going to know what wrong until data is gone.</p><p>-Drives in the 1TB range are going to be regular internal drives with a USB bridge on them.  Ever notice how external drives normally have a much shorter warranty on them than the internal versions of the same basic disk?  That's because moving a desktop drive around is really bad for it.  They just don't last very well in that situation, thus the derated warranty and lower expected lifetime.</p><p>-Drive failure rates are so bad, and the time it takes to make a full copy of a drive this big so long over USB, that you're way too exposed to losing two drives.  If you care about your data at all, ideally you'd want a RAID-1 pair of internal drives in a server system.  It's reasonable in that situation to make an off-site backup you sync periodically, but you don't want a portable drive to be your only primary copy.</p><p>Note that the first couple of these issues, the ones related to the crappy USB chipsets, can be avoided if you get an external drive that connects via eSATA.  Then you get SMART, no write cache fiasco, much better situation.  But it's still a desktop drive that's very likely to fail when used this way.</p></htmltext>
<tokenext>The idea of using a USB drive for any sort of large storage gives me the willies for the reason you list , which is extremely important , as well as some others : -USB bridges rarely pass any SMART data back to the host , which means that if it starts to fail you wo n't know until it 's already lost data .
How much data ?
You 'll have no idea .
Well , you could if you used ZFS or other checksumming , but even then you 're not going to know what wrong until data is gone.-Drives in the 1TB range are going to be regular internal drives with a USB bridge on them .
Ever notice how external drives normally have a much shorter warranty on them than the internal versions of the same basic disk ?
That 's because moving a desktop drive around is really bad for it .
They just do n't last very well in that situation , thus the derated warranty and lower expected lifetime.-Drive failure rates are so bad , and the time it takes to make a full copy of a drive this big so long over USB , that you 're way too exposed to losing two drives .
If you care about your data at all , ideally you 'd want a RAID-1 pair of internal drives in a server system .
It 's reasonable in that situation to make an off-site backup you sync periodically , but you do n't want a portable drive to be your only primary copy.Note that the first couple of these issues , the ones related to the crappy USB chipsets , can be avoided if you get an external drive that connects via eSATA .
Then you get SMART , no write cache fiasco , much better situation .
But it 's still a desktop drive that 's very likely to fail when used this way .</tokentext>
<sentencetext>The idea of using a USB drive for any sort of large storage gives me the willies for the reason you list, which is extremely important, as well as some others:-USB bridges rarely pass any SMART data back to the host, which means that if it starts to fail you won't know until it's already lost data.
How much data?
You'll have no idea.
Well, you could if you used ZFS or other checksumming, but even then you're not going to know what wrong until data is gone.-Drives in the 1TB range are going to be regular internal drives with a USB bridge on them.
Ever notice how external drives normally have a much shorter warranty on them than the internal versions of the same basic disk?
That's because moving a desktop drive around is really bad for it.
They just don't last very well in that situation, thus the derated warranty and lower expected lifetime.-Drive failure rates are so bad, and the time it takes to make a full copy of a drive this big so long over USB, that you're way too exposed to losing two drives.
If you care about your data at all, ideally you'd want a RAID-1 pair of internal drives in a server system.
It's reasonable in that situation to make an off-site backup you sync periodically, but you don't want a portable drive to be your only primary copy.Note that the first couple of these issues, the ones related to the crappy USB chipsets, can be avoided if you get an external drive that connects via eSATA.
Then you get SMART, no write cache fiasco, much better situation.
But it's still a desktop drive that's very likely to fail when used this way.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542068</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539806</id>
	<title>The solution..</title>
	<author>Anonymous</author>
	<datestamp>1259755140000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext><p>is to stop being so diverse! Pick a platform and stick with it!</p><p>Ok, in all seriousness.. here's what you do:</p><p>- buy yourself a cheap (~200) box<br>- hook all your drives to it<br>- use whatever file system you want (JFS, XFS would be my recommendation)<br>- share it over your zoo of a network using nfs, samba, etc..</p><p>As a bonus, your file server box could double as a media center, and replace your WD TV Live dealie.. (probably not though.. right)</p><p>Irregardless, I think you're way better off with this approach vice trying to find the magical widely supported cross platform file system with large file capacity.</p><p>You also might want to consider RAID vs. your monthly sync. Yes, RAID isn't a backup.. but for something like this where<br>restoration would be possible, but just a pain in the ass.. mirrored raid can be a lot more convenient. You can always have<br>a third external to back up your irreplacable data on a semi-annual basis..</p></htmltext>
<tokenext>is to stop being so diverse !
Pick a platform and stick with it ! Ok , in all seriousness.. here 's what you do : - buy yourself a cheap ( ~ 200 ) box- hook all your drives to it- use whatever file system you want ( JFS , XFS would be my recommendation ) - share it over your zoo of a network using nfs , samba , etc..As a bonus , your file server box could double as a media center , and replace your WD TV Live dealie.. ( probably not though.. right ) Irregardless , I think you 're way better off with this approach vice trying to find the magical widely supported cross platform file system with large file capacity.You also might want to consider RAID vs. your monthly sync .
Yes , RAID is n't a backup.. but for something like this whererestoration would be possible , but just a pain in the ass.. mirrored raid can be a lot more convenient .
You can always havea third external to back up your irreplacable data on a semi-annual basis. .</tokentext>
<sentencetext>is to stop being so diverse!
Pick a platform and stick with it!Ok, in all seriousness.. here's what you do:- buy yourself a cheap (~200) box- hook all your drives to it- use whatever file system you want (JFS, XFS would be my recommendation)- share it over your zoo of a network using nfs, samba, etc..As a bonus, your file server box could double as a media center, and replace your WD TV Live dealie.. (probably not though.. right)Irregardless, I think you're way better off with this approach vice trying to find the magical widely supported cross platform file system with large file capacity.You also might want to consider RAID vs. your monthly sync.
Yes, RAID isn't a backup.. but for something like this whererestoration would be possible, but just a pain in the ass.. mirrored raid can be a lot more convenient.
You can always havea third external to back up your irreplacable data on a semi-annual basis..</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541020</id>
	<title>NTFS and Compress</title>
	<author>ccrasher</author>
	<datestamp>1259764860000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>I would recommend NTFS. I would also recommend that you get an open source program and compress the dvd's to approx. 700MB for up to 90 minutes and 1.4GB over 90 mins.
H264/ac3 or Xvid are good codecs to use. Batch schedule the movies and let the system compress all night when you don't need the system.
The reason for this is because dvd's take up a lot of wasted space because of the format. A compressed movie takes up far less space. I can store about 1000 movies on a 1TB drive
and if a dvd is ever needed, I can recode a dvd. There is not much quality difference between a compressed movie and a dvd file.
You can also convert the dvd's to<nobr> <wbr></nobr>.mov files but apple can read most H264 files or mp4 files. Many dvd players can read Xvid or Dvix files and others without the need for a dvd file.

For cd's, If you plan to burn several copies, then rip the cd's directly to<nobr> <wbr></nobr>.wav or<nobr> <wbr></nobr>.flac (lossless) files. mp3 files are like<nobr> <wbr></nobr>.jpg image files such that they lose a little quality/data each
time they are copied whereas lossless<nobr> <wbr></nobr>.wav or<nobr> <wbr></nobr>.flac files DO NOT regardless of how many times they are copied.</htmltext>
<tokenext>I would recommend NTFS .
I would also recommend that you get an open source program and compress the dvd 's to approx .
700MB for up to 90 minutes and 1.4GB over 90 mins .
H264/ac3 or Xvid are good codecs to use .
Batch schedule the movies and let the system compress all night when you do n't need the system .
The reason for this is because dvd 's take up a lot of wasted space because of the format .
A compressed movie takes up far less space .
I can store about 1000 movies on a 1TB drive and if a dvd is ever needed , I can recode a dvd .
There is not much quality difference between a compressed movie and a dvd file .
You can also convert the dvd 's to .mov files but apple can read most H264 files or mp4 files .
Many dvd players can read Xvid or Dvix files and others without the need for a dvd file .
For cd 's , If you plan to burn several copies , then rip the cd 's directly to .wav or .flac ( lossless ) files .
mp3 files are like .jpg image files such that they lose a little quality/data each time they are copied whereas lossless .wav or .flac files DO NOT regardless of how many times they are copied .</tokentext>
<sentencetext>I would recommend NTFS.
I would also recommend that you get an open source program and compress the dvd's to approx.
700MB for up to 90 minutes and 1.4GB over 90 mins.
H264/ac3 or Xvid are good codecs to use.
Batch schedule the movies and let the system compress all night when you don't need the system.
The reason for this is because dvd's take up a lot of wasted space because of the format.
A compressed movie takes up far less space.
I can store about 1000 movies on a 1TB drive
and if a dvd is ever needed, I can recode a dvd.
There is not much quality difference between a compressed movie and a dvd file.
You can also convert the dvd's to .mov files but apple can read most H264 files or mp4 files.
Many dvd players can read Xvid or Dvix files and others without the need for a dvd file.
For cd's, If you plan to burn several copies, then rip the cd's directly to .wav or .flac (lossless) files.
mp3 files are like .jpg image files such that they lose a little quality/data each
time they are copied whereas lossless .wav or .flac files DO NOT regardless of how many times they are copied.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540642</id>
	<title>Re:ZFS, supported equally on your OSes</title>
	<author>joseph.spiros</author>
	<datestamp>1259761080000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>zfs-fuse does not currently compile for platforms other than Linux, despite FUSE's general compatibility with other systems. The Mac OS X ZFS port worked for me under Leopard, and I think it works under Snow Leopard now, though it is no longer being developed by Apple. Last I checked, the ZFS pool version supported by these two implementations differs, so you'll need to create your pool with the latest commonly supported pool version to ensure compatibility.

In short, I do support the use of ZFS, and I personally use zfs-fuse, but it's of far more use when shared over the network due to the problems with ZFS implementations on various platforms.</htmltext>
<tokenext>zfs-fuse does not currently compile for platforms other than Linux , despite FUSE 's general compatibility with other systems .
The Mac OS X ZFS port worked for me under Leopard , and I think it works under Snow Leopard now , though it is no longer being developed by Apple .
Last I checked , the ZFS pool version supported by these two implementations differs , so you 'll need to create your pool with the latest commonly supported pool version to ensure compatibility .
In short , I do support the use of ZFS , and I personally use zfs-fuse , but it 's of far more use when shared over the network due to the problems with ZFS implementations on various platforms .</tokentext>
<sentencetext>zfs-fuse does not currently compile for platforms other than Linux, despite FUSE's general compatibility with other systems.
The Mac OS X ZFS port worked for me under Leopard, and I think it works under Snow Leopard now, though it is no longer being developed by Apple.
Last I checked, the ZFS pool version supported by these two implementations differs, so you'll need to create your pool with the latest commonly supported pool version to ensure compatibility.
In short, I do support the use of ZFS, and I personally use zfs-fuse, but it's of far more use when shared over the network due to the problems with ZFS implementations on various platforms.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539916</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30543600</id>
	<title>Re:NTFS</title>
	<author>Marauder2</author>
	<datestamp>1261668000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Exactly. NTFS-3G has been solid for quite a while now. I've been using it for years on both my Macs and Linux boxes without issue. All of my large capacity external drives are formatted NTFS nowadays and they easily talk to all of the systems I care about.</p></htmltext>
<tokenext>Exactly .
NTFS-3G has been solid for quite a while now .
I 've been using it for years on both my Macs and Linux boxes without issue .
All of my large capacity external drives are formatted NTFS nowadays and they easily talk to all of the systems I care about .</tokentext>
<sentencetext>Exactly.
NTFS-3G has been solid for quite a while now.
I've been using it for years on both my Macs and Linux boxes without issue.
All of my large capacity external drives are formatted NTFS nowadays and they easily talk to all of the systems I care about.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539824</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540504</id>
	<title>NTFS or ZFS</title>
	<author>DiSKiLLeR</author>
	<datestamp>1259760060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Its been stated here repeatedly. You want to go NTFS for all the listed reasons, or ZFS.</p><p>I set up my own ZFS NAS server, but yeah, up to you.</p><p>Do NOT go FAT32 under ANY circumstances.</p></htmltext>
<tokenext>Its been stated here repeatedly .
You want to go NTFS for all the listed reasons , or ZFS.I set up my own ZFS NAS server , but yeah , up to you.Do NOT go FAT32 under ANY circumstances .</tokentext>
<sentencetext>Its been stated here repeatedly.
You want to go NTFS for all the listed reasons, or ZFS.I set up my own ZFS NAS server, but yeah, up to you.Do NOT go FAT32 under ANY circumstances.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540882</id>
	<title>Re:The best is...</title>
	<author>Anonymous</author>
	<datestamp>1259763300000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Hans Reiser should not be named.  He doesn't even deserve to be the butt of a joke out of respect for his wife and those bereaved of her loss.  I think that if you consider these jokes a little more carefully, you'll agree.</p></htmltext>
<tokenext>Hans Reiser should not be named .
He does n't even deserve to be the butt of a joke out of respect for his wife and those bereaved of her loss .
I think that if you consider these jokes a little more carefully , you 'll agree .</tokentext>
<sentencetext>Hans Reiser should not be named.
He doesn't even deserve to be the butt of a joke out of respect for his wife and those bereaved of her loss.
I think that if you consider these jokes a little more carefully, you'll agree.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539888</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542934</id>
	<title>Re:NTFS</title>
	<author>Anonymous</author>
	<datestamp>1261656480000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>EXT3</p><p>That's what I use here.</p><p>I think there's a driver in the kernel, why would you let windows mount your drives ? Just use some network protocol...<nobr> <wbr></nobr>...</p><p>Seriously I don't think NTFS is a good idea: it's slow, closed, prone to errors and fragmentation.</p><p>The only "advantage" is that its the only "modern" file system supported out-of the box by windows, is that the most important criteria for a backup solution ??</p><p>I had several horror stories in the past using NTFS (ex: corrupted master file table after a power surge =&gt; unreadable gigabyte partition), no problem with ext3 and if you really need windows just use the ext "ifs" driver for windows...</p></htmltext>
<tokenext>EXT3That 's what I use here.I think there 's a driver in the kernel , why would you let windows mount your drives ?
Just use some network protocol... ...Seriously I do n't think NTFS is a good idea : it 's slow , closed , prone to errors and fragmentation.The only " advantage " is that its the only " modern " file system supported out-of the box by windows , is that the most important criteria for a backup solution ?
? I had several horror stories in the past using NTFS ( ex : corrupted master file table after a power surge = &gt; unreadable gigabyte partition ) , no problem with ext3 and if you really need windows just use the ext " ifs " driver for windows.. .</tokentext>
<sentencetext>EXT3That's what I use here.I think there's a driver in the kernel, why would you let windows mount your drives ?
Just use some network protocol... ...Seriously I don't think NTFS is a good idea: it's slow, closed, prone to errors and fragmentation.The only "advantage" is that its the only "modern" file system supported out-of the box by windows, is that the most important criteria for a backup solution ?
?I had several horror stories in the past using NTFS (ex: corrupted master file table after a power surge =&gt; unreadable gigabyte partition), no problem with ext3 and if you really need windows just use the ext "ifs" driver for windows...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539824</parent>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541436
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539804
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540152
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539806
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539858
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539926
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540130
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540524
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_49</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539824
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30544044
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_40</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539824
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539930
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540770
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542068
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542284
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540242
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30566664
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539824
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540456
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30544238
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542172
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539912
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30549650
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539888
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540138
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541224
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_46</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540634
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_53</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540372
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_52</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540272
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541296
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_43</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539916
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540158
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30553798
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539824
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542934
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539806
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539858
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539926
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540130
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540428
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540688
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541606
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540242
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30544410
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539888
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540882
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539806
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539858
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539926
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540130
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540412
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_44</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539888
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541558
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_51</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539912
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540714
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_37</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539888
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540138
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542100
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_39</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539912
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541478
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540242
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30546180
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_41</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541106
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541070
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_38</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539888
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540780
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539912
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540396
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539824
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539930
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542350
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_47</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539806
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539858
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539936
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540530
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539916
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540642
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540324
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541524
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_48</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539824
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30552246
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539806
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539858
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539924
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542838
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542678
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_45</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541114
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30548652
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540568
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539912
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540076
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_50</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539824
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540074
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539806
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539858
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539926
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540130
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542324
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_36</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539824
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541798
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539974
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541122
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540302
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542230
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539806
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539858
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539926
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540130
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540686
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30550530
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_42</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539824
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30543600
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541402
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539806
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539858
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539926
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540130
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540842
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539916
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540536
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_23_2229226_34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541020
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30576454
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541020
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30576454
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539946
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540688
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541606
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539974
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541122
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540272
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541296
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539804
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540152
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540942
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540242
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30546180
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30566664
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30544410
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539806
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539858
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539924
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539936
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539926
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540130
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540686
-----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30550530
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540524
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540412
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540428
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542324
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540842
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540296
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539912
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540076
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540714
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540396
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541478
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30549650
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539824
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542934
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541798
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30552246
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540074
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30543600
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539930
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540770
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542350
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540456
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30544238
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30544044
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541114
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30548652
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539882
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539888
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540138
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541224
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542100
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541558
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540882
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540780
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539956
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540978
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539834
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540568
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540916
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539916
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540642
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540536
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540158
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30553798
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30545074
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540804
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541104
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541234
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_23_2229226.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30539970
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540372
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541436
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542068
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542284
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542678
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541106
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540302
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542230
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541524
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540530
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542172
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540634
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30540324
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30542838
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541402
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_23_2229226.30541070
</commentlist>
</conversation>
