From: Tim Bird <tbird@lineo.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: linux-kernel@vger.kernel.org
Subject: Re: Binary only module question
Date: Mon, 24 Sep 2001 11:42:06 -0600 [thread overview]
Message-ID: <3BAF706E.E0DFA0AA@lineo.com> (raw)
In-Reply-To: <20010924124044.B17377@devserv.devel.redhat.com>
Arjan van de Ven wrote:
> I'm composing a list of all existing binary only modules,
Will the list be available somewhere?
I'm working on a tool that (among other things) indicates
what is "accepted practice" for loadable modules that
are binary. I seem to recall Linus saying, some years
ago, something about the the fact that the module must
not be fundamental to basic kernel operation. I can't remember
the exact details of the quote (if anyone has it, I'd
appreciate a reference to it), but I thought the general
spirit was that add-on's are OK, but basic functionality
(like the scheduler, memory management, driver
*systems* (not drivers themselves), etc.) were off limits for
being binary modules.
I'm assuming that if a module is currently known, and there
does not appear to be great backlash against it, that it
is accepted practice. Also, I assume that modules that
perform essentially the same functionality as these would
also be acceptable (from a community standpoint - the
legal standpoint is a different matter). Basically, I'm
infering a kind of community precendence from existing
known binary modules?
Am I way off?
(And yes, I know that given a choice, the community
vastly prefers an open source module over a binary module)
____________________________________________________________
Tim Bird Lineo, Inc.
Senior VP, Research 390 South 400 West
tbird@lineo.com Lindon, UT 84042
next prev parent reply other threads:[~2001-09-24 17:41 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-24 16:40 Binary only module overview Arjan van de Ven
2001-09-24 16:53 ` Rasmus Bøg Hansen
2001-09-24 16:58 ` Ignacio Vazquez-Abrams
2001-09-24 17:02 ` Andreas Steinmetz
2001-09-24 17:08 ` Anders Peter Fugmann
2001-09-24 17:24 ` Dave McCracken
2001-09-24 23:32 ` Alan Cox
2001-09-24 16:54 ` Alan Cox
2001-09-24 17:15 ` Kai Germaschewski
2001-09-24 17:16 ` Rick Haines
2001-09-24 17:17 ` Greg KH
2001-09-24 20:40 ` Casey Schaufler
2001-09-24 23:25 ` Alan Cox
2001-09-25 16:22 ` Casey Schaufler
2001-09-24 17:35 ` Steve Lord
2001-09-24 17:42 ` Tim Bird [this message]
2001-09-24 20:06 ` Michael Leun
2001-09-24 21:18 ` Nerijus Baliunas
2001-09-24 22:57 ` Brian Strand
2001-09-25 15:44 ` Greg KH
2001-09-25 19:09 ` Mark Zealey
2001-09-25 19:24 ` Ignacio Vazquez-Abrams
2001-09-25 20:42 ` Greg KH
2001-09-25 21:09 ` Roberto Nibali
2001-09-25 21:16 ` Greg KH
2001-09-25 22:14 ` Roberto Nibali
2001-09-25 22:15 ` Greg KH
2001-09-25 22:39 ` Roberto Nibali
2001-09-25 22:40 ` Greg KH
2001-09-26 16:38 ` Alan Cox
2001-09-25 16:43 ` Fabbione
2001-09-28 2:38 ` Edward S. Marshall
2001-09-25 23:24 ` Jes Sorensen
2001-09-28 14:09 ` Daniel Caujolle-Bert
2001-09-28 14:14 ` Arjan van de Ven
2001-09-28 14:42 ` Alan Cox
2001-09-28 14:52 ` Nicholas Knight
2001-09-29 9:04 ` Albert D. Cahalan
2001-09-28 19:44 ` Daniel Caujolle-Bert
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=3BAF706E.E0DFA0AA@lineo.com \
--to=tbird@lineo.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