On Tue, 2009-03-10 at 16:03 -0600, TekBudda wrote: > > My NAS (DNS-323, FW=1.04) is using ext2. If it were up to me I'd use > > ext3 because of the journaling. > This was original thought as well. I know there are gobs of other > journaling system out tehre, but I imagine ext3 is likely the most > common & stable in today's world....but I could be on crack. I > supposes it would have the advantage of not getting fragmented as > well. > > The data would be a mixture of documents & media files at this > point...but who knows. > > > Using ext2 or ext3 allows you to retain all the file metadata that a > > windows share needs as well as have the data that xNIX needs to share. > > It's fairly straight forward to build a SAMBA server around a Linux > > formated drive. > Do I need to do anything special for storing my WIndows profiles or > anything or just build teh share & away I go? I imagine it is that > simple... most things in Linux are...LOL! ;-) The only consideration that I cared about was: Are these shares related to a particular user or are they 'globally' shared? My answer was that they are globally shared and therefore no specific access permissions needed to be setup.
> > > <pimp mode="ON"> > > Get a copy of "LINUX Networking Cookbook" by Carla Schroder > > One of the single best books on tactical management of Linux > > environments I've found. > > <pimp mode="OFF"> > I iwll have to look into this and see if I can get clearence from the wife. > I'd lend you my copy but I refer to it at least once a week so I really don't want to do without it. You could check the libraries too - they may well have a copy and the price is right! > > > This is a completely different can. If you make the problem slightly > > more generic you wind up having to arbitrate 'N' of 'M' updates. ie. > > you make a change to the 'slave' copy on your flash drive, your wife > > makes a change on her 'slave' copy and the master is updated via > > automated processing. How do you correctly merge the result? Tough > > problem! > > The best (and it's not great) solution I've seen is for every system to > > mark the changed copy 'dirty' and date/time stamp the change. When > > syncing the changes are applied in sequence where possible. > > The desired behaviour will probably change by application though. If > > you edit a friends contact info and your wife deletes the same contact > > info. When you merge with the master do you "Modify, then Delete" or > > "Delete and have an invalid Modify" or "Delete and implicitly add the > > Modified data"? > > I see what you mean with all of this. I have been trying to wrap my > head around it all. I would like start with a databse on the USB > stcik copied from the network...then when I got home copy it back and > mount it. I assume that would be the proper way? If you were the only one that could change it then that would work. But if you are the only one that can change it - why not just have the DB on the memory stick in the first place? If you aren't the only one that can change it then you need to figure out how to merge changes and detect and arbitrate conflicts. > > On other software though.. is that type of sharing possible of would > it take individual set up on each platform? I think this is a bigger problem than you may realize - most apps do not have provision for merge/de-conflict of import data. The ones that do tend to be PIM like where it's routine to 'sync' a device against your computer. > > _______________________________________________ > clug-talk mailing list > [email protected] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
