-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos E. R. wrote: > > El 2007-05-29 a las 12:59 +0100, Kevin Thorpe escribió: > > [You forgot to email to the list] > >> Carlos E. R. wrote: >>> I remember that. OOo also has this feature. What I talk about is different: >>> it uses one file for each version, with a version field in the file name >>> managed directly by the operating system, not the application program. It is >>> also different from external backup, as it is automatic and continuous, and >>> can be affected by disk failure, of course. >>> >> Novell NetWare did exactly that. Every time you saved a file it wrote a >> new copy and left the old one hidden in 'free' space on the hard drive. >> These old copies only got overwritten when the space was needed, in an >> oversized drive that seemed to be forever. A little utility allowed the >> administrator to retrieve old versions. Saved our bacon quite a number >> of times and I miss it badly. > > Cute :-) > > Yes, that's the thing I'm talking about. > >> The nearest I've seen on Linux is subversion but that's a repository not >> a filesystem. I seem to remember coming across a subversion filesystem >> but it wasn't finished. > > Pity. >
VMS if I remember correctly defaulted to 3 being available but the version numbers incremented (on the setup I was working one could flag files to be archived overnight and ask for them back later). Most editing applications I have dealt with create a backup copy by default so three versions is only a minor improvement. Yes Netware does this and it was great for short term file recovery. Netware still outperforms almost anything else as a secure file store and print server (It is damn near impossible to crack a properly configured Netware server). Not so good at some other server stuff unfortunately, and most definitely $$$ not OSS. I have looked at the idea of using Subversion for this purpose. Theoretically it should be possible to set up a background commit cycle, then use subversions dump mechanism to generate a dump of the latest revisions which then could be stored to wherever for backup purposes. (Already doing this in part for my coding projects). Unfortunately, the down side to this is that filestore can end up cluttered with an awful lot of unused data. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGXU/UasN0sSnLmgIRAikIAKCFsv7qkTqPpq7A6FFvr223mGYM6QCgp5lW 54ei2FKCoyby79WOKO9gxkE= =S1tD -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
