> Can you explain what standard you think should be applied to patent
> workaround patches for them to be acceptable? I'd like to know if
> there is the possibility of us finding some agreement in the future or
> not.
>
> For example, some possibilities might be:
>
> 1) no patent workarounds allowed in upstream kernel at all
I have no problem with working around alleged patents
> 2) the workaround must be shown to have 100% compatibility with all
> current and possible future devices
If we have a workaround that is truely compatible with stuff and has no
real impact then I am all for applying it.
> 3) the workaround must be shown to have a high degree of
> compatibility with all the devices we have available to test with
IFF the workaround can be turned off for non problem parts of the world
IFF we can define what the failure models are
That bit is critical
> 4) the workaround must have the highest degree of compatibility that
> we can achieve with the most used devices, but some degree of
> interoperability problems are OK for less used devices.
At this point we get into last resorts. I don't believe unpredictable
interoperability problems are acceptable, especially for file systems.
To give an example of the reverse case, a video decoder for some web
sites that only played most but not all content of that format wouldn't
worry me. Why - because the failure case is defined ("Sorry can't play
that because of patents" dialogue box) and there isn't a real risk of
loss.
> There are lots of possible levels in between these of course. I don't
> think you are advocating (1) or (2), as you seem happier with the "no
> long name creation" patch from May.
I am. For the simple reason that
cp importantstuff.doc /media/wibble
umount; eject
go to random other system and access the document has to be a reliable
process and it is far better to get the error copying (and use a
shortname) than to arrive at the other end of an eight hour flight to
find your document is invisible on the recipient system. Hence the focus
on definable the failure case. We wouldn't apply an fs patch that
randomly vanished files from some systems, and you wouldn't apply a SAMBA
patch that made documents vanish from some systems without apparent logic.
> I apologise if you don't think this is a reasonable way to phrase the
> question. As you are the most vocal opponent of the patch, I'd like to
> better understand what it would take for you to find a patch
> acceptable.
I want to find an elegant solution to this, that is reliable, safe for
users and doesn't mislead. If asking multi-choice questions like that
helps keeps going the right way carry on.
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
