From: Chris Malton <chrism@cjsoftuk.dyndns.org>
To: linux-kernel@vger.kernel.org
Subject: Re: NCPFS can't handle extended characters.
Date: Tue, 22 May 2007 13:53:30 +0100 [thread overview]
Message-ID: <4652E7CA.9060909@cjsoftuk.dyndns.org> (raw)
In-Reply-To: <4652E735.7000206@cjsoftuk.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 705 bytes --]
Oops, see inline comments!
Chris Malton wrote:
> I found a bug in NCPFS that I haven't the time to fix right now.
>
> Here's the problem: if a file contains an extended (Charcodes 128-255)
> character, especially ` (or a even worse, an word converted ' (curled
> apostrophe) NCPFS goes butter side down on the directory listing.
>
> It doesn't hand the machine, but it does cause some serious issues on
> our network, is there a way to make NCPFS understand extended characters
> in file names?
I mean hang, and our network has lots of extended file system characters
on it.
>
> I would appreciate this being patched.
>
> I'll get round to it post-exams if nobody else does.
>
> Chris
Chris
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 2146 bytes --]
next prev parent reply other threads:[~2007-05-22 12:53 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 [this message]
2007-05-22 19:57 ` Alan Cox
2007-05-22 20:28 ` Chris Malton
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=4652E7CA.9060909@cjsoftuk.dyndns.org \
--to=chrism@cjsoftuk.dyndns.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®