public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ali Akcaagac <aliakc@web.de>
To: linux-kernel@vger.kernel.org, hirofumi@mail.parknet.co.jp
Subject: Re: [BUG] FAT broken in 2.6.7-bk15
Date: Mon, 05 Jul 2004 08:08:55 +0200	[thread overview]
Message-ID: <1089007735.675.6.camel@localhost> (raw)

> But you didn't install these. So fatfs couldn't do what you specified,
> then fatfs logged it and returns error.
> 
> Looks like you want to the following config.
> 
> CONFIG_FAT_DEFAULT_CODEPAGE=850
> CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-15"

Right I figured this one out myself already (see the other mail to you earlier this morning). I only questionize whether having to do this "manually" is such a good idea and if it doesn't lead to misunderstanding (better explaination in my other mail too).

I recommend to have something like this:

check whether some default NLS and character encoding has been selected in default NLS option.

- If not select 437 and iso8859-1 automatically for msdos and also 'enable' these automatically in the default NLS setup.

- If something has been selected in the default NLS already then popup a submenu which only shows those that you already have selected in the default NLS setup. So you can chose between those you already have selected.

- If only utf-8 has been selected in default NLS previously then throw out a warning or something.

At least in any cases make sure that you MUST select something to get msdos and fat support compiled and working correctly so that cases like mine NEVER happens.



             reply	other threads:[~2004-07-05  6:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-05  6:08 Ali Akcaagac [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-07-05  4:50 [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=1089007735.675.6.camel@localhost \
    --to=aliakc@web.de \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    /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