From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Can't get inetd/busybox-telnetd to work
Date: Thu, 6 May 2010 19:24:56 +0000 (UTC) [thread overview]
Message-ID: <hrv528$56b$1@dough.gmane.org> (raw)
I've been trying to get inetd and busybox's telnetd to work, but I'm
stumped.
Here's my inetd.conf file:
telnet stream tcp nowait root /usr/sbin/telnetd /usr/sbin/telnetd
When I telnet to my board, this is what happens:
$ telnet 10.0.0.99
Trying 10.0.0.99...
Connected to 10.0.0.99.
Escape character is '^]'.
buildroot login: root
Login incorrect
I can't figure out why the login is "incorrect". The root user
doesn't have a password.
Telnetd and login are both from busybox 1.16.
When I run inetd in the foreground and tell it to log to stderr it's
completely mute.
What tricks are there to get busybox's inetd/telnetd/login to work?
--
Grant Edwards grant.b.edwards Yow! Is it NOUVELLE
at CUISINE when 3 olives are
gmail.com struggling with a scallop
in a plate of SAUCE MORNAY?
next reply other threads:[~2010-05-06 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 19:24 Grant Edwards [this message]
2010-05-06 19:36 ` [Buildroot] Can't get inetd/busybox-telnetd to work Grant Edwards
2010-05-06 20:07 ` Belisko Marek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='hrv528$56b$1@dough.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox