From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <3df301650807010840v1ae773cai9a44949e33fad71a@mail.gmail.com> Date: Tue, 1 Jul 2008 10:40:32 -0500 From: "michael block" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> In-Reply-To: <15E613B567802F1BF4A8AB71@F74D39FA044AA309EAEA14B9> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <15E613B567802F1BF4A8AB71@F74D39FA044AA309EAEA14B9> Subject: Re: [9fans] sad commentary Topicbox-Message-UUID: d35b7aca-ead3-11e9-9d60-3106f5b1d025 On Mon, Jun 30, 2008 at 4:45 PM, Eris Discordia wrote: > --On Monday, June 30, 2008 3:11 PM -0500 michael block > wrote: > >> On Mon, Jun 30, 2008 at 2:12 PM, Eris Discordia >> wrote: >>> >>> Fossil/Venti, however brilliant it may look like to the code junkie, does >>> not offer anything for me but added complexity. >> >> i'm using p9p venti on linux, and it's been a total breeze to >> configure and administer. the utility of hist and yesterday in my >> opinion far outweigh the couple megabytes of memory that venti needs >> to be running all the time (i run it on my desktop machine, not a >> dedicated file server). i'm curious to know what backup system you're >> using that is simpler than venti. my interest in plan 9, inferno, >> octopus, &c stems mainly from my using venti for backups and finding >> it to be far better that anything unix had to offer. so it you really >> do have a backup system simpler and more robust than venti, i'd love >> to try it out >> >> -- >> i apologize in advance if gmail has in anyway mutilated this messege. >> stay beautiful! >> > A very effective "backup" method for work on your "desktop:" > > 1. Organize your "creative work" when you "create" them, plan beforehand > > 2. Copy/synchronize the collection to an external hard disk and/or a > solid-state storage device which you detach from your "desktop" computer > after you turn it off, repeat this step depending on how heavily you modify > the work, automate using cron (or Task Scheduler if you're on Windows) > > 3. Copy the entire collection to optical media every once in a while, store > the copy in a safe place venti eliminates step one and simplifies step two. > b. If your data happens to be quite a lot of source code it should be stored > in a version control system which may provide its own backup measures. venti /is/ a version control system. it's practicly the same thing as git, but with sealed arenas > With (now almost obsolete) RCS backing up > should be as simple as tarring one or more directories. CVS and/or SVN > shouldn't pose any harder problems. backing up with venti is as simple as letting a cron job run regards, michael khayyam ravenhurst -- i apologize in advance if gmail has in anyway mutilated this messege. stay beautiful!