[lkml]   [2009]   [Jul]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] Added CONFIG_VFAT_FS_DUALNAMES option
    > I'd actually prefer to see the code ripped out and no config option available; 
    > it would the clearest avoidance case possible.

    What about the free world - why should we suffer because Americans have
    a broken patent system ? That just leads to a Farenheit 451 model where
    the kernel sources end up containing no code, text or image that can
    offend, harm or be found wanting in any possible legal jurisdiction.

    If we put in VFAT american fixes presumably we need to put in monitoring
    features required by dubious governments ?

    If you want to rip stuff out of your copy feel free. I am quite sure many
    US based vendors will do that (because they do so already with things
    like video codecs rather than just disabling the build option).

    Also please stop calling it VFAT. With the changes made it isn't VFAT and
    it's misleading to an end user to advertise it as vfat and users
    shouldn't accidentally be able to specify -o vfat and get non-vfat. Thats
    asking for incompatibility, data loss and unpleasant unwarned of suprises.

    Its "linfat" or something which when you've fixed the bugs Pavel has
    pointed out might be semi-compatible with other products (most *FAT using
    products don't use Microsofts implementation). Testing it versus Windows
    and saying it works is not really adequate. Thats what ACPI and BIOS
    people do that *we* moan about all the time.


     \ /
      Last update: 2009-07-01 13:29    [W:0.020 / U:32.696 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site