This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See for documentation how
to enable and use -proposed. Thank you!

** Tags added: verification-needed-xenial

** Tags added: verification-needed-yakkety

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  vfat: missing iso8859-1 charset

Status in linux package in Ubuntu:

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_NLS_ISO8859_1=y to make the vfat code completely independent on
  any external factor.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to