The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: pnr@planet.nl (Paul Ruizendaal)
Subject: [TUHS] Dash options
Date: Tue, 28 Nov 2017 22:30:16 +0100	[thread overview]
Message-ID: <23F0FC84-19B5-47F0-8422-D13F44F432A8@planet.nl> (raw)
In-Reply-To: <mailman.376.1511899437.9955.tuhs@minnie.tuhs.org>

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


> On Tue, Nov 28, 2017 at 2:36 PM, Paul Winalski <paul.winalski at gmail.com>
> wrote:
> 
>> MS/DOS patterned its command line
>> ​ ​
>> syntax after RT-11 and inherited the slash as a command option
>> introduction from there.
> 
> ​Minor correction...   To do a CDC style patient zero history ;-) RT11 took
> it from DOS/8, CP/M took it from RT11, then finally DOS-86 which became
> PC-DOS ney MS/DOS took it from CP/M.

I think Gary Kildall was very much into the PDP-8 when teaching at the
Naval Post Graduate School in the early 70's (doing the FORTRAN/8 compiler
for instance). Can't find the link now, but I read somewhere that his
work with the 8008 and 8080 was guided by the idea of having a PDP-8 like
machine in his home office. For CP/M's command syntax RT11 probably did
not come into it. I just had a quick glance through the CP/M 1.4 - 2.2
manuals, and I did not see slash options (or any other option character).

Microsoft bought QDOS as a base for PC-DOS/MS-DOS. The QDOS system calls
were done such that converting existing 8080 CP/M code with Intel's source
level 8080-to-8086 asm converter would generate the correct code. The FAT
file system was modeled after the one used by MS Disk BASIC for the 8086.
Not sure where the QDOS command line came from, other than CP/M. MS did a
lot of its early development on a PDP-10: perhaps that was an inspiration
too.

Sorry for getting off-Unix-topic...



       reply	other threads:[~2017-11-28 21:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.376.1511899437.9955.tuhs@minnie.tuhs.org>
2017-11-28 21:30 ` Paul Ruizendaal [this message]
2017-11-29 14:03 Noel Chiappa
2017-11-29 20:29 ` Charles Anthony
  -- strict thread matches above, loose matches on Subject: below --
2017-11-29  1:23 Doug McIlroy
2017-11-29  1:37 ` George Michaelson
2017-11-29  2:22 ` Charles Anthony
2017-11-28 13:19 Noel Chiappa
2017-11-28 18:20 ` Clem Cole
2017-11-28 21:56   ` Dave Horsfall
2017-11-28  5:51 Jon Steinhart
2017-11-28  6:05 ` Dave Horsfall
2017-11-28  6:49   ` Andrew Warkentin
2017-11-28 11:18     ` Ralph Corderoy
2017-11-28 11:49       ` Michael Kjörling
2017-11-28 12:46         ` Ralph Corderoy
2017-11-28 18:01       ` Lawrence Stewart
2017-11-28 19:36     ` Paul Winalski
2017-11-28 20:03       ` Clem Cole
2017-11-28  6:28 ` Greg 'groggy' Lehey
2017-11-29 19:16   ` Steffen Nurpmeso
     [not found]     ` <20171204054651.GA17671@eureka.lemis.com>
     [not found]       ` <20171204215701.l9Pvr%steffen@sdaoden.eu>
2017-12-05 13:22         ` Steffen Nurpmeso
2017-12-07  5:15           ` Greg 'groggy' Lehey

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=23F0FC84-19B5-47F0-8422-D13F44F432A8@planet.nl \
    --to=pnr@planet.nl \
    /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).