From: Theodore Tso <tytso@mit.edu>
To: Christoph Hellwig <hch@infradead.org>
Cc: Steve French <smfrench@gmail.com>,
Dave Kleikamp <shaggy@linux.vnet.ibm.com>,
Ogawa Hirofumi <hirofumi@mail.parknet.co.jp>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Michael Tokarev <mjt@tls.msk.ru>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Andrew Tridgell <tridge@samba.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add CONFIG_VFAT_NO_CREATE_WITH_LONGNAMES option
Date: Fri, 1 May 2009 22:12:58 -0400 [thread overview]
Message-ID: <20090502021258.GJ7681@mit.edu> (raw)
In-Reply-To: <20090501210109.GA3079@infradead.org>
On Fri, May 01, 2009 at 05:01:09PM -0400, Christoph Hellwig wrote:
> Steve, can you please stop the bullshitting?
>
> From the complete lack of technical arguments it's pretty obvious that
> this seems to be some FUD fallout from the MS vs TomTom patent lawsuite.
>
> I'm not a lawyer so I don't know how much of a threat it is. But either
> the case gets shot down by showing prior art and everything is fine, or
> we indeed are in deep trouble and should remove it completely. Given
> the Cc list on here IBM seems to have some legal opinion on it, so can
> we please see it and discuss what we want to with all cards on the
> table?
It's really not that simple. For some of the complexities involved,
please see:
http://arstechnica.com/open-source/news/2009/04/open-invention-network-seeks-prior-art-to-burn-fat-patents.ars
http://arstechnica.com/open-source/news/2009/04/linux-foundation-says-its-time-to-ditch-microsofts-fat.ars
I personally believe that the patents are bullshit, but at the same
time, I also believe that the USPTO is underfunded, has incompetent
patent examiners (if they were competent engineers they could be
making 2 or 3 times as much money and have much better working
conditions), and they are very loath to admit that they make mistakes,
whch is just human nature, I suppose --- and also, that in our
society, you get the best justice money can buy.
Even if the patents are bullshit, some companies, especially those
that might not have the money to engage in long, extended, drawn-out
patent battles that could easily cost $10 million minimum, might
decide that it's better to evade the issue than to fight the good
fight. If you're a small company, and you can't afford the legal
battle, or worse yet, be able to survive drop in sales caused by the
FUD generated during the lawsuit about whether or not you'll be around
to support your customers in the long-term, you make make difference
choices compared to some other larger, more secure company.
I have no trouble walking in Chinatown near the "Combat Zone" in
Boston at night; someone who is half my size and female and who has
had no martial arts training, however, might decide differently. In
neither case is the mugger justified in doing what they are doing, but
we live in an imperfect world, where pirates can hijack ships near
Somalia even though that's also Wrong.
So I don't believe removing the code is the right thing to do. I do
believe that giving people who build and use the Linux kernel choice
is a good thing; consider that digital cameras manufactures have
adhered to a 8.3 filenames, which is encoded in the DCIM standard, for
15+ years --- and I don't believe that's an accident. What might lead
one company to settle and another one to fight and another to decide
to evade the issue, may depend on many things, and may have very
little have to do with Truth or Ethics or Morality. Welcome to the
law and business as practiced in our civilized society.
(But hey, at least we don't torture people! :-)
- Ted
P.S. Everything in this e-mail is my own opinion, and does not
necessarily represent the positions, strategies, or opinions of IBM or
the Linux Foundation.
next prev parent reply other threads:[~2009-05-02 2:13 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 20:18 [PATCH] Add CONFIG_VFAT_NO_CREATE_WITH_LONGNAMES option Steve French
2009-05-01 21:01 ` Christoph Hellwig
2009-05-02 1:37 ` Paul E. McKenney
2009-05-02 1:59 ` Matthew Wilcox
2009-05-02 3:02 ` Steve French
2009-05-02 4:51 ` Paul E. McKenney
2009-05-02 9:15 ` tridge
2009-05-02 9:22 ` Christoph Hellwig
2009-05-02 9:30 ` tridge
2009-05-02 12:44 ` Christoph Hellwig
2009-05-03 21:57 ` Pavel Machek
2009-05-03 22:25 ` tridge
2009-05-03 22:56 ` Al Viro
2009-05-03 23:15 ` tridge
2009-05-04 5:42 ` Eric W. Biederman
2009-05-04 6:34 ` Paul E. McKenney
2009-05-04 6:49 ` Eric W. Biederman
2009-05-04 12:41 ` Paul E. McKenney
2009-05-04 12:44 ` Matthew Wilcox
2009-05-04 13:06 ` Paul E. McKenney
2009-05-04 13:21 ` Matthew Wilcox
2009-05-04 14:39 ` Paul E. McKenney
2009-05-04 15:08 ` Matthew Wilcox
2009-05-04 15:36 ` Dave Kleikamp
2009-05-04 15:59 ` Eric W. Biederman
2009-05-04 16:07 ` Dave Kleikamp
2009-05-04 16:30 ` Eric W. Biederman
2009-05-04 16:42 ` Paul E. McKenney
2009-05-04 17:18 ` Eric W. Biederman
2009-05-04 17:49 ` Paul E. McKenney
2009-05-04 17:54 ` Matthew Wilcox
2009-05-04 18:14 ` Paul E. McKenney
2009-05-04 18:17 ` Al Viro
2009-05-04 20:18 ` Paul E. McKenney
2009-05-04 17:06 ` Olivier Galibert
2009-05-04 17:27 ` Christoph Hellwig
2009-05-04 20:53 ` Chris Friesen
2009-05-04 23:03 ` Theodore Tso
2009-05-05 11:09 ` David Newall
2009-05-05 20:56 ` Valdis.Kletnieks
2009-05-05 21:04 ` Christoph Hellwig
2009-05-05 22:29 ` Steve French
2009-05-05 8:31 ` Zero-day exploit details (Was: Add CONFIG_VFAT_NO_CREATE_WITH_LONGNAMES option) David Newall
2009-05-04 16:11 ` [PATCH] Add CONFIG_VFAT_NO_CREATE_WITH_LONGNAMES option Paul E. McKenney
2009-05-04 15:38 ` Paul E. McKenney
2009-05-04 15:55 ` Matthew Wilcox
2009-05-04 16:10 ` Paul E. McKenney
2009-05-04 16:22 ` Matthew Wilcox
2009-05-04 22:12 ` Greg KH
2009-05-05 2:01 ` Matthew Wilcox
2009-05-05 2:11 ` Paul E. McKenney
2009-05-05 2:18 ` Matthew Wilcox
2009-05-05 3:34 ` Paul E. McKenney
2009-05-05 8:05 ` Valdis.Kletnieks
2009-05-05 15:35 ` Paul E. McKenney
2009-05-05 21:00 ` Valdis.Kletnieks
2009-05-05 21:56 ` Paul E. McKenney
2009-05-05 3:08 ` Valdis.Kletnieks
2009-05-04 15:55 ` Christoph Hellwig
2009-05-04 16:11 ` Paul E. McKenney
2009-05-04 15:40 ` Valdis.Kletnieks
2009-05-02 6:33 ` Christoph Hellwig
2009-05-02 2:12 ` Theodore Tso [this message]
2009-05-02 6:38 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2009-05-01 17:41 Dave Kleikamp
2009-05-01 17:47 ` Christoph Hellwig
2009-05-01 18:12 ` Dave Kleikamp
2009-05-01 18:19 ` Michael Tokarev
2009-05-01 19:09 ` Dave Kleikamp
2009-05-01 18:30 ` Christoph Hellwig
2009-05-02 10:09 ` OGAWA Hirofumi
2009-05-02 10:14 ` OGAWA Hirofumi
2009-05-02 10:26 ` OGAWA Hirofumi
2009-05-02 10:41 ` tridge
2009-05-02 11:03 ` OGAWA Hirofumi
2009-05-02 11:13 ` tridge
2009-05-02 11:29 ` OGAWA Hirofumi
2009-05-02 11:41 ` tridge
2009-05-02 11:59 ` OGAWA Hirofumi
2009-05-02 12:15 ` tridge
2009-05-02 12:48 ` OGAWA Hirofumi
2009-05-02 13:06 ` tridge
2009-05-02 14:01 ` OGAWA Hirofumi
2009-05-27 12:05 ` vimal singh
2009-05-27 23:57 ` tridge
2009-06-04 10:26 ` vimal singh
2009-06-04 21:33 ` tridge
2009-05-02 10:20 ` tridge
2009-05-02 10:32 ` OGAWA Hirofumi
2009-05-03 21:56 ` Pavel Machek
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=20090502021258.GJ7681@mit.edu \
--to=tytso@mit.edu \
--cc=hch@infradead.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=paulmck@linux.vnet.ibm.com \
--cc=shaggy@linux.vnet.ibm.com \
--cc=smfrench@gmail.com \
--cc=tridge@samba.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;
as well as URLs for NNTP newsgroup(s).