From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] New /prog idea
Date: Mon, 5 May 2014 09:06:56 -0400 [thread overview]
Message-ID: <a54a8f98540da39eafffa5abc3546f34@brasstown.quanstro.net> (raw)
In-Reply-To: <CAOw7k5j0_meJjEsnGZeEHBUnxWe+qPagiXGs2r0R=q=oM68Wug@mail.gmail.com>
> the system calls that are not currently in the name space are those
> that do not distribute (and there have been a few things in the name
> space that don't distribute and are troublesome).
>
> segbrk doesn't distribute. rfork doesn't distribute. you can have a
> control request in a name space that operates on another process, or
> creates another process, but that's not a system call by the calling
> process: it's a request to another process for it to do something
> (possibly in the kernel domain, if there is one).
yes. to implement this idea, one may need to change the set of system
calls. or maybe like file operations, not all system calls are valid in all
contexts. i never ment to imply this was more than a half-baked idea,
for a system that's no longer plan 9. (if i could see how things worked,
i'd implement a toy system.) i think the proliferation of system calls in
nemo's kernels with specialised cores might have been a related problem.
- erik
next prev parent reply other threads:[~2014-05-05 13:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 21:59 Oleksandr Iakovliev
2014-05-05 0:53 ` erik quanstrom
2014-05-05 11:03 ` tlaronde
2014-05-05 12:09 ` erik quanstrom
2014-05-05 12:33 ` Charles Forsyth
2014-05-05 13:06 ` erik quanstrom [this message]
2014-05-05 14:38 ` Oleksandr Iakovliev
2014-05-05 14:56 ` erik quanstrom
2014-05-05 15:22 ` Gorka Guardiola
2014-05-05 16:38 ` lucio
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=a54a8f98540da39eafffa5abc3546f34@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).