> Writing a report will not harm much for my aufs work. The report will be > something like how to use squashfs and aufs (or other module) > effectively. I am not sure it will be whether "the current use in SLAX > is best" or "there is another better way". Ah, ok then :) In that case, I am really interested if you can find a new way of how to do things more effectively in Slax, the current approach is old (unioning several squashfs filesystems as ro layers and then use tmpfs layer for rw).
What bothers a lot of Slax users is 'saving changes', that means, if tmpfs is used for writing then it is needed to save and then restore the changes during reboots. If other on-disk filesystem is used for writing then there is no need to 'restore' the changes (since it is not lost during reboot), but in case of vfat for example it has a lot of limitations (vfat is not posix compatible, however users prefer it since most USB flash drives are formated with vfat or ntfs). So I would say the most problems do not lay with squashfs, but rather with the tmpfs/ondisk_changes. Users would like to see some way of SNAPSHOTing, e.g. a possibility to switch between different 'changes versions' on the fly, and save the changes to any filesystem, but I think this is impossible :) > I know that you don't force me to do something else as a return of > donation. But when I think about what will I do next in aufs, I'd like > to choose something good for donators. The report will be the first > step. It may result in "no news", or "another better way". > If it result in "another new project instead of aufs", then I will ask > everyone how it will be. Until then, I hope you would not stop me. I welcome everything you do since you can do it THE BEST :) Thank you Tomas M slax.org ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
