So, my experiences so far trying to get woody running have met with a mixture of success and frustration. I have managed to get a semi functional system going, but I still get OOPses whenever I run some programs (one at startup, several whenever I run vim, or when I try to run apt-setup, also quite often when I install packages).
Networking is not working, and /proc is also not working, though df says that it is in fact mounted (though df also says that / is not mounted, so I don't think it's quite working).
One thing I noticed about the OOPses is that they all seem to be invalid page requests at 600000fc (the f could be a 1, I am running it with the composite video out, and the characters are a little fuzzy). Logins do not work properly, but there is a single user shell running on VC1. The problem is that half the time the config scripts from the debs fail with an oops, so a lot of things are left un-configured and as a result the system is half hosed.
I get a strong feeling that the problem is in the kernel, and is the same bug experienced by others when using potato. The new libc might make more frequent use of the system call that is broken, and so woody is broken on the WP. I'm curious to see what others are experiencing. What oops messages are you getting on potato/woody. Are all the oopses the same? How much memory is in your WP? Does anybody know what the start address of ram is on this thing?
I have 16Mb of ram in my WP, and get invalid page requests at 0x600000fc, same regardless of the whether swap is activated.
BTW, thanks to Dave for pointing out the debian archive. If I get too frustrated I might just use potato.