9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, Eirik Johnson <falmarian@yahoo.com>
Subject: Re: [9fans] GNU binutils: you can't make this shit up
Date: Thu, 19 Jan 2006 04:46:40 -0600	[thread overview]
Message-ID: <20060119104640.790801140E1@dexter-peak.quanstro.net> (raw)
In-Reply-To: <20060119082946.19064.qmail@web32707.mail.mud.yahoo.com>


Eirik Johnson <falmarian@yahoo.com> writes

| 
| There is something to be said for microkernels
| they allow for a lot less headaches with kernel
| development, and it could drastically improve plan 9's
| portability, a key feature.

"microkernels" cover a broad range. mach is
bigger than the plan 9 kernel. bigger than the linux kernel, even.
and linux is 90% device drivers.

i hold out some hope for l4. 

| Also, the multi-server approach taken by the GNU/Hurd
| is innovative and well suited to SMP and distributed
| environments. 

what's innovative about the hurd? unless i'm missing something
plan9 fileservers are isomorphic with hurd daemons, conceptually.
the major difference being, in the hurd a server exports a random
interface, in plan9 a server exports a filesystem.
hurd isn't even an os. it needs a microkernel.

 However, the FSF has a role and the GNU
| project is (and should be) a side project for them. 
| The real problem with it, though, is that C (like plan
| 9) was designed with portability as a major feature,
| and the GNU extensions in GCC aren't helping
| portability.  It's kinda like microsoft's C#, they may
| be wonderful features, but you missed the whole point.


  parent reply	other threads:[~2006-01-19 10:46 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-16  1:50 Ronald G Minnich
2006-01-16  2:00 ` Andy Newman
2006-01-16  3:10   ` Ronald G Minnich
2006-01-16  3:19     ` erik quanstrom
2006-01-16  3:47       ` David Leimbach
2006-01-18 12:55         ` Eirik Johnson
2006-01-18 13:45           ` Bruce Ellis
2006-01-18 14:00             ` alexandr babic
2006-01-18 15:45               ` Ronald G Minnich
2006-01-18 16:45                 ` Bruce Ellis
2006-01-18 17:00                   ` alexandr babic
2006-01-18 17:04                     ` Bruce Ellis
2006-01-18 17:00                 ` David Leimbach
2006-01-18 17:14                   ` Ronald G Minnich
2006-01-19  8:29               ` Eirik Johnson
2006-01-19 10:34                 ` Charles Forsyth
2006-01-19 10:43                   ` Bruce Ellis
2006-01-19 10:46                 ` erik quanstrom [this message]
2006-01-19 10:52                   ` Bruce Ellis
2006-01-19 15:41                 ` Ronald G Minnich
2006-01-19 16:05                 ` David Leimbach
2006-01-19 16:15                   ` [9fans] GNU binutils: you can't make this stuff up Brantley Coile
2006-01-19 17:16                     ` Bruce Ellis
2006-01-19 22:24                     ` erik quanstrom
2006-01-16 17:43       ` [9fans] GNU binutils: you can't make this shit up Ronald G Minnich
2006-01-16  3:46     ` David Leimbach
2006-01-16 17:44       ` Ronald G Minnich
2006-01-16 19:09         ` Bruce Ellis
2006-01-16  7:48     ` Andy Newman
2006-01-16  9:08       ` Bruce Ellis
2006-01-16 12:06       ` erik quanstrom
2006-01-16 13:23         ` Bruce Ellis
2006-01-16 19:17 jmk
2006-01-16 19:26 ` Bruce Ellis

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=20060119104640.790801140E1@dexter-peak.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@cse.psu.edu \
    --cc=falmarian@yahoo.com \
    /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).