From: Gerrit Van de Velde <gvd@denayer.wenk.be>
To: "Kevin P. Dankwardt" <k@kcomputing.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: remote access via shell
Date: Tue, 09 Mar 2004 17:24:11 +0100 [thread overview]
Message-ID: <404DEFAB.8070804@denayer.wenk.be> (raw)
In-Reply-To: <KCEOLLHGFJIAFNAMGACHEEPJDFAA.k@kcomputing.com>
I'm using sshd (OpenSSH 3.8-p1 i believe) and sftp-server which are 394k
and 60k in size.
Their makefiles are not well adapted but if you have "Building embedded
linux systems" of O'Reilly, you'll build it without any problem
Kind regards,
Gerrit Van de Velde
Kevin P. Dankwardt wrote:
>I have a ppc 5100 that is currently running Linux. I also have downloaded
>and looked at the ELDK. Neither appear to have a telnet nor a ssh daemon.
>What daemon for remote access is recommended? Are there small versions
>especially appropriate for embedded use? Versions that have Make files
>conducive to cross-compilation for PPC?
>
>Thanks,
>Kevin Dankwardt
>
>
--
Kind regards,
ing. Gerrit Van de Velde
Onderzoeksgroep Digitale Technieken
W & K, Campus De Nayer
J. De Nayerlaan 5
2860 Sint-Katelijne-Waver
Tel. 015 / 31 69 44
Fax. 015 / 31 74 53
http://emsys.denayer.wenk.be
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-09 16:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2D9AB865A49FD511914700105A0EF679016C4909@morse.smart.lfk.eads.net>
2004-03-09 13:03 ` AW: Compiling glibc-2.3.2 (debian) on mpc8xx ;-) David Jander
2004-03-09 14:20 ` remote access via shell Kevin P. Dankwardt
2004-03-09 15:14 ` Wolfgang Denk
2004-03-10 14:31 ` RAM Disk problems Kevin A. Sapp
2004-03-10 15:00 ` Wolfgang Denk
2004-03-10 17:35 ` Kevin A. Sapp
2004-03-10 15:03 ` Jaap-Jan Boor
2004-03-09 16:24 ` Gerrit Van de Velde [this message]
2004-03-09 14:26 remote access via shell VanBaren, Gerald (AGRE)
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=404DEFAB.8070804@denayer.wenk.be \
--to=gvd@denayer.wenk.be \
--cc=k@kcomputing.com \
--cc=linuxppc-embedded@lists.linuxppc.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).