I've lost that Drupal feeling for good now. Maintaining it was a bit too much hard work. Whilst trac is still a bit of work, the database structure is a lot easier to use and as such access my data.
All blog posts and comments have been retained, as has my image gallery. There are a few errors in the migration, but they are acceptable.
So welcome to new the site and enjoy :)
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.Basically PuTTY sends linux console style home/end by default. It has a toggle for rxvt style, but that's provided rxvt (and as such it's termcap entry) was compiled with -DLINUX_KEYS, which the BSD termcaps are not. This isn't good :(So I've spun a patch for PuTTY that changes the default home/end to match XTerm (as that's the default $TERM it sends) and changes the rxvt toggle to send the default style that rxvt expects. You can download the diff and/or a win32 binary I've built as Windows machines don't normally come with a compiler. I've sent the patch upstream - and hopefully it will be accepted so that PuTTY works out of the box for BSD and Linux servers.
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. Yes, I hear your gnashing and grinding of teeth as what is there currently just works out of the box. What I propose will also work out of the box :)The network modules will not vanish over night, as there are some parts that will not be brought over such as the system or arping modules as they don't make sense as init scripts. You can replicate the system module by configuring dhcpcd-5 per interface/ssid with a static configuration.When will this happen? Well, it will start to happen when dhcpcd-5 is released, which isn't that far away. Why wait for dhcpcd-5? Glad you asked! dhcpcd-5 takes care of a lot of the network management for you. It now works as one daemon, not one per interface. It manages your routing table for you and allows DHCP created routes to be changed. The last feature is to pickup PTP interfaces and give them a default route to their destination address so that it integrates seamlessly with PPP and VPN clients.But what about the other DHCP clients - I want to use dhclient with ifplugd/wpa_supplicant.You have two options here - keep on using the exiting network modules or script ifplugd/wpa_supplicant yourself. Or use something else like NetworkManager.