From: Mike Fedyk <mfedyk@matchmail.com>
To: James Clark <jimwclark@ntlworld.com>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: Re: Driver Model 2 Proposal - Linux Kernel Performance v Usability
Date: Fri, 5 Sep 2003 13:08:44 -0700 [thread overview]
Message-ID: <20030905200844.GB19041@matchmail.com> (raw)
In-Reply-To: <200309051931.09491.jimwclark@ntlworld.com>
On Fri, Sep 05, 2003 at 07:31:09PM +0100, James Clark wrote:
> This is not about Windows v Linux so please stop compraring what I have
> proposed to Windows. This debate should be about Performance v Usability.
> Source interfaces have ultimate performance, nobody has suggested, yet, that
> they are easier for Joe User than a binary interface.
Here is one thing we don't have standardized across the entire Linux
distribution landscape.
What you need is a project that will take the top 10 distributions, and do
this however each distribution does their thing:
o identify the current kernel running (you're going to use the kernel
you're running, right?)
o download the kernel source for the running kernel
o install the source in some temporary location
o compile against the downloaded kernel source
o install the module under /lib/modules
o load the module (with the corect optional parameters)
Now what we need is someone to create the project, and get the community to
point to that project for source available external driver modules.
And look! No kernel modifications!
next prev parent reply other threads:[~2003-09-05 20:08 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1062637356.846.3471.camel@cube>
2003-09-04 20:14 ` Driver Model 2 Proposal - Linux Kernel Performance v Usability James Clark
2003-09-04 20:27 ` Mike Fedyk
2003-09-04 21:16 ` James Clark
2003-09-04 21:50 ` Mike Fedyk
2003-09-04 22:10 ` insecure
2003-09-04 22:01 ` jdow
2003-09-04 20:29 ` Rik van Riel
2003-09-04 21:12 ` James Clark
2003-09-04 21:40 ` Alan Cox
2003-09-04 21:41 ` Bartlomiej Zolnierkiewicz
2003-09-04 22:19 ` Jamie Lokier
2003-09-04 21:29 ` Richard B. Johnson
2003-09-04 21:51 ` James Clark
2003-09-04 22:06 ` Alan Cox
2003-09-04 22:10 ` Martin Mares
2003-09-04 22:23 ` Gustav Petersson
2003-09-05 17:52 ` Valdis.Kletnieks
2003-09-05 18:31 ` James Clark
2003-09-05 18:59 ` Martin Schlemmer
2003-09-05 19:12 ` Dale P. Smith
2003-09-05 19:45 ` Stan Bubrouski
2003-09-05 19:59 ` Richard B. Johnson
2003-09-05 20:01 ` James Clark
2003-09-05 20:08 ` Mike Fedyk [this message]
2003-09-05 21:15 ` Valdis.Kletnieks
2003-09-05 23:19 ` Bernd Eckenfels
2003-09-10 20:50 ` Timothy Miller
2003-09-10 20:48 ` Richard B. Johnson
2003-09-10 23:22 ` James Clark
2003-09-10 23:58 ` Greg KH
2003-09-12 20:51 ` Timothy Miller
2003-09-12 20:55 ` Tim Hockin
2003-09-15 11:39 ` Richard B. Johnson
2003-09-05 20:53 Chad Kitching
2003-09-05 23:30 ` Mike Fedyk
-- strict thread matches above, loose matches on Subject: below --
2003-09-04 22:41 Chad Kitching
2003-09-03 17:53 James Clark
2003-09-03 17:49 ` Andre Hedrick
2003-09-03 18:23 ` Guillaume Morin
2003-09-04 4:10 ` Andre Hedrick
2003-09-03 18:35 ` Guillaume Morin
2003-09-03 19:30 ` Andre Hedrick
2003-09-03 18:18 ` Greg KH
2003-09-03 18:23 ` Richard B. Johnson
2003-09-03 18:49 ` Patrick Mochel
2003-09-03 18:58 ` Gábor Lénárt
2003-09-03 20:18 ` Christoph Hellwig
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=20030905200844.GB19041@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=jimwclark@ntlworld.com \
--cc=linux-kernel@vger.kernel.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