From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] What the reason of much change of rc(1)
Date: Thu, 17 Jul 2003 18:54:48 +0200 [thread overview]
Message-ID: <00a201c34c84$21ea40a0$b9844051@insultant.net> (raw)
In-Reply-To: <5.2.0.9.0.20030717165551.00ab4950@pop.noos.fr>
> All system objects are files, processes, threads, events or ports.
> Even sockets are handled as files (TDI).
that may well be the case, but i have a 'bad feeling' about trying trick
or mess with the Win32 API, by going behind its back.
as i've mentioned before the 'kernel' knows about who's calling
what and if it doesn't like it, well you're SOL.
next prev parent reply other threads:[~2003-07-17 16:54 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
2003-07-17 16:54 ` boyd, rounin [this message]
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='00a201c34c84$21ea40a0$b9844051@insultant.net' \
--to=boyd@insultant.net \
--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).