The Unix Heritage Society mailing list
 help / Atom feed
From: Peter Jeremy <peter@rulingia.com>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Set-uid shell scripts
Date: Thu, 8 Aug 2019 16:39:03 +1000
Message-ID: <20190808063903.GB84848@server.rulingia.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.1908080724190.81938@aneurin.horsfall.org>

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

On 2019-Aug-08 07:33:47 +1000, Dave Horsfall <dave@horsfall.org> wrote:
>I've always thought that Xenix was insane to start with...  Then again, my 
>first experience with it was on a 286...  Now, when porting Unify, should 
>I use large memory model here or small memory model?  Crazy.

Ah, yes.  I remember it well.  The large, small and various mixed modes
were a consequence of the braindeadedness of the 286 - reloading segment
registers (pretty much every memory reference in large mode) was abysmally
slow.  I recall hacking mg (a cut-down emacs clone) so that buffers were
in "far" memory and everything else was "near".

Some of the Xenix features I recall were:
* occasionally fork() would return -1 in both the parent and child (or
  something like that - it would both succeed and report failure)
* The contents of comments would affect the Pascal compiler's ability
  to compile the program (this was "using uninitialised variables"
  behaviour, rather than magic lint-style comments).  It made software
  development "interesting" because checking a program into SCCS might
  stop it compiling.
* fork()ing a large process could panic the system.
* The C compiler barfed on parts of starchart (from comp.sources.???)

-- 
Peter Jeremy

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 963 bytes --]

  reply index

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-04  7:36 Dave Horsfall
2019-08-04  7:43 ` Alec Muffett
2019-08-04 15:58   ` jnc
2019-08-04 16:30     ` Michael Kjörling
2019-08-04 16:48       ` Alec Muffett
2019-08-04 17:48         ` Michael Kjörling
2019-08-04 19:45           ` Alec Muffett
2019-08-04 16:50     ` Rico Pajarola
2019-08-04  7:46 ` arnold
2019-08-04 20:18 jnc
2019-08-04 20:29 ` Clem Cole
2019-08-04 20:42   ` Richard Salz
2019-08-04 23:58 ` Dave Horsfall
2019-08-04 21:18 Norman Wilson
2019-08-04 21:27 Norman Wilson
2019-08-06  8:28 ` jason-tuhs
2019-08-06  9:55   ` arnold
2019-08-06 22:48   ` Dave Horsfall
2019-08-06 22:56     ` ron minnich
2019-08-07  1:21     ` Dave Horsfall
     [not found]       ` <40c92e85142fe7e3@orthanc.ca>
2019-08-07 21:33         ` Dave Horsfall
2019-08-08  6:39           ` Peter Jeremy [this message]
2019-08-07 12:56     ` Chet Ramey
2019-08-07 21:40       ` Dave Horsfall
2019-08-08  5:16         ` Adam Thornton
2019-08-14  5:41           ` Efton Collins
2019-08-05  0:13 jnc

Reply instructions:

You may reply publically 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=20190808063903.GB84848@server.rulingia.com \
    --to=peter@rulingia.com \
    --cc=dave@horsfall.org \
    --cc=tuhs@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

The Unix Heritage Society mailing list

Archives are clonable: git clone --mirror http://inbox.vuxu.org/tuhs

Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.tuhs


AGPL code for this site: git clone https://public-inbox.org/ public-inbox