I like trac. It powers a lot of my project websites. Well, all of them infact.It’s written in Python which is a very nice language.trac upgrades are few and far between, there have been no security issues since I’ve been using it and it supports my DB of choice (PostgreSQL) very well.I’m starting to dislike Drupal, which I currently use for this blog.It’s written in PHP which is not a very nice language.
dhcpcd is DHCP client. DBus is an IPC mechanism. Add them together and you get dhcpcd-dbus! dhcpcd-dbus receives interface configuration events from the dhcpcd control socket and emits them to the DBus listeners. dhcpcd-dbus also has methods to release, rebind, stop and query dhcpcd on an interface. This allows users to control dhcpcd to some extent as all dhcpcd opertaions require root privilege and DBus has a fine grained ACL list for accessing these functions which dhcpcd-dbus can optionally use.
As blogged previously BSD systems have issues when you try and change or delete the automatically added subnet route. My patches have now been comitted to NetBSD here and here. If your NetBSD version is 5.99.6 or higher, then you can safely know dhcpcd will work (well, in regard to this anyway).
I’ll try and get them backported to NetBSD-5 and NetBSD-4 in the New Year.
Today I became a NetBSD developer! I’ll mainly be working with dhcpcd in NetBSD and some pkgsrc stuff. I do however have two patches lined up for the main NetBSD src tree- two trivial userland applications for POSIX compat (tabs and a new swtich to unexpand).
this is a small commit with big consequences. Basically it means that dhcpcd will no longer send a default ClientID. You have to specify this behavior. This change has been made so that we mirror the lease credentials sent by the in-kernel DHCP client, the ClientID itself is NOT mandatory for ethernet and it turns out some very badly written DHCP servers do not like ANY ClientID.How does this affect you?
Roy's Blog