From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] sendfd() on native Plan 9?
Date: Sun, 4 Jan 2009 08:26:09 +0200 [thread overview]
Message-ID: <41c083b856f1c8644dab7d813b2e53a1@proxima.alt.za> (raw)
In-Reply-To: <20090104055830.GI8355@masters10.cs.jhu.edu>
>> Would that satisfy your requirements? Oh, sure, I haven't ever used
>> #| directly and I'm a bit ignorant of consequences, but the rest seems
>> feasible.
>
> I suspect #| being an exception wouldn't hurt, though it might be viewed as
> a historical wart, being the only one... could #| be made to operate more
> like devdup and given a canonical mountpoint?
>
I'd love to see that, although I respect the Plan 9 developers enough
to believe they have given the issue plenty of thought. Still, there
have been some instance of expedience (don't ask me, I may have to
take this back :-) and perhaps there is another way if one looks
beyond the present boundaries.
>> Another aspect I noticed is that what you seem to need is a
>> finer-grained construction of #p and #s, but being able to construct
>> them one layer further down the hierarchy might suffice.
>
> "one layer further down the hierarchy" ?
>
Well, if you could bind a subset of #s by some selection criterion -
specifically process group, but who's to know what else might be
useful? - say, back onto a local /srv, you may have a sensible
mechanism for jailing processes. But I'm once again speculating
outside my knowledge and experience.
>> Just an uneducated opinion, I've had little occasion to study those
>> specific devices or the others in any detail. But I am curious of
>> where this discussion could lead.
>
> I too.
I have a feeling this is heading precisely where I would have liked to
go a year or so ago, namely putting Plan 9 at the bottom of a
paravirtualising executive. If that is the case, count me in on any
further developments.
++L
next prev parent reply other threads:[~2009-01-04 6:26 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-23 18:01 Nathaniel W Filardo
2008-12-23 22:52 ` Rodolfo kix Garcia
2008-12-23 23:53 ` Francisco J Ballesteros
2008-12-24 1:10 ` Nathaniel W Filardo
2008-12-24 1:39 ` erik quanstrom
2008-12-24 3:00 ` Nathaniel W Filardo
2008-12-24 4:14 ` erik quanstrom
2008-12-24 7:36 ` Nathaniel W Filardo
2008-12-24 13:36 ` erik quanstrom
2008-12-27 20:27 ` Roman Shaposhnik
2008-12-27 20:34 ` Eric Van Hensbergen
2008-12-27 20:21 ` Roman Shaposhnik
2008-12-30 8:22 ` Nathaniel W Filardo
2008-12-30 15:04 ` Eric Van Hensbergen
2008-12-30 15:31 ` erik quanstrom
2009-01-01 22:53 ` Roman V. Shaposhnik
2009-01-01 23:57 ` Nathaniel W Filardo
2009-01-03 21:23 ` Roman V. Shaposhnik
2009-01-03 21:41 ` erik quanstrom
2009-01-03 21:59 ` Roman V. Shaposhnik
2009-01-03 23:57 ` Nathaniel W Filardo
2009-01-04 5:19 ` lucio
2009-01-04 5:48 ` erik quanstrom
2009-01-04 6:10 ` Nathaniel W Filardo
2009-01-04 6:43 ` lucio
2009-01-05 1:12 ` Roman V. Shaposhnik
2009-01-05 1:32 ` erik quanstrom
2009-01-05 3:48 ` lucio
2009-01-04 17:32 ` erik quanstrom
2009-01-04 18:23 ` lucio
2009-01-05 1:24 ` Roman V. Shaposhnik
2009-01-04 5:58 ` Nathaniel W Filardo
2009-01-04 6:26 ` lucio [this message]
2009-01-04 15:46 ` erik quanstrom
2009-01-05 4:30 ` Roman V. Shaposhnik
2008-12-24 1:17 ` Nathaniel W Filardo
2008-12-27 17:06 ` Russ Cox
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=41c083b856f1c8644dab7d813b2e53a1@proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).