From: Ali Akcaagac <aliakc@web.de>
To: linux-kernel@vger.kernel.org, stockall@magma.ca,
hirofumi@mail.parknet.co.jp
Subject: Re: [BUG] FAT broken in 2.6.7-bk15
Date: Mon, 05 Jul 2004 06:50:07 +0200 [thread overview]
Message-ID: <1089003007.601.11.camel@localhost> (raw)
> > Yeah here the .config snipplet. But I still wonder how this
> > influences mounting an msdos or vfat partition. Unfortunately I am
> > no expert in FAT related stuff but I assume that textual stuff
> > stored in a filesystem shouldn't affect mounting and unmounting. The
> > only thing NLS changes in a filesystem is special charakters for
> > filenames but it doesn't change the technical structure of the FS
> > itself so in worst case I only get some strange characters shown in
> > filenames.
> Do you have both nls_cp437 and nls_iso8859_1 modules loaded?
Good point. After doing a normal lsmod I only saw that "msdos" and "vfat" modules got loaded and no further language specific stuff. I then tried modprobing 'nls_cp850' and 'nls_iso8859_15' which got loaded fine but same issues. After reconfiguring the Kernel and >>>manually<<< adjusting the msdos part from 437 to 850 and iso8859-1 to iso8859-15 and reloading the msdos module everything worked as expected again. Although I do questionize whether the current changes are so optimal for the user. In the past and that's how I understood OGAWA Hirofumi the msdos driver got it's information from the big NLS submenu of the Kernel configuration and now it has been split out due to some people reporting problems when having select utf8. But having >>>manually<<< to adjust msdos to point to nls modules other than 437 and iso8859-1 is quite cumbersome and leads to misunderstanding. I did saw the changes to msdos when going through my configure process but I assumed that it automaticly handles 437 (as it pointed on default) and I wondered why it has been split out. But I now figured out that it's not loading an OWN module, it's only POINTING to a NLS module >>>by name<<< and that you need to make sure >>>manually<<< to either change it to the module you selected in the NLS submenu or to adjust the NLS submenu by adding the module which msdos refers by default.
It would be pretty nice to have this 'idea' being rethought a bit more so that it doesn't lead into confusion and missunderstandings.
next reply other threads:[~2004-07-05 4:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 4:50 Ali Akcaagac [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-05 6:08 [BUG] FAT broken in 2.6.7-bk15 Ali Akcaagac
2004-07-04 22:11 Ali Akcaagac
2004-07-04 22:17 ` Jesse Stockall
2004-07-05 5:02 ` OGAWA Hirofumi
2004-07-04 14:34 Ali Akcaagac
2004-07-04 16:36 ` OGAWA Hirofumi
2004-07-04 11:28 Ali Akcaagac
2004-07-04 12:18 ` Andries Brouwer
2004-07-04 13:44 ` Jesse Stockall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1089003007.601.11.camel@localhost \
--to=aliakc@web.de \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=stockall@magma.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox