>> There is also the backwards compatibility issue; how do you handle
>> existing ext2 filesystems that are currently using ASCII, and a lot
>> of existing code which assumes that the '/' and '\0' characters have
>> special meaning. For that reason, the only thing which makes sense for
>> the ext2 filesystem is to declare that filenames and volume labels are
>> in UTF-8.
> I agree with all that you say, but there is another issue for some
> people: some file systems are being maintained by other operating
> systems, so sometimes the underlying representation must vary from
> file system to file system.
This suggests that the file system driver needs to know the representation
used for that file system, and convert it to the representation that the
kernel is expecting?
Best wishes from Riley.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu