colinux-devel

[coLinux-devel] scp'ing files

[Jason A. P. <pat...@pc...>]

SSH from cygwin works fine.  I haven't had any problems with it 
whatsoever.  However, I don't seem to be able to get scp'd files to 
work.  Whether it be inside the coLinux environment scp'ing to an 
outside server, or from the outside server to the coLinux environment.  
It's also just as bad (with only a few bytes transferred) scp'ing from 
the Windows/cygwin environment to the coLinux machine.  Don't know 
what's going on.  It seems that most other networking types work fine 
(i.e., http, ftp, etc.).


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

Re: [coLinux-devel] scp'ing files

[Jason A. P. <pat...@pc...>]

Jason A. Pattie wrote:

> SSH from cygwin works fine.  I haven't had any problems with it 
> whatsoever.  However, I don't seem to be able to get scp'd files to 
> work.  Whether it be inside the coLinux environment scp'ing to an 
> outside server, or from the outside server to the coLinux 
> environment.  It's also just as bad (with only a few bytes 
> transferred) scp'ing from the Windows/cygwin environment to the 
> coLinux machine.  Don't know what's going on.  It seems that most 
> other networking types work fine (i.e., http, ftp, etc.).

Sorry.  I guess the mailing list is a little slow getting back to me,
but I found something interesting.  After finally getting the kernel
transferred over, I tried scp'ing the linux patch file, and it worked!
It's only 116KB.  This may mean something?  Small files are OK, but
larger ones will fail?



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

Re: [coLinux-devel] scp'ing files

[John L. <jo...@su...>]

I assume you're using the latest version of colinux?  The older versions 
had a bug that caused corruption of packets over large transfers.

John

Jason A. Pattie wrote:

> Jason A. Pattie wrote:
>
>> SSH from cygwin works fine.  I haven't had any problems with it 
>> whatsoever.  However, I don't seem to be able to get scp'd files to 
>> work.  Whether it be inside the coLinux environment scp'ing to an 
>> outside server, or from the outside server to the coLinux 
>> environment.  It's also just as bad (with only a few bytes 
>> transferred) scp'ing from the Windows/cygwin environment to the 
>> coLinux machine.  Don't know what's going on.  It seems that most 
>> other networking types work fine (i.e., http, ftp, etc.).
>
>
> Sorry.  I guess the mailing list is a little slow getting back to me,
> but I found something interesting.  After finally getting the kernel
> transferred over, I tried scp'ing the linux patch file, and it worked!
> It's only 116KB.  This may mean something?  Small files are OK, but
> larger ones will fail?
>
>
>

Re: [coLinux-devel] scp'ing files

[Jason A. P. <pat...@pc...>]

John LeSueur wrote:

> I assume you're using the latest version of colinux?  The older 
> versions had a bug that caused corruption of packets over large 
> transfers. 

Hmm.  Possibly not.  I'm using the 0.5.3 download from SourceForge 
released 02-14.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

Re: [coLinux-devel] scp'ing files

[Jason A. P. <pat...@pc...>]

Jason A. Pattie wrote:

> SSH from cygwin works fine.  I haven't had any problems with it 
> whatsoever.  However, I don't seem to be able to get scp'd files to 
> work.  Whether it be inside the coLinux environment scp'ing to an 
> outside server, or from the outside server to the coLinux 
> environment.  It's also just as bad (with only a few bytes 
> transferred) scp'ing from the Windows/cygwin environment to the 
> coLinux machine.  Don't know what's going on.  It seems that most 
> other networking types work fine (i.e., http, ftp, etc.).

I'm attempting to transfer the kernel into the Debian 1GB filesystem.  
I've tried 'dd if=linux-2.4.24.tar.bz2 | ssh root@colinux tar -C 
/usr/src -jxf -' as a last ditch effort to maybe uncover whether it's a 
difference between scp and ssh or not.  Apparently, it happens with ssh 
as well.  I noticed an interesting effect, though.  It appears that only 
the first or a few packets are transmitted between the coLinux 
environment and the Windows environment.  Further traffic just ceases.  
I have no idea what's causing this, either, since existing ssh sessions 
continue to work.  I exited one of my ssh sessions while attempting to 
do the above tar command, and my ssh session would not completely exit.  
I had to type '~.' to terminate it and get back to my cygwin prompt.

I find it strange that apt-get install's work fine which use HTTP 
transfers, but scp and/or ssh don't.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

Re: [coLinux-devel] scp'ing files

[Jason A. P. <pat...@pc...>]

Jason A. Pattie wrote:

> SSH from cygwin works fine.  I haven't had any problems with it 
> whatsoever.  However, I don't seem to be able to get scp'd files to 
> work.  Whether it be inside the coLinux environment scp'ing to an 
> outside server, or from the outside server to the coLinux 
> environment.  It's also just as bad (with only a few bytes 
> transferred) scp'ing from the Windows/cygwin environment to the 
> coLinux machine.  Don't know what's going on.  It seems that most 
> other networking types work fine (i.e., http, ftp, etc.).

Sorry for replying so many times to my own post, but, this is very 
interesting.  I apt-get install'ed tcpdump and started a dump of eth0.  
The moment I did that, the dd piped through SSH to tar started working.  
An uninterrupted stream has so far ensued.  It's a bit slow, probably 
due to the fact that every packet is being dumped to the coLinux 
console, but at least it's working.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.