Re: [microblaze-uclinux] Why telned not work?

[John Williams <jwilliams@xxxxxxxxxxxxxx>]

Hi Paul,

Paul Hartke wrote:

> When is the "'[*] telnetd does not use openpty()'" option not required? 

IIRC you need it whenever /dev is on a romfs filesystem.

the uClibc openpty() library call attempts to open the /dev/ptyN node as
read/write - but the romfs filesystem doesn't recognise the notion of
the 'w' flag being set, even on device nodes.

(my personal solution BTW is to use the CRAMFS type)

> Perhaps its worth automatically selecting this option whenever Telnet is
> selected as a target.  

This is easy enough to do, we just need to update the default settings
that are contained in vendors/Xilinx/uclinux-auto/config.vendor  These
are the default settings that get initialised when you first choose a
platform in menuconfig.

> Do you automatically enable telnet when an ethernet
> device is present?  

No, telnetd is just selected as one of the applications to build in the
default vendor settings (config.vendor as above)

> I'd still like to understand the autoconf mechanism a
> little better at some point.

This is standard uClinux-dist config stuff - no MicroBlaze auto-config
magic here.

It is possible to create dependencies in the uClinux configs - for
example the "does not use openpty()" option is automagically set if
romfs filesystem support is built into the kernel.

While this might seem like a good idea, it creates hidden coupling
between the dist and the kernel, which is probably not so good.  Better
I think to just update the default settings.

This question is such a FAQ, even the most cursory google search should
find it by now.  Feel free to update the FAQ on the Wiki too.

Cheers,

John


> 
> Paul
> 
> Quoting John Williams <jwilliams@xxxxxxxxxxxxxx>:
> 
>>Hi Pavel,
>>
>>Pavel Ivanchenko wrote:
>>
>>
>>>I don't understand, if FTP and HTTP servers work, why Telnet not work.
>>>inetd.conf file:
>>>ftp     stream tcp nowait root /bin/ftpd -l
>>>telnet  stream tcp nowait root /bin/telnetd
>>>
>>>Link on port in services exist.
>>>
>>>If try connecting, receive:
>>>Connecting to 192.168.0.2 ...
>>>[TELNET] CONNECT (<unnamed>/192.168.0.2)
>>>telnetd: All network ports in use.
>>
>>This should be helpful:
>>
>>
> 
> http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/archive/2005/05/msg00019.html
> 
>>Regards,
>>
>>John
>>


-- 
Dr John Williams, Research Fellow,
Embedded Systems Group / Reconfigurable Computing
School of ITEE, The University of Queensland, Brisbane, Australia
(p) +61 7 33652185  (f) +61 7 33654999 (m) +61 403969243
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/