NCPFS can't handle extended characters.
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 would appreciate this being patched.
I'll get round to it post-exams if nobody else does.
Chris
Oops, see inline comments!
Quoted 5 lines · Chris Malton
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.
Quoted 6 lines
I would appreciate this being patched.
I'll get round to it post-exams if nobody else does.
Chris
Chris
Quoted 5 lines · On Tue, 22 May 2007 13:51:01 +0100 Chris Malton <[email protected]>…
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.
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.
Alan
Quoted 3 lines · Alan Cox
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
Quoted 9 lines
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/