[SunRescue] Tape drive

[Joshua D. Boyd]

Yeah, I've seen the Murray Hill setup.  Darn cool.

Still doesn't do what I want though.  For instance, what if I save the
file ten times in a minute.  Then, all those changes will be saved in
ram, and only some time later when you are done editing does the change
get saved to disk.

What I want is for all the changes (or diffs of them) to be saved to disk.
When the disk runs out of space, then start deleting the oldest diffs.

Perhaps there should be a way to set it to delete in some pattern than
just from oldest to most recent.  Not sure.

Of course, when I say saved to disk, it makes some assumptions about the
way the computer works.  Like that I load a file to memory and have to
save it.  Really, I should just open the file and work, and every
keystroke is saved to disk.  

But, to really achieve that, we don't just need new applications, but
probably a whole new OS to enforce this method of working.

Another thing on my todo list.  Need to familiarize myself with mach
first.  Perhaps I'll load xmach on my 486 and port a pppoe driver to it.

--
Joshua Boyd

On Sat, 19 May 2001, Ken Hansen wrote:

> Have you looked at the plan 9 file system? The way the boys in Murry Hill
> have implemented file storage is very cool (RAM to local disks, local disks
> to optical discs for long-term backup - files propogate through this
> hierarch as they are accessed, if they stagnate, they page out of RAM to
> local disk, then local disk to optical - there is only one copy at any one
> time - no need to delete in most circumstances, and the backups are keyed to
> points in time - like nightly)...
> 
> Cool, but a lot of set up for just one tinkerer...
> 
> Ken
> 
> ----- Original Message -----
> From: "Joshua D. Boyd" <jdboyd at cs.millersville.edu>
> To: <rescue at sunhelp.org>
> Sent: Saturday, May 19, 2001 8:13 PM
> Subject: Re: [SunRescue] Tape drive
> 
> 
> > Can you make the things keep a complete journal of all changes, so that
> > you can effect roll back the clock to any previous state?  I've always
> > wanted a file system that could do that.  I've seen a few that kinda did
> > what I wanted, but they were kinda strange.  More like an NFS serverlet
> > strapped onto the front of a code revision system.  Maybe someday I'll
> > write my own.  From what I've seen, if could be written as a NFS server
> > without to much trouble.  Then, you just mount the NFS file system locally
> > as something like /home.  Then, no matter how stupid your users are, you
> > could probably restore any mistakes they make.
> >
> > --
> > Joshua Boyd
> >
> > On Sat, 19 May 2001, Bill Bradford wrote:
> >
> > > On Sat, May 19, 2001 at 06:45:43PM -0500, Bill Bradford wrote:
> > > > They simply DO NOT BREAK.
> > >
> > > Oh, the other thing - built-in filesystem snapshots.
> > >
> > > Say you've got something in a NetApp-mounted directory, that you
> > > accidentally deleted:
> > >
> > > On a netapp:
> > >
> > > # rm passwd
> > > # ls passwd
> > > passwd: No such file or directory
> > >
> > > "oops"
> > > "oh shit"
> > >
> > > # cd .snapshot
> > > # cp passwd ../
> > > # cd ..
> > > # ls -al passwd
> > > -r--r--r--   1 root     sys         2398 May  9 13:51 passwd
> > > #
> > >
> > > "yay"
> > >
> > > You can have it snapshot the filesystem once an hour, once a day,
> > > etc... and you can have multiple snapshots, as well, if you need
> > > to get an older version of a file..
> > >
> > > Bill
> > >
> > > --
> > > Bill Bradford
> > > mrbill at mrbill.net
> > > Austin, TX
> > > _______________________________________________
> > > rescue maillist  -  rescue at sunhelp.org
> > > http://www.sunhelp.org/mailman/listinfo/rescue
> > >
> >
> > _______________________________________________
> > rescue maillist  -  rescue at sunhelp.org
> > http://www.sunhelp.org/mailman/listinfo/rescue
> 
> _______________________________________________
> rescue maillist  -  rescue at sunhelp.org
> http://www.sunhelp.org/mailman/listinfo/rescue
>