The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Steve Nickolas <usotsuki@buric.co>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Porting the SysIII kernel: boot, config & device drivers
Date: Fri, 30 Dec 2022 13:56:35 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.21.2212301354550.3796@sd-119843.dedibox.fr> (raw)
In-Reply-To: <335F89A9-30C2-41A2-8E84-C2D761746634@planet.nl>

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

On Fri, 30 Dec 2022, Paul Ruizendaal wrote:

> One could argue that one of the drivers of the success of CP/M in the 
> 1970’s was due to its clear separation between the boot rom, BIOS and 
> BDOS components. As far as I am aware, Unix prior to 1985 did never 
> attempt to separate the device drivers from the other kernel code. I am 
> not very familiar with early Xenix, it could be that Microsoft had both 
> the skill and the interest to separate Xenix in a standard binary (i.e. 
> BDOS part) and a device driver binary (i.e. BIOS part). Maybe the 
> differences in MMU for the machines of the early 80’s were such that a 
> standard binary could not be done anyway and separating out the device 
> drivers would serve no purpose. Once the PC became dominant, maybe the 
> point became moot for MS.

Certainly Microsoft *did* have an operating system, as early as 1981, that 
had the concept of separated BIOS and BDOS, but they didn't write it, they 
bought it 🤪

That said, given that it existed in MS-DOS, I can't imagine it wouldn't 
have been impossible to also implement in Xenix...

-uso.

  reply	other threads:[~2022-12-30 18:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30 18:25 [TUHS] " Paul Ruizendaal
2022-12-30 18:56 ` Steve Nickolas [this message]
2022-12-31 14:59 ` [TUHS] " Dan Cross
2022-12-31 19:08   ` Clem Cole
2022-12-31 21:10     ` Dan Cross
2022-12-31 21:39       ` Clem Cole
2022-12-31 21:52         ` Dan Cross
2022-12-31 23:25         ` Dave Horsfall
2023-01-01  1:02           ` Rob Pike
2023-01-01  1:16             ` George Michaelson
2023-01-01  1:40               ` Larry McVoy
2023-01-01  2:29                 ` Warner Losh
2023-01-01  1:24             ` Larry McVoy
2022-12-31 22:38       ` Theodore Ts'o
2022-12-31 22:55         ` Marc Donner
2023-01-01  3:55         ` Dan Cross
2023-01-01 20:29         ` Paul Ruizendaal
2023-01-01 21:26           ` G. Branden Robinson
2023-01-01 21:31             ` Rob Pike
2022-12-31 21:11     ` Paul Ruizendaal
2022-12-31 20:02   ` Paul Ruizendaal
2022-12-31 21:04     ` Warner Losh
2022-12-31 21:41     ` Dan Cross
2023-01-01  3:08     ` Warner Losh
2023-01-01  4:40       ` Dan Cross
2023-01-01  8:05     ` Jonathan Gray

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=alpine.DEB.2.21.2212301354550.3796@sd-119843.dedibox.fr \
    --to=usotsuki@buric.co \
    --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
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).