The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Jim Capp <jcapp@anteil.com>
To: Josh Good <pepe@naleco.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] PC Unix (had been How to Kill a Technical Conference
Date: Tue, 6 Apr 2021 15:26:52 -0500 (EST)	[thread overview]
Message-ID: <12445917.1513.1617740812263.JavaMail.root@zimbraanteil> (raw)
In-Reply-To: <20210406201118.GA3953@naleco.com>

[-- Attachment #1: Type: text/plain, Size: 1440 bytes --]

Josh, 


At the time (1982-83), Xenix was the only Unix available to me. By 1984, we upgraded to a full-fledged NCR 1632 system, with Unix SVR4. 


Installation was through a VGA console and after it was up and running, you could add serial terminals to your heart's content. 


We mostly wrote our own software, but had productivity packages for word processing, spreadsheets, and databases (non-SQL). 


Xenix was my first experience with *nix. I "caught the bug" and have been working with *nix ever since. 


Cheers, 


Jim 





From: "Josh Good" <pepe@naleco.com> 
To: tuhs@minnie.tuhs.org 
Sent: Tuesday, April 6, 2021 4:11:19 PM 
Subject: Re: [TUHS] PC Unix (had been How to Kill a Technical Conference 

On 2021 Apr 6, 12:32, Charles H Sauer wrote: 
> For much of my last few years at IBM, my uucp machine, ibmchs, was an AT 
> running Xenix, probably that version of Xenix. 

Hi. I'm curious about that Xenix vintage. How did you use that machine: 
headless from a serial terminal?, or at the VGA console? Was it "single 
user" or shared among several people? Did you run Xenix and only SCO 
provided software, or did you had third party software in it? Were you 
using it by choice as your favourite Unix, or merely because it was the 
only Unix you could have? Did you like living with Xenix? Did it have 
problems, o was it "setup and forget"? 

If you feel like sharing that experience, thank you very much. 

-- 
Josh Good 


[-- Attachment #2: Type: text/html, Size: 1897 bytes --]

  reply	other threads:[~2021-04-06 20:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-06 15:35 M Douglas McIlroy
2021-04-06 17:09 ` Clem Cole
2021-04-06 17:32   ` Charles H Sauer
2021-04-06 20:11     ` Josh Good
2021-04-06 20:26       ` Jim Capp [this message]
2021-04-06 20:47         ` Charles H Sauer
2021-04-07 16:42           ` Josh Good
2021-04-07 18:04             ` Charles H. Sauer
2021-04-07  2:49         ` Dave Horsfall
2021-04-07  6:04         ` arnold
2021-04-07 16:01           ` heinz
2021-04-06 21:06       ` Clem Cole
2021-04-07  0:58     ` heinz
2021-04-07  1:37       ` Warner Losh
2021-04-07  3:38         ` Dave Horsfall
2021-04-07  2:30     ` Ed Bradford
2021-04-07  2:44       ` Charles H. Sauer
2021-04-06 20:20   ` Boyd Lynn Gerber
2021-04-06 22:41 ` Dave Horsfall
2021-04-07  1:10   ` Jon Steinhart
2021-04-07  1:47     ` Greg 'groggy' Lehey
2021-04-07  1:49       ` Jon Steinhart
2021-04-07  1:58         ` Larry McVoy
2021-04-07  2:31           ` Serge Burjak
2021-04-09 21:24   ` Michael Parson
2021-04-10  3:33     ` Ed Bradford
2021-04-10 15:12       ` Clem Cole
2021-04-10 15:41         ` Larry McVoy
2021-04-07  0:59 Jason Stevens
2021-04-10 18:12 Paul Ruizendaal via TUHS

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=12445917.1513.1617740812263.JavaMail.root@zimbraanteil \
    --to=jcapp@anteil.com \
    --cc=pepe@naleco.com \
    --cc=tuhs@minnie.tuhs.org \
    /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).