From: "Sangmoon Kim" <dogoil@etinsys.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: MPC860 Linux-2.6.12.2 wu-ftpd error
Date: Fri, 22 Jul 2005 11:35:41 +0900 [thread overview]
Message-ID: <007301c58e66$10df1170$212d4cdc@smkim> (raw)
Hi,
I'm porting linux-2.6.12.2 on a custom MPC860 board.
It boots okay, but whenever I connect to it through ftp,
I get the following error.
[dogoil@genesis ~]$ ftp 192.168.0.3
Connected to 192.168.0.3.
220 kvme316 FTP server (Version wu-2.6.1(1) Mon Mar 7 07:50:41 MET 2005)
ready.
530 Please login with USER and PASS.
530 Please login with USER and PASS.
KERBEROS_V4 rejected as an authentication type
Name (192.168.0.3:dogoil): dogoil
331 Password required for dogoil.
Password:
421 Service not available, remote server has closed connection
Login failed.
No control connection for command: No such file or directory
ftp>
It goes well with linuxppc_2_4_devel (gotten from denx few days ago)
and the same disk image.
On a custom MPC8245 board there is no such problem.
Is it the problem of linux-2.6.12.2?
Did I get something wrong?
Best regards,
Sangmoon Kim
reply other threads:[~2005-07-22 2:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='007301c58e66$10df1170$212d4cdc@smkim' \
--to=dogoil@etinsys.com \
--cc=linuxppc-embedded@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).