lkml.org 
[lkml]   [2009]   [Jul]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: CONFIG_VFAT_FS_DUALNAMES regressions
    > The FAT patents *have* been tested, invalidated, and then revalidated.
    > Yes, they might still be invalid - I believe they are. This helps a
    > Linux user whose products have been seized at the US border exactly
    > how?

    The same way as one who shipped mp3 software.

    Of course they can simply remove the code that concerns them as companies
    *already do*. They have specialists for this, experts who know the very
    complex field of import and export regulation.

    > SCO is a very different story, though. Copyright infringement is
    > usually pretty easy to avoid - just do your own work. Patent
    > infringement happens regardless of how original your work is.

    Actually this is changing, large corporations stealing photographic
    images and the threatening to sue the original photographer is becoming
    rather common. I'm sure the same will happen in other fields too. SCO
    probably did it by accident, but folks will do it deliberately too.

    > I have a lot of sympathy for Alan's assertion that we can't muck up our
    > upstream code with hackarounds for every bit of legal obnoxiousness we
    > encounter. But outright refusal of things like patent workarounds does
    > not help us either. Linux is a pragmatic system; somehow, I believe,
    > we can find a way to minimize our patent hassles without messing up the
    > system as a whole.

    If you don't believe VFAT is permitted in your shipping locale you turn
    it off (actually you cut the code from your source tar before build).
    Utterly routine practice every day for companies shipping product into
    the USA. Happens with tons of other open source software that isn't
    permitted in the USA.

    The pragmatic approach would be to either avoid the patent without
    breaking stuff (which Tridge hasn't managed, although maybe one day he
    might), or to produce something which doesn't break stuff, is reliable,
    meets our quality goals but which is alternative and clearly presented as
    an alternative - such as Tridge's shortname creating tridgefat variant,
    which at least didn't randomly explode users data in new and novel ways.
    It still needs to be an alternative not a replacement for the real thing.

    Alan


    \
     
     \ /
      Last update: 2009-07-10 23:17    [W:4.153 / U:0.024 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site