jmorton@euler.Berkeley.EDU (John Morton) (10/03/89)
I don't have a copy of Steven Grimm's "Welcome to Binaries" message before me, but as I remember it does not mention the following treachery of uudecode (or at least not strongly enough!): The first file in a uuencoded set has a name on the "begin" line such that if the file is named with that name, the newly opened arc file (with the same name) will immediately trash it. What makes this treacherous is that the _other_ parts of the uuencoded set _must_ be named with the name on the "begin" line for uud to find them. Why is this designed into such a great program? Sorry if this is old news; when you're mad, bandwidth means nothing. "Down John Morton M.E. Machine Shop Down in the basement jmorton@euler.berkeley.edu Etcheverry Hall We hear the sound of machines..." Univ. of Calif.
sgrimm@sun.com (Steven Grimm) (10/03/89)
In article <17919@pasteur.Berkeley.EDU> jmorton@euler.berkeley.edu (John Morton) writes: >The first file in a uuencoded set has a name on the "begin" >line such that if the file is named with that name, the newly opened >arc file (with the same name) will immediately trash it. Yes, uud probably should warn you about that. It's easily tweakable if you have the source. >What makes this treacherous is that the _other_ parts of >the uuencoded set _must_ be named with the name on the >"begin" line for uud to find them. What I usually do is save the parts to "part01", "part02", and so on, then % cat p* >foo % uud foo If uud can't find a file of the appropriate name, it continues to scan the file it's on. I'll add a warning about this to the binaries intro, though (which should be coming your way later today.) --- This message is a figment of your imagination. Any opinions are yours. Steven Grimm Moderator, comp.{sources,binaries}.atari.st sgrimm@sun.com ...!sun!sgrimm