Re: JFS default behavior (was: UTF-8 in file systems? xfs/extfs/etc.)

From: Jamie Lokier (jamie_at_shareable.org)
Date: 02/12/04

  • Next message: Philipp Kolmann: "[2.6.3-rc2] System hangs after 'cat /proc/asound/card0/codec97#0/ac97#0-0'" 
    Date:	Thu, 12 Feb 2004 08:54:51 +0000
To: Andy Isaacson <adi@hexapodia.org>

    Andy Isaacson wrote:
    > Why on earth is JFS worried about the filename, anyways? Why has it
    > *ever* had *any* behavior other than "string of bytes, delimited with /,
    > terminated with \0" ?

    Perhaps for the same reason that these other in-tree filesystems are
    sensitive to the character encoding:

       Joliet (ISO-9660 extension), FAT/VFAT, NTFS, BeFS, SMBFS, CIFS.

    Those filesystems will also fail, or give unexpected behaviour (such
    as bytes being changed to '?'), if you pass them names which are not
    in the appropriate encoding.

    -- Jamie
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Philipp Kolmann: "[2.6.3-rc2] System hangs after 'cat /proc/asound/card0/codec97#0/ac97#0-0'"