It is currently Tue, 30 Nov 2021 17:03:58 GMT



 
Author Message
 cu, uuencode, compress - data corruption and loss

I've configured a dial-up connection from home using 3.2.4.2, to work
(5.0.0d); I use cu to dial in, connect at 28.8, V42bis. On the machine
at work, I've created 3 files - one, using

find . -name "*" -depth | cpio -o > cpio_file

and then

compress -cF -H cpio_file > compressed_file

and the other 2

compress -cF -H * > compressed_file

The files at this stage are ~450K, 2.4Mb, and 246K respectively.

I separately uuencode all 3, so their sizes are increased by ~35%, using

uuencode local_compressed_file remote_compressed_file > uuencoded_file

I connect from home, and enter

~[node_name]%take uuencoded_file

and get them across with no problem.

I uudecode on 3.2.4.2:

the largest file manages ~122K of decoded output, and then fails
with "No end line", which the file has; the other 2 decode OK.

When I run

uncompress compressed_file

the first outputs the first file only from the compressed_file
(all 46 bytes) and exits; the cpio'ed one manages 65K
and then says "Bad decode table" and exits.

I've tried this using compress from both systems.
What am I doing wrong? Are these files too big for some
part of this operation? I've set up a variety of different connections
between these machines - a SLIP from Windows '95 even,
but I wanted to keep this entirely Unix, as it is part
of a planned site-to-site installation.

Can anyone help?

--
P.R.John



 Fri, 07 May 1999 03:00:00 GMT   
 cu, uuencode, compress - data corruption and loss

P.R.John propounded certain bytes, to wit:
| I've configured a dial-up connection from home using 3.2.4.2, to work
| (5.0.0d); I use cu to dial in, connect at 28.8, V42bis. On the machine
| at work, I've created 3 files - one, using
|
| find . -name "*" -depth | cpio -o > cpio_file
|
| and then
|
| compress -cF -H cpio_file > compressed_file
|
| and the other 2
|
| compress -cF -H * > compressed_file
|
| The files at this stage are ~450K, 2.4Mb, and 246K respectively.
|
| I separately uuencode all 3, so their sizes are increased by ~35%, using
|
| uuencode local_compressed_file remote_compressed_file > uuencoded_file
|
| I connect from home, and enter
|
| ~[node_name]%take uuencoded_file
|
| and get them across with no problem.
|
| I uudecode on 3.2.4.2:
|
| the largest file manages ~122K of decoded output, and then fails
| with "No end line", which the file has; the other 2 decode OK.
|
| When I run
|
| uncompress compressed_file
|
| the first outputs the first file only from the compressed_file
| (all 46 bytes) and exits; the cpio'ed one manages 65K
| and then says "Bad decode table" and exits.
|
| I've tried this using compress from both systems.
| What am I doing wrong? Are these files too big for some
| part of this operation? I've set up a variety of different connections
| between these machines - a SLIP from Windows '95 even,
| but I wanted to keep this entirely Unix, as it is part
| of a planned site-to-site installation.
|

Just use uucp. It has a much better chance at error-free transmission than
cu, and it will be faster since you can skip the uuencode/uudecode part.

--
Jean-Pierre Radley   j...@jpr.com   XC/XT Custodian   Sysop, CompuServe SCOForum



 Sun, 09 May 1999 03:00:00 GMT   
 
   [ 2 post ] 

Similar Threads

1. cu, compress and uuencode; data loss

2. 2.4.19-rc1,2 + ext3 data=journal: data loss on unmount

3. 2.4.19-rc1,2 + ext3 data=journal: data loss on unmount

4. serial port data acquisition without data loss?

5. Looking for uuencode/uudecode & compress/uncompress

6. Processing an compressed,uuencoded file

7. tar, compress, uuencode


 
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software