Yesterday I deprecated the non-default Fedora based Linux base ports. This means fc6, f7, f8 and f9 will vanish soon (I decided for one month of expiry time). This is because all of them are End of Life upstream since a long time (= no security updates).
The fc4 and f10 ones are still available – even if they are End of Life too – because FreeBSD 7.x can not use something newer than the fc4 one, and we have not tested yet a more recent Linux distribution.
Probably the most easy way to update the Linux base ports to something newer is to stay with Fedora (we have a lot of ports-infrastructure for it already). Unfortunately it is not known if something newer works without problems (missing epoll/inotify support could be a roadblock here in case it is extensively used in a more recent version).
I want to get some time to have a look if a more recent Fedora version is suitable for the use as a Linux base in FreeBSD 8.x+, but I do not have an estimate when I can start and how long it may take. In case someone already tested a more recent Fedora version feel free to share your experience.
At work we have to use a proxy which requires authorization. With previous versions (firefox 3.0.x and 3.5.y for each valid x and y) I had the problem that each tab requested to enter the master password when starting firefox, to be able to fill in the proxy-auth data (shortcut: fill in only the first request, and for all others just hit return/OK). So for each tab I had to do something for the master-password, and after that for each tab I also had to confirm the proxy-auth stuff.
Very annoying! Oh, I should maybe mention that as of this writing I have 31 tabs open. Sometimes there are more, sometimes there are less.
Now with firefox 3.6 this is not the case anymore. Yeah! Great! Finally only one time the master password stuff, and then one time the proxy-auth stuff, and then all tabs proceed.
It took a long time since my first report about this, but now it is finally there. This is the best improvement in 3.6 for me.
The TXT entry outgoing-alex._domainkey.leidinger.net which worked for a long time suddenly stopped being delivered by named (thanks to Henri Hennebert for the HEADS-UP). Every other query I try works so far, it is really just this one entry (resolve timeout). I notified the responsible person, investigation is ongoing.
This means that any verification of my outgoing mail will not work, as the data necessary to verify the signatur is not available. 🙁