Sounds like the binds didn't fully work.. this is why I'm trying to figure out a better way of doing it.
Best way is to check "mount" that everything goes on properly, and if "dmesg | less" says anything about things not binding correctly.
As for sshd not working while having the extend installed, that could be because some of the binds did take, and the sshd config files were being read from the extend, rather than the NAND. It should've been fine when you rebooted though, that's an odd one.
Try setting up sshd again, as it may just be the config files got mangled. I haven't used sshd on the Pandora, so I can't really help much more than that, I'm afraid.. sorry.
I'm not particularly happy with the dev extend stuff at the moment, as with the aufs binds, you'll essentially get my configuration files ( or at least, whatever configuration files I had at the time I generated the extend. )
A better idea would be to setup a root overlay and install the dev tools into there, so then it's at least unique to your Pandora, and has any of your configuration files on it.
I am however, really quite knackered with things just now, so not sure when I'll have time to take another look at what I was up to with the cross-compiler idea, I'm afraid.
After a second reboot it started working again, don't know what the problem was.
I too think that a cross-compiler-like approach should be better, so everything can be on the SD card. Can't we just setup a compiler like we do today on linux, but the "cross compiler" be the same platform as the current one?
I think something like the DJwillis toolchain would be great, doing an "opkg-target install" would install on the cross-compiler path on the SD, so as not to interfere with the OS on nand.
To use gcc as a cross-compiler is it necessary to build it like that, or is it possible to "convert" a standard gcc into a cross compiler?