From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bge
Date: Thu, 9 Mar 2006 14:57:36 -0500 [thread overview]
Message-ID: <00300f2992d401162743ea162b6dfc34@swtch.com> (raw)
In-Reply-To: <85f1dbf5e47591c036d98e933dec64cb@cat-v.org>
> As russ explained, the replacement for 9load is a standard Plan 9
> kernel. I am still thinking about what the best way design the user
> space bits that parse the plan9.ini invoque /dev/reboot. I'm happy to
> hear suggestions.
it's great that you can just think through the design
without coding anything. i wish i could do that.
russ
next prev parent reply other threads:[~2006-03-09 19:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 2:42 [9fans] SSH v2 Lyndon Nerenberg
2006-02-11 3:03 ` jmk
2006-02-11 3:37 ` [9fans] bge Lyndon Nerenberg
2006-02-11 4:12 ` jmk
2006-02-11 4:16 ` jmk
2006-02-11 4:23 ` Lyndon Nerenberg
2006-03-09 19:37 ` jmk
2006-03-09 19:45 ` uriel
2006-03-09 19:57 ` Russ Cox [this message]
2006-03-09 20:12 ` andrey mirtchovski
2006-03-09 21:04 ` Bruce Ellis
2006-03-09 21:18 ` jmk
2006-03-09 23:32 ` Dan Cross
2006-03-10 6:44 ` Bruce Ellis
2006-03-10 13:41 ` Dan Cross
2006-02-11 3:10 ` [9fans] SSH v2 Russ Cox
2006-02-14 6:56 ` William Josephson
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=00300f2992d401162743ea162b6dfc34@swtch.com \
--to=rsc@swtch.com \
--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).