9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Corey <corey@bitworthy.net>
To: 9fans@9fans.net
Subject: Re: [9fans] plan9 kernel on genode?
Date: Thu, 25 Feb 2010 18:27:21 -0700	[thread overview]
Message-ID: <201002251827.21678.corey@bitworthy.net> (raw)
In-Reply-To: <69354e94edc365db80dad6691585d2ee@brasstown.quanstro.net>

On Thursday 25 February 2010 17:30:16 erik quanstrom wrote:
> > kernel and there doesn't need to be one. By using Genode, applications
> > developed for one kernel can be ported to all the other supported
> > platforms with a simple recompile.
>
> this sort of thing is built for a knee-jerk reaction.  ...
> which i will happily provide.
>
> ah, the chicago crain technique of building complicated
> system.
>
> 	for(floor = nil;; floor = nf){
> 		nf = buildfloor(floor);
> 		jackupcrain(nf);
> 	}
>
> the main difference is that each floor in a building
> is typically not unique, yet serves a unique purpose
> whereas in chicago crain systems, each layer of abstraction
> is unique, yet does not serve a unique purpose.
>
> maybe i'm looking at it wrong and each abstraction
> layer is actually floor space for some poor programmer
> to make a living.
>

I won't comment on the kneejerk reaction, other than to say
platform portability is not the primary goal of genode -

http://genode.org/about
http://genode.org/documentation/general-overview

At any rate, probably _I'm_ looking at it wrong - but it occurred to me that
plan9 on genode might provide a route to exploring union directories,
namespaces, etc. in a different context than via the current native plan 9
system.




      reply	other threads:[~2010-02-26  1:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26  0:24 Corey
2010-02-26  0:30 ` erik quanstrom
2010-02-26  1:27   ` Corey [this message]

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=201002251827.21678.corey@bitworthy.net \
    --to=corey@bitworthy.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).