> All conversions works correctly under 2-2-13 kernel in both positions: with and
> without case convertion. I don't change any configuration except kernel
> changing, and have such effect. I tried "koi8-r", cp437 "iso-8859-1" as
> default in kernel nls, but it's no effect. Only when I switch off conversion
> function, it's became work.
No, it does not work. It did not lowercased your filenames even when
it should. If you had 'NCP' in ASCII instead of CP866, it was lowercased
on 2.2.13, but if it had 'NCP' in CP866, it was not lowercased... So
when mixing latin and azbuka you could get 'nCp' - that's wrong. If
you do not want DOS created filenames to be lowercased, do not select it.
(BTW, you can see it on file 'SEMENOV.doc' in 2.2.13 picture - '.doc'
was lowercased, but SEMENOV (CEMEHOB) was not...)
> By the way, I try to load 2.2.16 - it's worse ewen
> under 2.4.0. Under 2.2.16 russian names of directories and files doesn't detect
> at all, they desplayed as abracadabra like ")%../ " and so on.
NLS16 screwed 2.2.16 NCP. I sent patch to Urban and Alan, but it looks
like that 2.2.17-pre13 still has not it fixed.
> The screenshots your ask is in attachement (from bash). No effect. It's no KFM
> bug, by my mind.
> Near that screenshots are the screenchots from 2-2-13 WITH lowercasing(i.e. the
> same parameters that tested 2.4.0) It's no bug!!!
No. You did not do 'ls -l'... Of course that filenames are lowercased -
- it is intentional. But your bash listing does not show whether Linux
thinks that files are files or that they are directories...
> > Try telnet/ping to your machine when it does not react to
> > ctrl-alt-backspace or ctrl-alt-del (mine X server ignores ctrl-alt-del, btw;
> >if I (just > by accident) run X and I want to reboot, I must hit
> >ctrl-alt-backspace and then ctrl-alt-del). Also, what about alt-sysrq-K?
> Sorry, but it isn't telnet on my comp by security reasons
So try ping... or ssh... or anything else...
> RESUME.
> We have the such picture.
Yes.
> It is normal work both with lowercase and uppercases with 2.2.13.
No. See CEMEHOB.doc on your picture.
> It is partially workable (with uppercase) and partially unworkable (with
> lowercase) with 2.4.0
No. If you do 'nwdir -v' in that directory, you'll see that some files
have DOS as owning namespace, some have OS/2 (and maybe some have NFS
(though if you had NFS namespace, ncpfs will use this and will not
do any case plays as NFS is case sensitive).
Only filenames created by DOS are lowercased, because of, for your
convience when moving from DOS namespace to OS/2 namespace, you want
to still see lowercased filenames as you saw before you added OS/2
namespace to volume.
> It's worse in 2.2.16 (it's no screenshots, but if you want I can analize a
> behavior of 2.2.16 with various parameters)
Yes, 2.2.16 is broken.
> - 2.4.0 shows wrong russian names with uppers, but shows something.
What? I looked at bash-2.4.0-upper and bash-2.4.0 and I see that all
characters were correctly uppercased, if entry had to be uppercased.
Where letter was damaged by uppercasing?
> 2.2.16 shows full abracadabra in the same
> configuration.
Yes. Urban (I believe that Urban... if not, sorry) by accident
passed always zero as high unicode byte into unicode translation,
so it worked for iso-8859-1 only...
Go to linux/fs/ncpfs/ncplib_kernel.h and replace (twice) first
parameter to nls_out->uni2char(0x00, uc.uni2, .....) with
nls_out->uni2char(uc.uni1, uc.uni2, .....). Then you'll get same
behavior which 2.4.0 has. Which is IMHO correct behavior.
If you are using case-insensitive namespace (OS/2) and your
server can open 'NCP', but cannot open 'ncp', your server
is broken, isn't it?
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jul 31 2000 - 21:00:18 EST