From: Chris Malton <chrism@cjsoftuk.dyndns.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NCPFS can't handle extended characters.
Date: Tue, 22 May 2007 21:28:55 +0100 [thread overview]
Message-ID: <46535287.7060904@cjsoftuk.dyndns.org> (raw)
In-Reply-To: <20070522205723.0d0dc5ce@the-village.bc.nu>
[-- Attachment #1: Type: text/plain, Size: 941 bytes --]
Alan Cox wrote:
> For any real hope to answer things like that it would be useful to have
> precise descriptions of what fails, any messages logged when it occurs
> etc.
OK,
What fails: A dir on the folder containing the offending file results in
part listings or no listing at all.
There are no messages logged anywhere, dir completes successfully
without complaining. I'm going to recompile with the latest kernel and
debug in a few weeks time (add the debug option to the NCPFS kernel module).
On this occasion the offending files had a character produced by MS Word
in them. I can't find out which charcode at present (think it was
charcode 180).
Chris
>
> Alan
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 2146 bytes --]
prev parent reply other threads:[~2007-05-22 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 12:51 Chris Malton
2007-05-22 12:53 ` Chris Malton
2007-05-22 19:57 ` Alan Cox
2007-05-22 20:28 ` Chris Malton [this message]
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=46535287.7060904@cjsoftuk.dyndns.org \
--to=chrism@cjsoftuk.dyndns.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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®