In the last days I took (and even had) the time to install a VM with Fedora 10, updated all the packages after installation, and created a new linux-f10-pango port (v 1.28.3). I did this because the port has a security vulnerability according to our VuXML DB and there where more and more reports in the last months from users which had a problem with this.
During the update of the port I noticed that the port does not contain a FORBIDDEN entry, just portaudit complains about it because there is an entry in the VuXML. That is not nice. I was told that the ports slush will be lifted soon (I need to bump some PORTREVISIONs), this means that I can commit the update probably tomorrow, just in time when the new RPM should hit the FreeBSD distribution infrastructure (MASTER_SITE_LOCAL is updated once a day from a specific folder in our home directories).
Thanks to Luchesar V. ILIEV for the nice writeup of what to install in Fedora 10 to be able to build RPMs, and the description of how to build your own RPM.
I experimented a little bit with the order of directories to backup in tarsnap.
Currently I use the following sorting algorithm:
- least frequently changed directory-trees first
Every change – even in meta-data – will affect the following data, as tarsnap is doing the de-duplication in fixed-width blocks (AFAIR 64k).
- for those directory-trees which change with the same frequency: list the bigger ones first
Implicitly I assume that the smaller ones are much smaller than the bigger ones so that the smaller part which will be backed up will not be noticed because of the bigger change. For my use cases of tarsnap this is true.
- if changes in a directory-tree are much much bigger than anything else, but the directory-tree has a medium change-frequency, put it even before less-frequently changing stuff
I do not want that a small change triggers a big backup, but a big backup can contain the remaining small part.
- if you backup home directories (even root’s one) and they do not contain much data, put them before directory-trees which change a lot daily
I do not want that a login triggers the transfer of data in other directory-trees which have not changed.