Let's assume people would get a huge banner saying "this is not verified in any way". Do you seriously expect this to matter for more than a few months? We want it all and we want it now. And if it's on the Internet, it must be true.
On the plus side, humanity always adapted to the latest stupidity. It just takes 5-100 years, depending on what example you choose.
I find it fascinating how little knowledge need to have a lot of opinion. Did you ever stop & think about what ISO did? Without ISO and its national counterparts, we would either still trade firewood or have a different organization which goes by a different name, but does the same.
Yes, the OOXML mess was just that: a mess. One wants to scream and shout and shake sense into people.
But to imply that ISO outlived itself over this, believe it or not, relatively small issue.. I don't think so.
Afaik, Git supports Meta/recursive repos where I have one master repo with many subrepos. Thus, it would be best to have a master repo that contains all other repos. That will make replication easier.
The only other requirements would be that it adds all files in a given directory to repo foo and pulls repos bar, baz, quux. Preferably, it would happen automagically & regularly with a throttled connection. Requiring them to click a button in a butt-ugly app is fine, as well. If Windows had cronjobs or I knew VB, I would do it myself, but..
_If_ you decide to do something like this, I will definitely give it a try. And it will finally give me a reason to poke Git:)
First of all, thanks for all the feedback. I appreciate it.:)
It seems that I did not state my requirement well enough and there's some confusion about them. So, here goes again:
* The clients are distributed all over Germany, sometimes all over the world. DSL or better is available at all sites. * Data synchronization must be asynchronous. * Clients must have local shares, slices, working copies, whatever. They must work offline, as well. * Data must be partitionable. While my sister and mother share all their pics, others do not. * Automagic sync as soon as network connectivity is available is a plus. Requiring them to click a button is fine, as well. * Almost all clients will be Windows. * Total amount of storage used is a few dozen GiB. Using a few times that amount on the servers is fine. * It's OK if brains need to be poured over this baby during initial setup. * It's _not_ OK if tech knowledge is required during day-to-day operations. * I will not be on site very often, depending on how far away they live. * It's OK if they are not able to restore anything by themselves. I will just grad whatever and send it per eMail. * I don't like S3 or other cloud implementation. That data is mine/theirs and not storing it elsewhere is better than encryption. Hard drives are too large, anyway. Storage space is not a concern, reproductions of the complete data make it fault tolerant.
Well, this ideal app would treat the directory with private stuff differently than the the one containing photos.
Also, all the end users see is a local directory where they can put stuff into. Nothing more, nothing less. All complexity would be hidden and only visible to me.
I did think this through. I want distributed backups with several, for lack of a better word, working copies checked out on different machines.
I don't need to worry about encrypted backups or anything as all machines involved will be under my control. If any machine is compromised, I lose confidentially, anyway.
That a homebrew solution would suck is a given. This is why I asked/. for readymade solutions.
Actually, I was asking one question. I need both rolled into one. And requiring me to be on site is not feasible. Ideally, they don't even notice that Backups are being made.
I looked at Cleversafe, trying to get through the PR bubblespeak. It seems they are emulating disks, not offering integrated _backup_. As saving from my mom's SD card to a distributed online disk via a DSL line is not feasible, I will most likely need to scratch that idea.
Because that's probably what his wallet contained when he hopped on the plain. It makes sense to take more money with you than you reasonably expect to spend during the day. When you own as much money as he did, that metric will adjust, as well.
Let's pretend I fall for your ad hominem attack so I can answer the valid points you make.
> unfortunately it doesn't have GSM either.
It has bluetooth. I own a cell phone. The N810 does not have GSM, either. Unfortunately, Nokia have very good & logical reasons not to 'fix' this any time soon, so do these people.
> Nor a camera.
Might be useful, at some point. Depending on your target group, a bit more or a bit less so than GPS.
> Nor a motion sensor.
_That_ is a huge pity & an oversight which can not really be explained. Those things are tiny, dirt-cheap & just look at the Wiimote for its potential.
Well, there is OSM which is a good start. Also, you could put Google Earth on it (if there is enough RAM). It might not be useful this very second, but I suspect they will not change the hardware between the first and later batches, so we are stuck with no GPS for a year or two..
Slashdot Mirror
Because they will just download their own cars, for free.
I learned this a decade or two ago in school.. That's old even by /. standards.
Let's assume people would get a huge banner saying "this is not verified in any way". Do you seriously expect this to matter for more than a few months? We want it all and we want it now. And if it's on the Internet, it must be true.
On the plus side, humanity always adapted to the latest stupidity. It just takes 5-100 years, depending on what example you choose.
PS: Open is good, but let's be realistic about the requirements of the average software shop.
Frameworks that do not integrate with each other very well and, apart from Qt, force you to open the resulting application.
I use Linux exclusively, but I make a point of being realistic about its downsides, as well.
(And yes, D-BUS makes the whole integration thing a lot better. As do Qt's GUI plugins)
I find it fascinating how little knowledge need to have a lot of opinion. Did you ever stop & think about what ISO did? Without ISO and its national counterparts, we would either still trade firewood or have a different organization which goes by a different name, but does the same.
Yes, the OOXML mess was just that: a mess. One wants to scream and shout and shake sense into people.
But to imply that ISO outlived itself over this, believe it or not, relatively small issue.. I don't think so.
They have been doing that for decades with next to no negative feedback. What has changed, now?
Will do, thanks!
FYI, the navigation buttons on the left of hand side of openmigration.net are black in Konqueror 4.1.2. Works fine with Iceweasel 3.0.1, though.
Cygwin can do cronjobs? Neat, I will remember that if I ever use Windows, again.
I would code it in Perl, but I do _not_ want to expose my mom to a CLI interface.
If you are being serious..:
Afaik, Git supports Meta/recursive repos where I have one master repo with many subrepos. Thus, it would be best to have a master repo that contains all other repos. That will make replication easier.
The only other requirements would be that it adds all files in a given directory to repo foo and pulls repos bar, baz, quux. Preferably, it would happen automagically & regularly with a throttled connection. Requiring them to click a button in a butt-ugly app is fine, as well.
If Windows had cronjobs or I knew VB, I would do it myself, but..
_If_ you decide to do something like this, I will definitely give it a try. And it will finally give me a reason to poke Git :)
First of all, thanks for all the feedback. I appreciate it. :)
It seems that I did not state my requirement well enough and there's some confusion about them. So, here goes again:
* The clients are distributed all over Germany, sometimes all over the world. DSL or better is available at all sites.
* Data synchronization must be asynchronous.
* Clients must have local shares, slices, working copies, whatever. They must work offline, as well.
* Data must be partitionable. While my sister and mother share all their pics, others do not.
* Automagic sync as soon as network connectivity is available is a plus. Requiring them to click a button is fine, as well.
* Almost all clients will be Windows.
* Total amount of storage used is a few dozen GiB. Using a few times that amount on the servers is fine.
* It's OK if brains need to be poured over this baby during initial setup.
* It's _not_ OK if tech knowledge is required during day-to-day operations.
* I will not be on site very often, depending on how far away they live.
* It's OK if they are not able to restore anything by themselves. I will just grad whatever and send it per eMail.
* I don't like S3 or other cloud implementation. That data is mine/theirs and not storing it elsewhere is better than encryption. Hard drives are too large, anyway. Storage space is not a concern, reproductions of the complete data make it fault tolerant.
Once again, thanks for all feedback :)
Not quite, but I am pondering Git.. It's the one SCM which can do distributed storage right.
Well, this ideal app would treat the directory with private stuff differently than the the one containing photos.
Also, all the end users see is a local directory where they can put stuff into. Nothing more, nothing less. All complexity would be hidden and only visible to me.
Indeed. But as it should support versioning etc, we are back at it being a backup. Not in the sense of 'grab tape, stow it in bank', though.
Being easy to use (as in, not more than 3-5 mouse clicks, total) is one of my main concerns. Git definitely fails in this regard.
I did think this through. I want distributed backups with several, for lack of a better word, working copies checked out on different machines.
I don't need to worry about encrypted backups or anything as all machines involved will be under my control. If any machine is compromised, I lose confidentially, anyway.
That a homebrew solution would suck is a given. This is why I asked /. for readymade solutions.
I have. But I don't want to put the data in anyone else's hands.
Actually, I was asking one question. I need both rolled into one. And requiring me to be on site is not feasible. Ideally, they don't even notice that Backups are being made.
I looked at Cleversafe, trying to get through the PR bubblespeak. It seems they are emulating disks, not offering integrated _backup_. As saving from my mom's SD card to a distributed online disk via a DSL line is not feasible, I will most likely need to scratch that idea.
English is not my first language, but isn't "more ready" wrong?
Because that's probably what his wallet contained when he hopped on the plain. It makes sense to take more money with you than you reasonably expect to spend during the day. When you own as much money as he did, that metric will adjust, as well.
Which goes to show how much closed source sucks. Thanks for re-adjusting my brains.
Thanks.
> I would call you a Whaaambulance
Let's pretend I fall for your ad hominem attack so I can answer the valid points you make.
> unfortunately it doesn't have GSM either.
It has bluetooth. I own a cell phone. The N810 does not have GSM, either. Unfortunately, Nokia have very good & logical reasons not to 'fix' this any time soon, so do these people.
> Nor a camera.
Might be useful, at some point. Depending on your target group, a bit more or a bit less so than GPS.
> Nor a motion sensor.
_That_ is a huge pity & an oversight which can not really be explained. Those things are tiny, dirt-cheap & just look at the Wiimote for its potential.
Well, there is OSM which is a good start. Also, you could put Google Earth on it (if there is enough RAM). It might not be useful this very second, but I suspect they will not change the hardware between the first and later batches, so we are stuck with no GPS for a year or two..