this seems to confuse the device into giving a dump of a file from the OS that among other things tells me this:
no/etc/CGI_ds.confstatusaction/tmp/tmpfile.XXXXXXrt/etc/inetd.conftelnet_enablenetworkwttelnetdtelnet stream tcp nowait root /usr/sbin/telnetd /bin/mv -f %s %s 2>/dev/null/etc/rc.d/rc.xinetd

Anyway, this got me thinking that telnet.cgi still actually exists. Truth is that it does seem to be there. If you try to use it in the same way as setup.cgi ie. by passing it a parameter it doesn't have an error.

http://IPoftheNSLU2/Management/telnet.cgi?enable=true - while not actually enabling it it proves that telnet.cgi is present and therefore if someone could locate telnet.cgi in the firmware download and see what parameters it is looking for maybe we could actually use telnet again...

I look forward to anything anyone is able to find out about this. Good luck!

Thanks Tony, yes I'd read your posts (on this and my other thread) before posting mine. As I have this in an office situation (not just me using it) and need stability I really don't want to use anything other than the latest official release of the firmware so I'm loathe to go back to the older firmware.

I'm hopeful that with the discovery we need to use parameters someone will work out how to do it - it seems to me that the original telnet.cgi did not require that.