Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
To quibble a bit: You would only have 11 copies if the versioning file system didn't support generation limits, or the generation limit was 11 or higher. I worked with RSX11M for most of the first decade of my career, and I found the following to be my friend: PIP *.*/PU:2 ---- Original message ---- >Date: Thu, 03 May 2012 14:33:44 -0400 >From: discuss-bounces+j.natowitz=rcn.com at blu.org (on behalf of Richard Pieri <richard.pieri at gmail.com>) >Subject: [Discuss] Versioning File Systems >Cc: discuss at blu.org > >On 5/3/2012 12:13 PM, Gordon Ross wrote: >> No, but combined with an auto-snapshot service, I'd call it "close". >> You would not get a new version on every file change, but one can >> make snapshots pretty frequently, i.e. every few minutes. >> Anyway, probably getting off topic here. Sorry. > >Not off topic for the list so I'll change the Subject. > >Snapshots aren't at all close to versioning. A versioning file system >keeps (or can keep; one can usually configure how many versions to keep) >every version of a file saved. File system snapshots get the file >system state when the snapshots are made. > >For example: create a ZFS snapshot. Create a file. Edit it and save >it. Repeat nine more times. Create another snapshot. How many >versions of the file do you have? You would have just one on ZFS. You >would have all eleven on a versioning file system. > >-- >Rich P. >_______________________________________________ >Discuss mailing list >Discuss at blu.org >http://lists.blu.org/mailman/listinfo/discuss
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |