From: Tarkan Erimer <tarkane@gmail.com>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Andrew Morton <akpm@osdl.org>,
arjan@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG]: Software compiling occasionlly hangs under 2.6.15-rc1/rc2 and 2.6.15-rc1-mm2
Date: Thu, 1 Dec 2005 20:47:37 +0000 [thread overview]
Message-ID: <9611fa230512011247ifc0d0d1xb92849dbe63d1325@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0511301347490.14736@hermes-1.csi.cam.ac.uk>
On 11/30/05, Anton Altaparmakov <aia21@cam.ac.uk> wrote:
> Yes. (-:
>
> These just means that you have mounted with a bad default code page or
> whatever you want to call it and the ntfs volume contains characters
> whethe the Unicode (i.e. NTFS) to your code page conversion fails (NLS
> conversion returns error due to non-existant character in your code page).
> As the message suggests if you adjust your mount options to include the
> "nls=utf8" option the errors will go away and everything will work except
> maybe your terminal/gui may dislay some garbage characters if it does not
> understand utf8 characters but at least you will see all
> files/directories.
Hi,
I mounted with "nls=utf8" option as you mentioned and all the related
error messages disappeared. Thanks :)
Regards
next prev parent reply other threads:[~2005-12-01 21:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-25 11:12 Tarkan Erimer
2005-11-25 11:19 ` Arjan van de Ven
2005-11-27 11:17 ` Tarkan Erimer
2005-11-27 11:58 ` Arjan van de Ven
2005-11-27 19:08 ` Tarkan Erimer
2005-11-27 19:12 ` Arjan van de Ven
2005-11-27 19:18 ` Tarkan Erimer
2005-11-28 0:57 ` Andrew Morton
2005-11-29 21:57 ` Tarkan Erimer
2005-11-29 23:10 ` Andrew Morton
2005-11-30 13:53 ` Anton Altaparmakov
2005-12-01 20:47 ` Tarkan Erimer [this message]
2005-12-01 20:42 ` Tarkan Erimer
2005-12-02 12:49 ` Tarkan Erimer
2005-12-05 14:30 ` Tarkan Erimer
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=9611fa230512011247ifc0d0d1xb92849dbe63d1325@mail.gmail.com \
--to=tarkane@gmail.com \
--cc=aia21@cam.ac.uk \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--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
all inboxes | Powered by JetHome®