From: "Anthony DeRobertis" <asd@suespammers.org>
To: <kaos@ocs.com.au>
Cc: <sirmorcant@morcant.org>, <tkhoadfdsaf@hotmail.com>,
<dwmw2@infradead.org>, <alan@lxorguk.ukuu.org.uk>,
<viro@math.psu.edu>, <linux-kernel@vger.kernel.org>
Subject: Re: Tainted Modules Help Notices
Date: Wed, 10 Oct 2001 18:03:25 -0400 (EDT) [thread overview]
Message-ID: <44355.192.168.65.5.1002751405.squirrel@maxwell.local> (raw)
In-Reply-To: <16172.1002749316@ocs3.intra.ocs.com.au>
In-Reply-To: <16172.1002749316@ocs3.intra.ocs.com.au>
> To triage bug reports. Any bug report against a tainted kernel is
> almost certain to be bounced with "your kernel contains code that
> we do not have the source for, send this bug report to the company
> that
> maintains the non-GPL code".
Couldn't this mess be solved with a module (optionally) containing a URL
to a source-code tarball? Modules that come with the kernel would point
to the relevant kernel sources on ftp.kernel.org.
This would alleviate all worry about things like closed-source BSD;
after all, anyone could check if there is source availible with wget.
next prev parent reply other threads:[~2001-10-10 22:04 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 8:06 Tainted Modules Help Notices Morgan Collins [Ax0n]
2001-10-10 8:20 ` David Woodhouse
2001-10-10 8:24 ` Morgan Collins [Ax0n]
2001-10-10 8:31 ` David Woodhouse
2001-10-10 13:50 ` Keith Owens
2001-10-10 13:59 ` Alexander Viro
2001-10-10 14:01 ` Keith Owens
2001-10-10 17:30 ` Alan Cox
2001-10-10 18:18 ` David Woodhouse
2001-10-10 20:06 ` Concerned Programmer
2001-10-10 20:28 ` Morgan Collins [Ax0n]
2001-10-10 21:28 ` Keith Owens
2001-10-10 22:03 ` Anthony DeRobertis [this message]
2001-10-11 7:27 ` David Woodhouse
2001-10-10 21:17 ` Alan Cox
2001-10-10 23:02 ` Juan Quintela
2001-10-10 23:28 ` Andreas Dilger
2001-10-10 22:29 ` Rob Landley
2001-10-11 2:48 ` 2.4.11 UDF Morgan Collins [Ax0n]
2001-10-11 3:26 ` Craig Whitmore
2001-10-11 8:50 ` Tainted Modules Help Notices Andreas Ferber
2001-10-11 9:25 ` Alan Cox
2001-10-11 9:35 ` Henning P. Schmiedehausen
2001-10-11 9:41 ` Pekka Pietikäinen
2001-10-11 9:48 ` Syed Mohammad Talha
2001-10-11 10:09 ` Concerned Programmer
2001-10-11 10:37 ` Alan Cox
2001-10-11 22:42 ` David Schwartz
2001-10-11 23:40 ` John Alvord
2001-10-12 1:12 ` David Schwartz
2001-10-12 1:32 ` Robert Love
2001-10-11 12:10 ` James Sutherland
2001-10-10 14:13 ` David Woodhouse
2001-10-10 14:18 ` Alexander Viro
2001-10-10 13:10 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-10-10 14:06 Bonds, Deanna
2001-10-10 14:24 ` Arjan van de Ven
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=44355.192.168.65.5.1002751405.squirrel@maxwell.local \
--to=asd@suespammers.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dwmw2@infradead.org \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=sirmorcant@morcant.org \
--cc=tkhoadfdsaf@hotmail.com \
--cc=viro@math.psu.edu \
/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