9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Philippe Anel <philippe.anel@noos.fr>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] What the reason of much change of rc(1)
Date: Thu, 17 Jul 2003 17:17:00 +0200	[thread overview]
Message-ID: <5.2.0.9.0.20030717165551.00ab4950@pop.noos.fr> (raw)
In-Reply-To: <6af263ecf0dd5c8acd58afb98cf074ff@plan9.bell-labs.com>

At 10:37 17/07/03 -0400, you wrote:
>I did indeed reformat it.  I was making a version that would work
>both on windows and unix/plan9 and got angry at the formating style.
>
>The have{nt}fork.c was indeed for os's without fork.

Hi,

I suggest you to read "Windows NT/2000: Native API reference"
by Gary Nebbett (ISBN: 1-57870-199-6).

It contains the set of system services provided by the Window NT
executive (the native syscall interface).

Even though it only works with NT(2k/xp) kernels, the book contains
the source code for a Un*x-like fork.

The NT executive has a lot similarities with the M*ch kernel and the
IO subsystem is entierly object oriented. That being said, the main
problem is the Win32 API.

All system objects are files, processes, threads, events or ports.
Even sockets are handled as files (TDI).

         Philippe.




  reply	other threads:[~2003-07-17 15:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-16  7:38 okamoto
2003-07-17  1:38 ` okamoto
2003-07-17 14:37   ` David Presotto
2003-07-17 15:17     ` Philippe Anel [this message]
2003-07-17 16:54       ` boyd, rounin
2003-07-17 16:14     ` Scott Schwartz
2003-07-17 16:51       ` rog
2003-07-17 17:38         ` boyd, rounin

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=5.2.0.9.0.20030717165551.00ab4950@pop.noos.fr \
    --to=philippe.anel@noos.fr \
    --cc=9fans@cse.psu.edu \
    /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).