Multisession does not refer to the files stored inside the sessions, if it did it would not be possible to use the CD drive for anything else. The contents of the session directories are copied into ram. The rationale behind /archive in multisession is that files in it are not loaded into ram when puppy boots. Files stored inside /root are. If I am running multisession and I put lots of files into the trash they are all loaded into ram next boot. This is unlikely to be what the hypothetical user wants. If I edit a 25 MB video file 10 times reversioning it with a new name and dumping the old ones in the trash they will all still be stored in ram even when I reboot.disciple wrote: How much space would you actually save by archiving trashed items anyway?
I may misunderstand how the multisession system works, but I don't think if you trash a 25MB file it will take up an extra 25MB in your latest session. I think the filesystem will refer to the file in its original location in an old session. So it would only be taking up extra space when you move to a new disc. Can anyone confirm this? I think that's what you were saying Flash?
There is a reasonable amount of work involved but it would be more efficient if the trash was multisession aware. It would be nice to have an app that could search through archive in all the sessions. Even better would be a more sophisticated tool that could show which sessions any file had been revised in, nice(connected to diff?). That said, I'm still not sure how many users multisession really has so this may be unimportant.