The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Command-line options
Date: Sat, 26 Mar 2016 15:43:07 -0400	[thread overview]
Message-ID: <CAC20D2OKN=emm+cJxDKez19JZKwFoa7C7TbfyNtbGf7_7eu=2w@mail.gmail.com> (raw)
In-Reply-To: <CANV78LSp3o+iAvO8Jnbex1tPMe8c8aidszGpiSr8x5PhNQE+Wg@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]

On Fri, Mar 25, 2016 at 11:09 PM, Charles Anthony <
charles.unix.pro at gmail.com> wrote:

> And Dec's RADIX-50, packing 3 characters into 16 bits. (IIRC the origin of
> the 6.3 filenames. bit I can't document that.)


​Sort of.... before ASCII, DEC used a few other 5 bit codes that were
around such as baudot​ (look at the PDP-1/4 etc and KSR 28). RAD50 was a
natural scheme for storing file name and using bits efficiently.

Which, of course, lead to the abomination of case folding - it's not a bug,
it's a feature 😂

RAD50 gave us the x.y file name form with the implied dot et al. 6.3 and
later 8.3 were natural directions from that coding.   Using the .3 ext as a
type tag of course followed that naturally given that's all that was stored
in the disk "catalog."  [And CP/M and PC/MS-DOS inherit that scheme -
including the case folding silliness even though by that time all keyboard
were upper and lower case and they stored the files in 8 bits].

UNIX of course, would put the "type" in the file itself (magic #) and force
the storing of the dot, but removed the strict mapping of name and type.
Having grown up in both systems, I see the value of each; but agree I think
I find UNIX's scheme better and lot more flexible.

What is funny is that Apple's OSX does it both ways which I find
schizophrenic and my major complaint with OSX (which is still my current
fave but that's another story).

​Clem​
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160326/15bef175/attachment-0001.html>


  reply	other threads:[~2016-03-26 19:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-25 14:43 [TUHS] Is the Teletype the unsung hero of Unix? Aharon Robbins
2016-03-25 19:47 ` Jaap Akkerhuis
2016-03-25 21:03 ` Diomidis Spinellis
2016-03-28 20:12   ` scj
2016-04-01 14:06     ` Dave Horsfall
2016-04-01 22:41       ` Greg 'groggy' Lehey
2016-03-25 21:29 ` [TUHS] Command-line options Warren Toomey
2016-03-25 23:25   ` Greg 'groggy' Lehey
2016-03-26  2:10     ` John Cowan
2016-03-26  3:09       ` Charles Anthony
2016-03-26 19:43         ` Clem Cole [this message]
2016-03-26 20:54           ` Ronald Natalie
2016-03-26 22:05             ` John Cowan
2016-03-27  1:25             ` Dave Horsfall
2016-03-27  1:50               ` Charles Anthony
2016-03-27  2:01               ` Greg 'groggy' Lehey
2016-03-27  6:18                 ` Random832
2016-03-27  6:57                   ` Greg 'groggy' Lehey
2016-03-27 19:38                   ` Dave Horsfall
2016-03-27  1:35             ` Greg 'groggy' Lehey
2016-03-26  3:54 ` [TUHS] Is the Teletype the unsung hero of Unix? Greg 'groggy' Lehey
2016-03-26  4:30   ` Steve Nickolas
2016-03-26  5:44     ` Greg 'groggy' Lehey
2016-03-26  8:33       ` Steve Nickolas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAC20D2OKN=emm+cJxDKez19JZKwFoa7C7TbfyNtbGf7_7eu=2w@mail.gmail.com' \
    --to=clemc@ccc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).