Something that occurred to me - ok, so you can make a backup of a file (eg foo.conf -> foo.conf.old), and if you edit foo.conf, then SiS splits them back to two seperate files. Wonderful.
But in the meantime, before you've edited foo.conf and the two files are effectively hard-linked together, what happens when Windows crashes (as happens now and again) - foo.conf could get corrupted. And since foo.conf.old is still linked to it, my nice backup is now corrupted too. Wonderful.
This innovation (and yes, I do think it's a new idea - the automation and all), _must_ have an easy way to disable it.
Slashdot Mirror
Something that occurred to me - ok, so you can make a backup of a file (eg foo.conf -> foo.conf.old), and if you edit foo.conf, then SiS splits them back to two seperate files. Wonderful.
But in the meantime, before you've edited foo.conf and the two files are effectively hard-linked together, what happens when Windows crashes (as happens now and again) - foo.conf could get corrupted. And since foo.conf.old is still linked to it, my nice backup is now corrupted too. Wonderful.
This innovation (and yes, I do think it's a new idea - the automation and all), _must_ have an easy way to disable it.
Hey, it's Thursday here...