Using Drupal as a CMS is nice - it’s worked for me very well. However, it’s not made for project management. I just had a static page that people couldn’t add comments or feedback to (well, they could if I enable comments but that gets messy after a while). I do have bugzilla to handle bugs but I find it too overblown and complex for my needs. Don’t get me wrong, bugzilla has it’s place and it’s a solid project- it’s just not suited for my small site.
You may have noticed an interuption to this service…..I finally got too irritated with the lighttpd configuration. Seems there’s a few fastcgi issues which I’m now seeing. Also, development seems to have stalled. :(So, I gave apache another whirl. I don’t recall why I changed from apache to lighttpd, but it was propably speed related. This is due to me running this site on an old VIA C3-2 processor and apache is slower than lighttpd - noticably on that box.
dhcpcd now manages routing in a sane manner across multiple interfaces on BSD. It always has on Linux due to it’s route metric support, but as BSD doesn’t have this it’s a little more tricky. We basically maintain a routing table built from all the DHCP options per interface and change it accordingly. As such, dhcpcd now prefers wired over wireless and changes back to wireless if the cable is removed (assuming both on the same subnet) and this works really well :DIt’s now starting to look quite stable and all the features in dhcpcd-4 appear to be working still so I’ve released an experimental version to get some feedback.
You tag something with a metric. The same somethings with a lower metric take precedence over the same somethings with a higher metric.
dhcpcd has been able to apply metrics to routes on Linux so that we can prefer to route packets over wired instead of wireless. dhcpcd-git is now able to distinguish wired from wireless and can make a metric accordingly.
But how do we teach configuration files about this?
Well, support for multiple instances in dhcpcd is coming along nicely, but I’ve had to pretty much re-write the entire state handling code. The existing code was wait for data or timeout. Then drop into case statements depending on if we timed out and what our current state is.The new code is now based around an event loop, where we register functions to call when we get data or a time has passed.
Roy's Blog