I’m trying to email myself a large file from my laptop to a UNIX based workstation by using a file splitting program that splits large files up into emailable sized pieces. Along with the split files is a bat file that runs a DOS copy and merge command. It is in the format of:
Files 1 thru 5 are 4Megs each and merging them together makes a 20Meg zipped file which expands out to say 32Meg when unzipped. I kind of recall that UNIX has a “cp” command that is the same as DOS “Copy” command, but I don’t know which option flags to turn use. How would I do the same thing on a UNIX box?
You can concatenate them using cat regardless of what kind of file they are. (That is, in fact, what cat means.) Unix doesn’t make the text/binary distinction DOS and Windows and other OSes do: A file is a file.
Other OS’s don’t either. Well, the Mac has multiple forks that can confuse things, but a file is a file is a file. It’s up to a program to determine if that files means anything, even on Unix. Try opening a so-called binary in TextWrangler on the Mac or Notepad on your Windows box – you’ll see that there’s no filetype discrimination there. Conversely try to open an binary with vi in Unix. Some deal.
Yeah, you can cat a jpeg to a text file to an executable, but it won’t be useful unless you have an application that understands it, and that goes for any platform.
Some networks only work with 7-bit bytes, meaning the normal 8-bits that make up everything on a computer don’t fit. That why you you binhex or uuencode and so on, and it’s pretty much all transparent these days. That goes for any OS.
FTP still has a binary/text distinction, too, and most FTP programs are transparent. All text mode does is translate line endings for you if they’re different. The different platforms use various combinations of ASCII 11 and ASCII 13 to define what ends a line, so if you’re not working mixed environments, binary is fine.
It worked on my parasolid CAD data quite nicely. 