PuTTY is a good Windows Terminal emulator that supports SSH. As such, you can use it to SSH into your Linux server and administer it. Life was good.Imagine my horror when I used it to SSH into my FreeBSD and NetBSD boxes and my home/end keys didn’t work! Yea gods, editing files became harder. After spending time on why home/end didn’t work on the standard NetBSD console either I had a good idea as to what was wrong.
Whilst the networking scripts I wrote for baselayout and OpenRC are quite powerful, they do come at a price. Here’s some of the cons:
Slow - each net.foo loads every network module Hard to extend - only I really know how the network modules work Has own dependency code separate to OpenRC So what’s the future? Well, the future is scrapping the network module idea and just supplying an init script that can be multiplexed for each network component.
dhcpcd-gtk is a GTK+ monitor for dhcpcd. It uses dhcpcd-dbus to actually talk to dhcpcd and wpa_supplicant. The end game is to be a viable alternative to NetworkManager for wired and wireless setups but without reliance on Linux specific libraries- we just require dhcpcd and GTK+ available on your platform.
At present, dhcpcd-gtk is just an application which sits in the notification area. The icon has several states, showing offline, address negotiation and online.
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.