console command history

Fox Mulder Quakeman1 at
Thu Oct 16 18:46:34 CEST 2008

Joel Newkirk wrote:
> On Thu, 16 Oct 2008 14:12:26 +0200, Xavier Cremaschi
> <omega.xavier at> wrote:
>> papa-piet a écrit :
>>>> Fox Mulder schrieb:
>>>> I didn't try it with 2008.9 because i only use debian
>>> I did.
>>>  shh into your Neo workerd for me, but scp didn't, it looked like a
>>> timeout.
>>> Greetings
>> Same behavior here, with bash I can ssh, but not scp.
>> Here is the end of a scp -vvv with sh :
>> Here is the end of a scp -vvv with bash :
>> With bash I cannot :
>> scp localfile root at openmoko:/tmp
>> nor
>> scp root at openmoko:/tmp/file localfile
>> Xavier.
> Interesting.  I usually use SFTP instead of SCP, just a matter of habit.
> I tested (Raster's prior image + FSO, uname -a gives "Linux
> 2.6.24 #1 PREEMPT Fri Sep 26 14:13:25 EST 2008 armv4tl unknown")
> and both sftp and scp work for me as expected, with
> "root:Kepdp5b2.52RA:0:0:root:/home/root:/bin/bash" in /etc/passwd.  Oh, and
> I have a root password set.  I've not tested with ssh-key, since I don't
> have that handy here at work.
> My suspicions fall on either differing dropbear ("Dropbear sshd v0.51")
> config or different bash packages.  ("GNU bash, version 3.2.39(1)-release
> (arm-angstrom-linux-gnueabi)", installed from FSO repository)

The first thing i always did on my different distros was to replace
bash-busybox with real bash and replace dropbear with openssh. Maybe you
should try this combo to get scp to work again because i never got any
problems with it.


More information about the community mailing list