public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Rohland <cr@sap.com>
To: Larry McVoy <lm@bitmover.com>
Cc: Michael Rothwell <rothwell@holly-springs.nc.us>,
	richardj_moore@uk.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Generalised Kernel Hooks Interface (GKHI)
Date: 09 Nov 2000 09:43:18 +0100	[thread overview]
Message-ID: <qwwzoj9k02h.fsf@sap.com> (raw)
In-Reply-To: <80256991.007632DE.00@d06mta06.portsmouth.uk.ibm.com> <3A09C725.6CFA0EE2@holly-springs.nc.us> <qwwn1f9lhdg.fsf@sap.com> <20001108235312.H22781@work.bitmover.com>
In-Reply-To: Larry McVoy's message of "Wed, 8 Nov 2000 23:53:12 -0800"

Hi Larry,

On Wed, 8 Nov 2000, Larry McVoy wrote:
> On Thu, Nov 09, 2000 at 08:44:11AM +0100, Christoph Rohland wrote:
>> *Are you crazy?* =:-0 
>> 
>> Proposing proprietary kernel extensions to establish an enterprise
>> kernel? No thanks!
> 
> Actually, I think this idea is a good one.  I'm a big opponent of
> all the big iron feature bloat getting into the kernel, and if SGI
> et al want to go off and do their own thing, that's fine with me.
> As long as Linus continues in his current role, I doubt much of
> anything that the big iron boys do will really make it back into the
> generic kernel.  Linus is really smart about that stuff, are least
> it seems so to me; he seems to be well aware that 99.9999% of the
> hardware in the world isn't big iron and never will be, so something
> approximating 99% of the effort should be going towards the common
> platforms, not the uncommon ones.

If we would not allow binary only modules I would not have such a big
problem with that...

I understand that the one size fits all approach has some limitations
if you want to run on PDAs up to big iron. But a framework to overload
core kernel functions with modules smells a lot of binary only, closed
source, vendor specific Linux on high end machines. 

And then I don't see the value of Linux anymore.

Greetings
		Christoph
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-11-09  8:44 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-08 20:31 [ANNOUNCE] Generalised Kernel Hooks Interface (GKHI) richardj_moore
2000-11-08 21:35 ` Michael Rothwell
2000-11-09  7:44   ` Christoph Rohland
2000-11-09  7:53     ` Larry McVoy
2000-11-09  8:08       ` Andre Hedrick
2000-11-09  8:43       ` Christoph Rohland [this message]
2000-11-09 12:20         ` Michael Rothwell
2000-11-09 12:31           ` Lars Marowsky-Bree
2000-11-09 12:40           ` Alexander Viro
2000-11-09 13:02             ` Michael Rothwell
2000-11-09 13:30               ` Alexander Viro
2000-11-09 13:39                 ` Michael Rothwell
2000-11-09 17:19                 ` Mike Coleman
2000-11-09 17:27                   ` Alexander Viro
2000-11-10 11:42                     ` Martin Dalecki
2000-11-09 13:40               ` Marco Colombo
2000-11-10  8:44           ` Christoph Rohland
2000-11-09 12:50       ` Tigran Aivazian
2000-11-09 16:03       ` Ingo Molnar
2000-11-10  8:42         ` Christoph Rohland
2000-11-09 14:28   ` Theodore Y. Ts'o
2000-11-10 15:07   ` Matti Aarnio
2000-11-10 15:24     ` Michael Rothwell
2000-11-13 21:56 ` Advanced Linux Kernel/Enterprise Linux Kernel Josue Emmanuel Amaro
2000-11-14  7:49   ` Lars Marowsky-Bree
2000-11-14 18:33   ` lamont
  -- strict thread matches above, loose matches on Subject: below --
2000-11-09  7:43 [ANNOUNCE] Generalised Kernel Hooks Interface (GKHI) richardj_moore
2000-11-09 11:24 ` Christoph Rohland
2000-11-09 12:25   ` Michael Rothwell
2000-11-09 12:30     ` Lars Marowsky-Bree
2000-11-09 12:46       ` Michael Rothwell
2000-11-09 13:35         ` Alan Cox
2000-11-09 13:43           ` Michael Rothwell
2000-11-09 14:23             ` Theodore Y. Ts'o
2000-11-09 12:50     ` Paul Jakma
2000-11-09 12:53       ` Michael Rothwell
2000-11-09 13:39         ` Paul Jakma
2000-11-09 14:06           ` Marco Colombo
2000-11-09 14:14           ` Theodore Y. Ts'o
2000-11-09 14:26             ` Alan Cox
2000-11-09 14:37               ` Jeff Garzik
2000-11-09 20:24               ` Theodore Y. Ts'o
2000-11-09 13:31     ` Alan Cox
2000-11-09 14:02 Jesse Pollard
2000-11-10 10:57 richardj_moore
2000-11-10 13:45 ` Alexander Viro
2000-11-10 13:51   ` Michael Rothwell
2000-11-10 14:00     ` Alexander Viro
2000-11-10 14:37   ` David Lang
2000-11-10 10:57 richardj_moore
2000-11-10 10:57 richardj_moore
2000-11-10 11:17 richardj_moore
2000-11-10 11:41 richardj_moore
2000-11-10 16:24 ` Theodore Y. Ts'o
2000-11-10 16:37   ` Christoph Rohland
2000-11-10 18:36     ` Matt D. Robinson
2000-11-11  0:12       ` Theodore Y. Ts'o
2000-11-11  3:29         ` Matt D. Robinson
2000-11-11  4:57           ` Keith Owens
2000-11-11 17:58           ` tytso
2000-11-13 10:30             ` Daniel Phillips
2000-11-11 21:48         ` Lars Marowsky-Bree
2000-11-11 22:12           ` Michael Rothwell
2000-11-10 16:54   ` Andi Kleen
2000-11-10 16:08 richardj_moore
2000-11-10 18:42 richardj_moore
2000-11-10 19:31 richardj_moore
2000-11-12 23:27 richardj_moore
2000-11-13 10:38 ` Andi Kleen
2000-11-14  3:17   ` Andrea Arcangeli
2000-11-13  5:52 richardj_moore
2000-11-14  1:34 richardj_moore
2000-11-15 15:22 richardj_moore
2000-11-15 15:24 richardj_moore
2000-11-15 18:20 ` Matt D. Robinson

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=qwwzoj9k02h.fsf@sap.com \
    --to=cr@sap.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=richardj_moore@uk.ibm.com \
    --cc=rothwell@holly-springs.nc.us \
    /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