All of lore.kernel.org
 help / color / mirror / Atom feed
From: kilobug@freesurf.fr (Gaël Le Mignot)
To: Larry McVoy <lm@work.bitmover.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Larry McVoy <lm@bitmover.com>,
	Christian Reichert <c.reichert@resolution.de>,
	John Bradford <john@grabjohn.com>,
	lkml@lrsehosting.com, linux-kernel@vger.kernel.org, rms@gnu.org,
	Valdis.Kletnieks@vt.edu
Subject: Re: [OT] HURD vs Linux/HURD
Date: Sat, 19 Jul 2003 22:07:16 +0200	[thread overview]
Message-ID: <plopm34r1i8emj.fsf@drizzt.kilobug.org> (raw)
In-Reply-To: <20030719184519.GB24197@work.bitmover.com> (Larry McVoy's message of "Sat, 19 Jul 2003 11:45:19 -0700")

 > Mach is kinda on the bloated side, I always questioned the wisdom of
 > the GNU HURD being based on Mach, seemed like a bad call.  But then,
 > unless you have an extremely well controlled dev team, any micro kernel
 > is a bad call, it's going to bloat out.

If you  were documenting  yourself a bit  instead of  trolling, you'll
notice that's the GNU Hurd is not based on Mach. The GNU Hurd tries to
be micro-kernel independant, and will be ported to other microkernels,
like L4 Version 4.

And  if you  look a  bit  in the  history, you'll  notice that  second
generation  micro-kernels  (like  L4)  were  not  available,  or  even
designed, at the time Mach was chosen as the first microkernel to make
the Hurd runs on.

-- 
Gael Le Mignot "Kilobug" - kilobug@nerim.net - http://kilobug.free.fr
GSM         : 06.71.47.18.22 (in France)   ICQ UIN   : 7299959
Fingerprint : 1F2C 9804 7505 79DF 95E6 7323 B66B F67B 7103 C5DA

Member of HurdFr: http://hurdfr.org - The GNU Hurd: http://hurd.gnu.org

  reply	other threads:[~2003-07-19 19:50 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-19 15:03 [OT] HURD vs Linux/HURD John Bradford
2003-07-19 15:02 ` Christian Reichert
2003-07-19 17:09   ` Gaël Le Mignot
2003-07-19 17:23     ` Larry McVoy
2003-07-19 17:46       ` Gaël Le Mignot
2003-07-19 18:12         ` Larry McVoy
2003-07-19 18:41           ` Christoph Hellwig
2003-07-19 18:45             ` Larry McVoy
2003-07-19 20:07               ` Gaël Le Mignot [this message]
2003-07-19 20:05           ` Gaël Le Mignot
2003-07-19 20:28             ` Valdis.Kletnieks
2003-07-19 22:03             ` Larry McVoy
2003-07-19 22:23               ` Alan Cox
2003-07-19 22:33               ` Roman Zippel
2003-07-20  6:35                 ` Andre Hedrick
2003-07-19 18:58         ` Zwane Mwaikambo
2003-07-19 22:42         ` Greg KH
2003-07-19 15:04 ` Christoph Hellwig
2003-07-19 15:16 ` Linux Kernel Mailing List
2003-07-20  6:32   ` Andre Hedrick
2003-07-20  0:07 ` Theodore Ts'o
2003-07-20 13:23   ` Charles E. Youse
2003-07-20 13:41     ` David Lloyd
2003-07-20 14:09     ` Christoph Hellwig
2003-07-20 15:27       ` Brian McGroarty
2003-07-22  4:52     ` Miles Bader
  -- strict thread matches above, loose matches on Subject: below --
2003-07-20 17:24 John Bradford
2003-07-20 13:49 John Bradford
2003-07-20 16:59 ` Horst von Brand
2003-07-19 10:33 Bitkeeper John Bradford
2003-07-19 14:00 ` [OT] HURD vs Linux/HURD Linux Kernel Mailing List

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=plopm34r1i8emj.fsf@drizzt.kilobug.org \
    --to=kilobug@freesurf.fr \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=c.reichert@resolution.de \
    --cc=hch@infradead.org \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@lrsehosting.com \
    --cc=lm@bitmover.com \
    --cc=lm@work.bitmover.com \
    --cc=rms@gnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.