From: tomas szepe <kala@pinerecords.com>
To: Brian Beattie <alchemy@us.ibm.com>
Cc: Robert Love <rml@tech9.net>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Richard Thrapp <rthrapp@sbcglobal.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: The tainted message
Date: Mon, 29 Apr 2002 19:15:17 +0200 [thread overview]
Message-ID: <20020429171516.GA25377@louise.pinerecords.com> (raw)
In-Reply-To: <E171TzX-0008PF-00@the-village.bc.nu> <1019926629.2045.698.camel@phantasy> <1020099580.5131.14.camel@w-beattie1>
> > > Warning: The module you have loaded (%s) does not seem to have an open
> > > source license. Please send any kernel problem reports to the
> > > author of this module, or duplicate them from a boot without
> > > ever loading this module before reporting them to the community
> > > or your Linux vendor
> >
> > Perfect. A little long, but otherwise nails it.
> >
> Warning: The module (%s) does not seem to have a compatible license.
> Please contact the supplier of this module regarding any
> problems, or reproduce the problem after rebooting without
> ever loading this module.
>
> shorter?
I don't think you can strip the part about open-ness of the code --
it's an essential part of the explanation. And "any problems" might
be too broad.
Moreover, it would make sense - I believe - to include a conditional
like "Should you encounter problems after ...", as the message, as
it stands in this proposal, is rather scary: It seems to tell the
user to *do* expect problems.
T.
--
"hello it's not like i read my mail so that you have where to offer to sell me
a giant turnip or anything else thankyou." -tomas szepe <kala@pinerecords.com>
next prev parent reply other threads:[~2002-04-29 17:15 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-27 4:51 Richard Thrapp
2002-04-27 7:50 ` arjan
2002-04-27 8:06 ` Enrico Demarin
2002-04-27 18:45 ` Alan Cox
2002-04-27 12:08 ` Francois Romieu
2002-04-27 15:51 ` Richard Thrapp
2002-04-27 17:02 ` was: " Francois Romieu
2002-04-28 0:33 ` Keith Owens
2002-04-27 15:20 ` Alan Cox
2002-04-27 14:27 ` Martin Dalecki
2002-04-27 18:41 ` Alan Cox
2002-04-27 16:03 ` Richard Thrapp
2002-04-27 16:28 ` Bob_Tracy
2002-04-27 16:57 ` Robert Love
2002-04-29 16:59 ` Brian Beattie
2002-04-29 17:15 ` tomas szepe [this message]
2002-04-29 17:43 ` Ian Molton
2002-04-29 17:41 ` Thomas 'Dent' Mirlacher
2002-04-29 18:16 ` Ian Molton
2002-04-29 18:14 ` tomas szepe
2002-04-29 17:42 ` tomas szepe
2002-04-29 19:11 ` John Alvord
2002-04-29 19:21 ` tomas szepe
2002-04-29 18:41 ` Sandy Harris
2002-04-29 20:00 ` tomas szepe
2002-04-29 23:06 ` Keith Owens
2002-04-29 23:53 ` tomas szepe
2002-04-30 13:37 ` john slee
2002-04-30 13:44 ` Keith Owens
2002-04-29 18:14 ` Christian Bornträger
2002-04-29 17:34 ` Sandy Harris
2002-04-27 19:22 ` Chris Abbey
2002-04-27 19:50 ` Alan Cox
2002-04-28 0:27 ` Keith Owens
2002-04-28 1:27 ` Richard Thrapp
2002-04-28 1:41 ` Keith Owens
2002-04-28 2:14 ` Richard Thrapp
2002-04-28 2:00 ` Alan Cox
2002-04-30 8:36 Martin Knoblauch
2002-05-02 7:35 Martin Knoblauch
2002-05-02 11:55 ` Keith Owens
2002-05-02 13:08 ` Martin Knoblauch
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=20020429171516.GA25377@louise.pinerecords.com \
--to=kala@pinerecords.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alchemy@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--cc=rthrapp@sbcglobal.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®