All of lore.kernel.org
 help / color / mirror / Atom feed
From: kilobug@freesurf.fr (Gaël Le Mignot)
To: Christian Reichert <c.reichert@resolution.de>
Cc: John Bradford <john@grabjohn.com>,
	lkml@lrsehosting.com, linux-kernel@vger.kernel.org,
	lm@bitmover.com, rms@gnu.org, Valdis.Kletnieks@vt.edu
Subject: Re: [OT] HURD vs Linux/HURD
Date: Sat, 19 Jul 2003 19:09:23 +0200	[thread overview]
Message-ID: <plopm3lluu8mv0.fsf@drizzt.kilobug.org> (raw)
In-Reply-To: <1058626962.30424.6.camel@stargate> (Christian Reichert's message of "19 Jul 2003 17:02:41 +0200")

Hello Christian!

19 Jul 2003 17:02:41 +0200, you wrote: 

 > On Sat, 2003-07-19 at 17:03, John Bradford wrote:
 >> > Given that large chunks of HURD come from Linux, please refer to it as
 >> > Linux/HURD.
 >> 
 >> What HURD code comes from Linux?  GNU/Mach uses code from Linux, but
 >> not HURD as far as I know.

 > Neither to my knowledge -

 > GNU/HURD uses GNU/MACH as the microkernel (and GNU/MACH uses Linux 2.0
 > drivers), but they are actually thinking of switching to another MACH
 > implementation once it's stable.

To be more exact:

- GNU/Hurd, the  whole systems, is  actually GNU tools  (libc, linker,
  ...)  on top  of the  GNU Hurd  (set of  servers) and  the  GNU Mach
  microkernel.

- GNU Mach 1.x uses drivers from Linux 2.0.36 (IIRC)

- GNU  Mach 2.0  (actually 1.9,  as a  beta version),  uses  the OSKit
  framework, and such drivers from Linux 2.2.12 (but nearly any driver
  for Linux  2.2 can  be easily ported)  or FreeBSD (I  don't remember
  which version, we actually use more Linux drivers).

- In the future, we'll probably use  the L4 microkernel. On top of L4,
  we'll have  to implement user space drivers.   That'ld probably take
  time, so  we may reuse Linux  drivers with glue code  as a temporary
  solution.

- pfinet (our  TCP/IP server)  comes from Linux  2.0 IP stack,  but we
  need a rewrite for that (first  because Linux 2.0 stack's is not the
  best in  the world ;) and  then because kernel-space  code runned in
  user-space with glue code isn't either fast nor flexible).

I'm not aware  of other use of Linux code inside  the Hurd project, or
even inside the GNU project, but there may be.

-- 
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 16:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-19 15:03 John Bradford
2003-07-19 15:02 ` Christian Reichert
2003-07-19 17:09   ` Gaël Le Mignot [this message]
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
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=plopm3lluu8mv0.fsf@drizzt.kilobug.org \
    --to=kilobug@freesurf.fr \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=c.reichert@resolution.de \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@lrsehosting.com \
    --cc=lm@bitmover.com \
    --cc=rms@gnu.org \
    --subject='Re: [OT] HURD vs Linux/HURD' \
    /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

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.