Win95/98/NT --> Solaris character issue

[Cole, Timothy D.]

These kinds of problems have been around for a very long time.  Thing is,
there's no really reliable way to know with 100% certainty whether a file is
supposed to be ASCII or binary, and the only way ftp gets around that is to
allow the user to explicitly specify which it is.  That really isn't
practicable with the user interface that Windows provides, and certainly
wouldn't be transparent in any case. This is a software engineering problem
that predates Samba by quite a bit (at least 20 years); if it was soluable,
it would have been solved by now. :(

> -----Original Message-----
> From:	Hoyt, Travis (Contractor) [SMTP:thoyt at harris.com]
> Sent:	Thursday, June 17, 1999 13:36
> To:	Multiple recipients of list
> Subject:	Win95/98/NT --> Solaris character issue
> 
> Had anyone addressed the issue of transfering text files from a Windows
> system
> to a UN*X box and getting the ^M at the end of each line.  I know this had
> to do
> with the line feed/carriage return issue between windows and unix systems.
> My
> question is, has anyone figured out a way, or is there a flag for samba
> to,
> sanitize files so that they don't have those characters
> at the end?  Much the way ftp does when you put it into ascii mode instead
> of
> binary.
> 
> I've looked through some of the docs at the samba site but I'm not having
> any
> luck.
> 
> Thanks,
> 
> Travis