Alexander Birch on 11 Sep 2004 20:53:02 -0000 |
On Sat, 11 Sep 2004 16:45:49 -0400, eric@lucii.org <eric@lucii.org> wrote: > On Sat, Sep 11, 2004 at 04:20:17PM -0400, Alexander Birch wrote: > > On Sat, 11 Sep 2004 14:33:38 -0400, John Sladek <jsladek@comcast.net> wrote: > > > I've had this happen when ftp'ing graphic files with out changing to binary > > > mode first. > > > Not sure if that helps.. > > > > This happens when ftping between a windows box and a linux box. The > > windows box uses a carriage return and a new line, i.e., \r\n Where > > Linux just used \n. > > > > This is yet another reason not to use windows. > > > > Alex > > That's an interesting theory (and I've had files corrupted in just this > way) but I'm pretty sure that's not the case here. For one, there is a > single byte changed - and it's not from \n to \r or vise-versa. Also, > these have not been anywhere near a Windows box (well, the computer > adjacent to it on the table runs NT but you know what I mean.) I'm giving up on bottom posting... I am never said that this was the cause of this problem, but if you looked at the message that I was replying. I thought that was the point of bottom posting, you could see to what I was replying. Alex -- "Gno Gnus is Good Gnus" ~~The Unofficial Motto of Microsoft www.lifesabirch.org ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|