Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ll-xn!husc6!spdcc!dyer
From: dyer@spdcc.UUCP
Newsgroups: comp.protocols.tcp-ip
Subject: Re: FTP advisory messages
Message-ID: <268@spdcc.COM>
Date: Thu, 17-Sep-87 20:02:39 EDT
Article-I.D.: spdcc.268
Posted: Thu Sep 17 20:02:39 1987
Date-Received: Sat, 19-Sep-87 10:24:36 EDT
References: <8709172107.AA16664@beno.CSS.GOV>
Organization: S.P. Dyer Computer Consulting, Cambridge MA
Lines: 18

In article <8709172107.AA16664@beno.CSS.GOV>, rick@SEISMO.CSS.GOV (Rick Adams) writes:
> What I really want to know in this example is the packing (and
> possibly byte ordering) of characters in a word. I don't believe that
> all Unix implementations are 8 bits = 1 character = 1 byte. I think the
> C/70 has a 9 bit byte or something. It runs Unix (I don't have my manuals
> with me, but you get the idea)

Puhleeaze.  The C/70 has *10* bit bytes and *20* bit words, in 68K-style
byte order.  As you might expect, IMAGE mode was an exercise in bit
manipulation.  As to how it packed them together, well, that depended
on what version of ftp and ftpd we had released at the time.  Luckily,
this confusion was never inflicted on customers, only in-house.  I remember
that the switch between one encoding scheme to another was only slightly less
disruptive than the cutover from NCP to TCP...
-- 
Steve Dyer
dyer@harvard.harvard.edu
dyer@spdcc.COM aka {ihnp4,harvard,linus,ima,bbn,m2c}!spdcc!dyer