vfat: missing iso8859-1 charset
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
The vfat kernel code has two dependencies: the code page (437) and the iocharset (iso8859-1), and while the former is built-in (like the vfat code itself), the latter is built as an external module, making vfat unusable unless the nsl_iso8859-1 ko is available at the moment a vfat filesystem is mounted.
What is just a discrepancy in the config that we never hit (since we are shipping the nsl_iso8859-1 .ko in our initrd), became a problem in kernel derivatives of our -generic kernel (e.g. snappy) where we don't have any control on the modules people pack in their initrd, and in case the boot partition is a vfat partition that is being mounted during the boot.
For this reason, i propose to fix the root problem and turn CONFIG_
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1677230
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.