From: Steve Nickolas <usotsuki@buric.co>
To: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Has this been discussed on-list? How Unix changed Software.
Date: Wed, 7 Sep 2022 09:52:24 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.21.2209070951500.32531@sd-119843.dedibox.fr> (raw)
In-Reply-To: <CAEoi9W73PosrK0V_HC4jCLEp+v18DR5_jioZD+0YR4_JR8jNPw@mail.gmail.com>
On Wed, 7 Sep 2022, Dan Cross wrote:
> Second, I have it directly from folks who worked on Hyper-V that it is
> neither based on Unix/Linux, nor strongly influenced by either VMWare
> or Xen. It was an entirely in-house project at MSFT that probably
> includes more DNA strands from Windows than Unix et al. Some of the
> stories about clashes with Cutler to change the Windows startup
> sequence to accommodate Hyper-V are interesting (short version:
> Cutler, in typical fashion, didn't want to and early versions of
> Hyper-V basically booted under windows, then "took over" the running
> machine so that Windows resumed, but suddenly in a VM where it had not
> been before).
That sounds like what Compaq's CEMM (a.k.a. EMM386) did with MS-DOS.
-uso.
next prev parent reply other threads:[~2022-09-07 13:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 23:48 [TUHS] " steve jenkin
2022-09-06 16:09 ` [TUHS] " Marc Donner
2022-09-07 4:00 ` steve jenkin
2022-09-07 14:58 ` John Cowan
2022-09-07 17:13 ` Paul Winalski
2022-09-08 14:12 ` Paul Winalski
2022-09-07 5:15 ` steve jenkin
2022-09-07 13:20 ` Dan Cross
2022-09-07 13:52 ` Steve Nickolas [this message]
2022-09-07 12:53 ` [TUHS] STDIN/OUT vs APIs [was: How Unix changed Software] Brian Zick
2022-09-07 13:19 ` [TUHS] " John Cowan
2022-09-07 15:39 ` Joe
2022-09-07 15:43 ` John Cowan
2022-09-07 16:01 ` Charles H Sauer (he/him)
2022-09-06 15:07 [TUHS] Re: Has this been discussed on-list? How Unix changed Software Douglas McIlroy
2022-09-06 17:13 ` Larry McVoy
2022-09-07 1:40 ` steve jenkin
2022-09-07 2:33 ` segaloco via TUHS
2022-09-07 4:08 ` Steve Jenkin
2022-09-07 13:08 ` Steffen Nurpmeso
2022-09-07 14:56 ` Larry McVoy
2022-09-07 21:27 ` Steve Jenkin
2022-09-07 22:36 ` Larry McVoy
2022-09-08 14:42 ` Paul Winalski
2022-09-08 15:02 ` Larry McVoy
2022-09-08 15:04 ` ron minnich
2022-09-08 15:52 ` Warner Losh
2022-09-08 16:47 ` Paul Winalski
2022-09-08 16:50 ` segaloco via TUHS
2022-09-08 17:58 ` ron minnich
2022-09-06 19:04 Douglas McIlroy
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.2209070951500.32531@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).