From: Stephan von Krawczynski <skraw@ithnet.com>
To: "Dave Rattay [ITeX]" <Dave.Rattay@itexinc.com>
Cc: "Benjamin LaHaise" <bcrl@redhat.com>, <alan@lxorguk.ukuu.org.uk>,
<egberts@yahoo.com>, <lkml@secureone.com.au>,
<linux-kernel@vger.kernel.org>,
"ITeX Tech Support" <techsupport@itexinc.com>
Subject: RE: Dlink DSL PCI Card
Date: Sat, 23 Feb 2002 00:15:15 +0100 [thread overview]
Message-ID: <200202222315.AAA06074@webserver.ithnet.com> (raw)
In-Reply-To: <E788BA1D236784409F3F7138F1EABFDDE4DF@iteusa-nt.itexinc.com>
> Stephan,
> [...]
> Due to previous licensing
> agreements we cannot release our source code to anyone including our
> direct customers and there is no way around that. Sorry.
Hello Dave,
first of all: thank you for your clear statement.
Unfortunately your world and our (linux-) world do not match (in my
eyes). If you cannot provide either docs or source code chances will
be very high that your product line (chips) will be disliked by a big
percentage of linux using people. Most of them do not like w*ndows
because they cannot control what the system is doing, you are _never_
sure what it does to your (personal) data and where it will be spread.
If you - being a linux user - would be willing to use binary-only
drivers you are just about in the same situation - you lost control.
Your statement - for me - makes one thing absolutely clear: I will
never use your chips.
> Now if you
> have a request for a driver please let me know the kernel version
being
> used as well as the ADSL protocol that you have. I will see what I
can
> do to get you a usable driver.
I do not want a useable driver. I want to have full control over my
system where my personal data resides on. You deny this. I cannot
certify a customer system including your drivers either. Simply
because I cannot check out the code. This is why my customers will not
buy your chips either.
In fact I would not even take them as free gift. Their use is a severe
security issue.
I have no doubts though that you might sell a lot of pieces in the
w*ndows market.
Regards,
Stephan
next prev parent reply other threads:[~2002-02-22 23:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 22:33 Dlink DSL PCI Card Dave Rattay [ITeX]
2002-02-22 22:49 ` Benjamin LaHaise
2002-02-23 0:00 ` Michal Jaegermann
2002-02-22 23:15 ` Stephan von Krawczynski [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-23 13:10 Per Jessen
2002-02-22 23:27 Dave Rattay [ITeX]
2002-02-22 23:39 ` Erik Andersen
2002-02-23 12:42 ` Mark H. Wood
2002-02-22 23:00 Dave Rattay [ITeX]
2002-02-20 0:36 Andrew Hatfield
2002-02-20 1:57 ` Andrew Hatfield
2002-02-20 18:50 ` S W
2002-02-20 19:53 ` Alan Cox
2002-02-20 20:14 ` S W
2002-02-22 16:36 ` Benjamin LaHaise
2002-02-22 17:19 ` Stephan von Krawczynski
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=200202222315.AAA06074@webserver.ithnet.com \
--to=skraw@ithnet.com \
--cc=Dave.Rattay@itexinc.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bcrl@redhat.com \
--cc=egberts@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@secureone.com.au \
--cc=techsupport@itexinc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.