From: Lionel Bouton <Lionel.Bouton@inet6.fr>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: root@chaos.analogic.com, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: What exactly does "supports Linux" mean?
Date: Tue, 13 May 2003 17:07:27 +0200 [thread overview]
Message-ID: <3EC10A2F.70109@inet6.fr> (raw)
In-Reply-To: <Pine.LNX.4.53.0305131016180.238@chaos>
Richard B. Johnson wrote:
>If you really want it to work, try `insmod -f modulename.o`.[...]
>
Of course, don't do this unless you can live with the following :
1/ nobody will support you in this configuration.
2/ you have zero guarantee that your hardware will be supported in the
future (what will happen when you upgrade to a new kernel with different
interfaces and the vendor marketing folks decide that Linux support
isn't a good thing anymore ?).
next prev parent reply other threads:[~2003-05-13 14:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 13:16 What exactly does "supports Linux" mean? Stephan von Krawczynski
2003-05-13 12:53 ` Alan Cox
2003-05-13 14:24 ` Richard B. Johnson
2003-05-13 15:07 ` Lionel Bouton [this message]
2003-05-13 16:45 ` Jonathan Matthews
2003-05-13 13:46 ` Duncan Sands
2003-05-13 15:12 Chuck Ebbert
2003-05-13 20:36 ` Måns Rullgård
2003-05-14 2:12 ` jw schultz
2003-05-14 7:57 ` Riley Williams
2003-05-14 17:58 ` Måns Rullgård
2003-05-17 16:05 ` Pavel Machek
2003-05-18 1:39 ` jw schultz
2003-05-18 3:53 ` Werner Almesberger
2003-05-18 21:49 ` Pavel Machek
2003-05-18 22:20 ` Neale Banks
2003-05-19 10:20 ` Helge Hafting
2003-05-14 14:11 ` Henning P. Schmiedehausen
2003-05-14 15:29 ` Mike Dresser
2003-05-15 0:11 ` jw schultz
2003-05-14 14:09 ` Henning P. Schmiedehausen
2003-05-14 14:44 ` Dave Jones
2003-05-14 15:58 ` Henning Schmiedehausen
2003-05-14 16:14 ` Dave Jones
2003-05-14 19:40 ` David Schwartz
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=3EC10A2F.70109@inet6.fr \
--to=lionel.bouton@inet6.fr \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=skraw@ithnet.com \
--cc=torvalds@transmeta.com \
/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;
as well as URLs for NNTP newsgroup(s).