From: Larry McVoy <lm@bitmover.com>
To: Ga?l Le Mignot <kilobug@freesurf.fr>
Cc: Christian Reichert <c.reichert@resolution.de>,
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 10:23:11 -0700 [thread overview]
Message-ID: <20030719172311.GA23246@work.bitmover.com> (raw)
In-Reply-To: <plopm3lluu8mv0.fsf@drizzt.kilobug.org>
> - 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.
Mach wasn't written by GNU, it's a BSD based kernel pried apart into chunks
by people at CMU.
> - 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
>
> - pfinet (our TCP/IP server) comes from Linux 2.0 IP stack
>
> I'm not aware of other use of Linux code inside the Hurd project, or
> even inside the GNU project, but there may be.
Drivers and networking account for about 50% of the total lines of code.
The bulk of the work in any operating system is typically drivers. The
generic part of Linux (non-driver, non-file system) is tiny compared to
the rest.
If the Hurd gets its drivers from Linux then it should rightfully be called
Linux/HURD (or Linux/HURD/GNU).
work /tmp/linux-2.5$ bk -rnet cat | wc -l
326411
work /tmp/linux-2.5$ bk -rdrivers cat | wc -l
2605850
work /tmp/linux-2.5$ bk -r cat | wc -l
6618524
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-07-19 17:08 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 [this message]
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=20030719172311.GA23246@work.bitmover.com \
--to=lm@bitmover.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=c.reichert@resolution.de \
--cc=john@grabjohn.com \
--cc=kilobug@freesurf.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@lrsehosting.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 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).