On Thu, 30 Dec 2004, Hans Reiser wrote: > >A working undelete can either hog disk space or die the moment some > >large write comes in. And if you're at that point, make it a versioning > >file system > > > Well, yes, it should be one..... > > darpa is paying for views, add in a little versioning and.....
If the "view" is something between a transactional view in a SQL database and a device-mapper snapshot, then yes, it might be close enough. There's however always the problem of capacity conflicts, and there may need to be a switch that prefers "keep older versions" over "discard older versions" so that the admin with - by your leave - idiot users has a chance to save his users' a**e*. > >- but then don't complain about space efficiency. > > This is an area where apple was smarter than Unix. Having a trash can > is what real users need, more than they need performance.. Does Apple's trash can help against files that get overwritten in situ? If not, it's insufficient to fix another common failure. My Mom is "prone" (is that word applicable to human behavior?) to open a file (say, a half year schedule of the local community), edit it, without saving it under a new name - by the time she's completed her edit, she has forgotten to rename it and boom, old file dead. Next week she wants it back... > I would however auto-empty the trash can when space got low.... That isn't desired. See above. > Well, it hasn't been coded solely because we haven't gotten around to it > what with all else that needs doing and still needs doing. Remind me > about this in a year.:) Save this mail to a file and have atd mail it to you. Or use a calendar :) -- Matthias Andree
