mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brad Kemp <kemp@indusriver.com>
To: root@chaos.analogic.com, grep@oriole.sbay.org
Cc: "Manuel J. Galan" <manolow@step.es>,
	Linux kernel <linux-kernel@vger.rutgers.edu>
Subject: Re: Linux-asm (was A patch for linux 2.1.127)
Date: Thu, 19 Nov 1998 18:14:22 -0500	[thread overview]
Message-ID: <3.0.3.32.19981119181422.00cc93a0@pop3.indusriver.com> (raw)
In-Reply-To: <Pine.LNX.3.95.981119083036.1012A-100000@chaos.analogic.com >


The first unix was on a
PDP-7 cross assembled and originally developed to 
support game of `Space Travel`

>From Dennis Ritchie's home page
http://cm.bell-labs.com/~dmr/

The evolution of a Unix timeshare system
http://cm.bell-labs.com/cm/cs/who/dmr/hist.html


At 08:38 AM 11/19/98 -0500, Richard B. Johnson wrote:
>On Wed, 18 Nov 1998, George Bonser wrote:
>
>> On Wed, 18 Nov 1998, Richard B. Johnson wrote:
>> 
>> > Unix was built on a Digital PDP-11/34, using tools available
>> > in the RSX-11 Digital Operation system. Most of the 'hardware stuff'
>> > was done in DEC MACRO Assembly under RSX-11.
>> 
>> scuse me but the first Unix I saw was running on a PDP-8. It might have
>> originated on a PDP-6.  Unix was written in C from the start according to
>> all the documentation I have read. Also, I saw Unix running on PDP systems
>
>> before the /34 was ever produced. This includes the 11/24 and 11/70.
>> Probably the best Unix installation I ever saw was a dual /44 system in
>> 1984. It was the first HA system I ever worked with. It had the beginnings
>> of what we now call RAID. 
>> 
>
>See "The UNIX Time-Sharing System", Vol 57, No.6 Part 2, pages 1905-
>1929, by Dennis Ritchie and K Thompson. The concepts were worked out
>on earlier machines. 
>
>
>Cheers,
>Dick Johnson
>                 ***** FILE SYSTEM WAS MODIFIED *****
>Penguin : Linux version 2.1.128 on an i686 machine (400.59 BogoMips).
>Warning : It's hard to remain at the trailing edge of technology.
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.rutgers.edu
>Please read the FAQ at http://www.tux.org/lkml/
>
--- -- --
Brad Kemp
Indus River Networks, Inc.                   BradKemp@indusriver.com
31 Nagog Park						 978-266-8122
Acton, MA 01720                              fax 978-266-8111

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

       reply	other threads:[~1998-11-20  6:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.3.96.981118224238.1397F-100000@calvin.captech.com>
     [not found] ` <Pine.LNX.3.95.981119083036.1012A-100000@chaos.analogic.com >
1998-11-19 23:14   ` Brad Kemp [this message]
     [not found] <199811190719.CAA22430@saturn.cs.uml.edu>
     [not found] ` <Pine.LNX.3.95.981119125048.327A-100000@chaos.analogic.com>
     [not found]   ` <13909.6329.396399.658355@tzadkiel.efn.org>
     [not found]     ` <stevev@efn.org>
1998-11-20 17:52       ` Pekka Pietik{inen

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=3.0.3.32.19981119181422.00cc93a0@pop3.indusriver.com \
    --to=kemp@indusriver.com \
    --cc=grep@oriole.sbay.org \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=manolow@step.es \
    --cc=root@chaos.analogic.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

all inboxes | Powered by JetHome®