All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: john@grabjohn.com, vonbrand@inf.utfsm.cl
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OT] HURD vs Linux/HURD
Date: Sun, 20 Jul 2003 18:24:13 +0100	[thread overview]
Message-ID: <200307201724.h6KHODWk002989@81-2-122-30.bradfords.org.uk> (raw)

> >                                                              We are
> > discussing what parts of the Hurd and GNU Mach contain code derived
> > from Linux.  That's actually quite interesting, and on-topic.
>
> Why? Are you planing to take anything from Hurd? Or complain that they
> (legally!) are taking GPLed code and use it elsewhere? In the fist case,
> discussion about the _technical_ merit of the code to swipe is on-topic,
> all else isn't. The second case is none of your business, (unless you wrote
> the code and did not GPL it).

I'm certaily _not_ going to complain that code has been taken from
Linux - as you pointed out, that is perfectly legal.

The use of the Linux drivers in the Hurd is the closest thing[1] we've
got to a fork[2] of the Linux kernel.

So, yes, I am interested in seeing if they have done anything better
than we have, or have investigated possibilities we haven't.

John.

[1] I am _NOT_ saying that the Hurd is a fork of Linux, but that it's
about the only codebase which took Linux kernel code, and has let it
evolve separately from mainline over a number of years.  OK, the Vax
port has lived outside of mainline for a number of years too, but
that's mainly architecture specific changes.

[2] OK, ELKS is a fork of the Linux kernel, but not specifically
targeted at 386+ boxes.

John.

             reply	other threads:[~2003-07-20 16:59 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-20 17:24 John Bradford [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-20 13:49 [OT] HURD vs Linux/HURD John Bradford
2003-07-20 16:59 ` Horst von Brand
2003-07-19 15:03 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
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
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=200307201724.h6KHODWk002989@81-2-122-30.bradfords.org.uk \
    --to=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vonbrand@inf.utfsm.cl \
    /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.