Morning guys,
We're currently working with Voyage 5x which seems to work quite nicely for us, however I can see some upcoming benefits of us using the new 6x release and I wanted to try and clear up a few questions about the new file system which is implemented on the new release. In our application for Voyage we use MySQL to collect data, this is then written to the disk and must remain there after a reboot. At the moment we've always taken care of this by using the WIKI document found here http://wiki.voyage.hk/dokuwiki/doku.php?id=remove_ro which is an anything but ideal situation but has always worked well for us. Now, I assume that with this new move to AUFS it's about time we started doing things properly. At the moment I understand next to nothing about AUFS and how it works but I'm hoping we'll be able to configure it for our needs. If you guys had data you needed to persist on the disk regardless of a reboot or power loss how would you go about it? I know we've talked in the past about having a secondary scratch partition on the disk which we use, is this still our best option? Or does AUFS give us some better configuration options to set some space aside on the same partition as the OS? Aside from the MySQL database which we need to persist I also have a bunch of log files and some XML configuration files generated by our application which we need to keep permanently, other than that most changes can be lost. I'm looking for a solution which is easy to implement and also simple to replicate so we can duplicate the cards quickly. Many thanks guys, I appreciate any pointers. Robert
_______________________________________________ Voyage-linux mailing list [email protected] http://list.voyage.hk/mailman/listinfo/voyage-linux
