RE: FTP to AS400 from Unix server gives Hex 0D at end

["Chris Bipes" <chris.bipes@xxxxxxxxxxxxxxx>]

CP/M did it cause when sending to a very dump printer or terminal, CR
only would cause all data to be printed / displayed on the same line.

LF only would cause the printer to roll up a line and continue from the
same column.

Ok I am showing my age again.

Quick survey, anyone besides me ever work with and program in MP/M?  Oh
the memories that are wasting away in my main storage...

Chris Bipes
Director of Information Services
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Simon Coulter
Sent: Thursday, March 04, 2010 9:59 PM
To: Midrange Systems Technical Discussion
Subject: Re: FTP to AS400 from Unix server gives Hex 0D at end


On 05/03/2010, at 4:06 PM, Ken Sims wrote:

> Nope.  The standard for Unix/Linux is to end each line with just 0d.
>
> The standard for _Macs_ is (or at least was) just 0a.  Something in
> the deep recesses of what's left of my mind is telling me that I may
> have read somewhere that that changed.


I suggest your mind has recesses that are fabricating information.

	LF	ASCII	x'0a'	Unix, Linux, and MacOS X
	CR	ASCII	x'0d'	Mac OS up to and including OS 9
	CRLF	ASCII	x;0d0a' CP/M, DOS, OS/2, Win

The list is not complete. Win and OS/2 use CRLF because DOS used it.  
DOS used it because QDOS used it. QDOS used it because CP/M used it.  
Not sure why both characters we chosen by CP/M.