From: "Richard B. Johnson" <root@chaos.analogic.com>
To: James Clark <jimwclark@ntlworld.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>,
rml@tech9.net, mochel@osdl.org, alan@lxorguk.ukuu.org.uk
Subject: Re: Driver Model 2 Proposal - Linux Kernel Performance v Usability
Date: Wed, 3 Sep 2003 14:23:57 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0309031405340.29451@chaos> (raw)
In-Reply-To: <200309031850.14925.jimwclark@ntlworld.com>
On Wed, 3 Sep 2003, James Clark wrote:
> Following my initial post yesterday please find attached my proposal for a
> binary 'plugin' interface:
>
But we already have a well-defined modular interface. It allows
(driver) modules to not only be installed into a running kernel,
but also to be removed from a running kernel. This makes driver
development quite easy compared to others where one needs to
re-boot to make the .... "mouse movement detected, reboot to make
the changes take effect.."
The well-defined interface for the modules is "struct file_operations".
It corresponds to the Unix I/O model for devices. This interface
is not broken and is, therefore, not necessary to be changed.
There is a Microsoft NT model where software is put somewhere and
its functions are 'registered' with the kernel. This is an abortion
designed totally to hide the inner workings of the kernel. Since
our source-code is visible, we don't need layers of abstraction
to high it from developers.
So, to your proposal, no thanks. Also, there is no way that
I will __ever__ allow software provided by others to execute
within the kernel of anything I am responsible for, unless that
software's source-code is available for inspection.
The recent problems with the Microsoft worms should certainly
convince any sane person that we can't allow some hidden software
to run our industry no matter how well we recognize the name.
There are two main reasons for using Linux in embedded systems:
(1) I know what's in there.
(2) I can make hardware drivers without having to reboot the target.
Before Linux, we had to roll our own Operating Systems. And, yes,
we made ARTOS (Analogic Realtime Operating System). We created
a whole 'C' runtime library environment. It was a bitch. We don't
need to do this anymore because there is Linux. If you, or any
other well-wisher ever succeeds in converting Linux to a binary,
no-source system, then Linux will get forked and your interface
will get fu*k^M^Mmorked also.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (794.73 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2003-09-03 18:22 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2003-09-03 18:49 ` Patrick Mochel
2003-09-03 18:58 ` Gábor Lénárt
2003-09-03 20:18 ` Christoph Hellwig
[not found] <1062637356.846.3471.camel@cube>
2003-09-04 20:14 ` 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
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-04 22:41 Chad Kitching
2003-09-05 20:53 Chad Kitching
2003-09-05 23:30 ` Mike Fedyk
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=Pine.LNX.4.53.0309031405340.29451@chaos \
--to=root@chaos.analogic.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jimwclark@ntlworld.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=rml@tech9.net \
/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
all inboxes | Powered by JetHome®