Yes, this is because Puppy 4.3.1 and Wary 5.1.2 were originally compiled from source in T2, and T2 is stuck on using a very old version -- 3.1.8. I just checked the T2 website, yep they are still using that old version (released in 2007).
I downloaded the latest, 5.2.12, and configured it like this (these are the recommended options for Linux):
# ./configure --libexecdir=/lib/dhcpcd --dbdir=/var/lib/dhcpcd --sysconfdir=/etc
Here is the PET (46KB):
Something is tugging at my memory about this... yes, I did compile dhcpcd 5.2.5 in Wary late last year. But, it wasn't put into Wary 5.1.2, must have forgot about it.
Comments:Posted on 16 Jul 2011, 15:04 by Iguleder
Woof XKB bug
Barry, there's a problem with Woof that I've been investigating for a couple of weeks: all Ubuntu/Debian (and maybe other builds) wooflets have a critical X crash once it starts, because of the xorg_base template.
In that template, /usr/share/X11/xkb is a symlink to /etc/X11/xkb, but that directory (which comes from the kbd-data packages, something you missed in dpup) is needed for the keyboard driver and it must be placed under /usr/share/X11.
Posted on 22 Jul 2011, 9:43 by BarryK
I don't see that there is any problem with the symlink. If you select the kbd-data package to be installed, it will follow the symlink, so the kbd data will get installed to /etc/X11/xkb.
What you would need to do is get rid of the old /etc/X11/xkb, contents, which is builtin to Woof.
Posted on 22 Jul 2011, 9:46 by BarryK
dhcpcd kernel version sensitive
I'm not sure, I think that dhcpcd is very kernel-version-sensitive. It needs to be compiled for the kernel version source that it is to be used with.