Yes, the files are slightly different sizes, and diff-a spits out a ton of junk (remember, they're mpeg4s, and 40+MB each.. )

Comparing the strings output, they starts out similar, and with some binary looking characters in them, too..

43810573 Nov 06 16:25 x.mp4 (Net::FTP)
43811351 Nov 06 13:45 y.mp4 (Fetch)

%> head *.txt
==> x.txt<==
ftypmp42 mp42isom kmoov lmvhd çġtrak \tkhd $edts elst çmmdia mdhd
==> y.txt <==
ftypmp42 mp42isom kmoov lmvhd çġtrak \tkhd $edts elst çmmdia mdhd

had to stop the strings, cuz each file was generating around 24 MEGs of "strings"!!

Clearly, fetch and Net::FTP are not doing the same thing!

In reply to Re: Re: Net::FTP on OSX10.3 corrupting files by manchot
in thread Net::FTP on OSX10.3 corrupting files by manchot

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.