Dots in the root of network drives
Dots in the root of network drives
Hello, I have problem with FAR 2.0 (1263). On our network drives, which are mapped, are strange . and .. items in file list. You can see on , that drive I: (mapped as JASPIS/USR:) is everything allright, on drive K: (mapped as JASPIS/USR:VEREJNY) are dots.
Last edited by ragimiri on Thu 01 Jan, 1970 01:00, edited 0 times in total.
Reason: Generalized the Subject
Reason: Generalized the Subject
Re: Dots in Novell NetWare drives
If it is not a bug, how is possible, that in version 1.75 there are no dots?
-
- Posts: 1326
- Joined: Mon 04 Apr, 2005 13:41
- Location: San Ramon, CA / Kharkov, UA
- Has thanked: 32 times
- Been thanked: 61 times
Re: Dots in Novell NetWare drives
In Far 1.75 there is a "workaround" for dots, but in 2.0 it was removed. If OS reports about dots in a root folder of share Far will show them as well. You have to just accept the situation as it is for the time being.ragimiri wrote:If it is not a bug, how is possible, that in version 1.75 there are no dots?
Мы не можем ждать милостей от Фара, взять их у него — наша задача! (C) Мичурин
- t-rex
- Страшный и ужасный
- Posts: 4910
- Joined: Tue 15 Mar, 2005 16:17
- Location: Tel-Aviv
- Has thanked: 1 time
- Been thanked: 8 times
- Contact:
Re: Dots in Novell NetWare drives
if you don't know what you are talking about, better don't say anything.
Re: Dots in Novell NetWare drives
Thanks for explanation.Yegor wrote:In Far 1.75 there is a "workaround" for dots, but in 2.0 it was removed. If OS reports about dots in a root folder of share Far will show them as well. You have to just accept the situation as it is for the time being.
-
- Posts: 7
- Joined: Fri 26 Dec, 2008 23:19
Current 2.0 build shows "." directory on network drives
Hey everybody,
downloaded the current 2.0 build and have a new and strange behaviour that wasn't there before. Now Far displays "." and ".." directories on network drives on CIFS/SMB shares, but not on Windows shares (which CIFS/SMB implementations I cannot tell, one of the drives is on an EMC though). Somehow those implementations are sending those directories as on UNIX and Far won't work correctly, as it doesn't know the concept of "." being the current directory. All file actions (copy/move, directory size etc.) are operating recursively on the "." directory, resulting in endless loops, endless copies and endless directory sizes...
This problem is even in the 3.0 alpha versions.
Thanks in advance and greetings...
downloaded the current 2.0 build and have a new and strange behaviour that wasn't there before. Now Far displays "." and ".." directories on network drives on CIFS/SMB shares, but not on Windows shares (which CIFS/SMB implementations I cannot tell, one of the drives is on an EMC though). Somehow those implementations are sending those directories as on UNIX and Far won't work correctly, as it doesn't know the concept of "." being the current directory. All file actions (copy/move, directory size etc.) are operating recursively on the "." directory, resulting in endless loops, endless copies and endless directory sizes...
This problem is even in the 3.0 alpha versions.
Thanks in advance and greetings...
-
- Posts: 7
- Joined: Fri 26 Dec, 2008 23:19
Re: Current 2.0 build shows "." directory on network drives
Hiho,
it's me again. Does nobody have this issue? Unfortunately I've got one of the earlier alphas here at work (build 1263) and that thing is unstable as hell - at least in Far terms (I mean was Far ever really unstable?). At least every other day Far dies. So I'd really like to use the current version, but I can't because of this issue. Every file action is unusable (e.g. copy, move, dir size) as Far will do its action indefinitely - while copying not so funny when your small directory gets multiplied times forever.
Anyways, was/is there ever a reason that "." should be displayed in Far? This seems to me to be a major bug, if Far doesn't know about "." being the current directory and handles it like every other one. Isn't this absolutely easily fixed by just checking for "." (if the underlying file system lists it) and just to ignore it?
Or should I file a "real" bug report?
Thanks'n'greetings
[Edit: s/no/know/ ]
it's me again. Does nobody have this issue? Unfortunately I've got one of the earlier alphas here at work (build 1263) and that thing is unstable as hell - at least in Far terms (I mean was Far ever really unstable?). At least every other day Far dies. So I'd really like to use the current version, but I can't because of this issue. Every file action is unusable (e.g. copy, move, dir size) as Far will do its action indefinitely - while copying not so funny when your small directory gets multiplied times forever.
Anyways, was/is there ever a reason that "." should be displayed in Far? This seems to me to be a major bug, if Far doesn't know about "." being the current directory and handles it like every other one. Isn't this absolutely easily fixed by just checking for "." (if the underlying file system lists it) and just to ignore it?
Or should I file a "real" bug report?
Thanks'n'greetings
[Edit: s/no/know/ ]
Last edited by Sir Diddymus on Wed 21 Dec, 2011 15:39, edited 1 time in total.
-
- Posts: 7
- Joined: Fri 26 Dec, 2008 23:19
Re: Current 2.0 build shows "." directory on network drives
Here's some output, anonymized. As previously stated, I'm guessing that somehow those CIFS implementations are sending the "." directory.
Code: Select all
Volume in drive H is 242
Volume Serial Number is 0000-0096
Directory of H:\
20.12.2011 12:46 <DIR> . .
15.09.2011 14:16 44.544 MB-SEI~1.XLS MB-xxxx-xxxxxxx.xls
15.09.2011 14:05 5.789 pixxxxxx.txt
13.12.2011 08:56 <DIR> Soxxxxxx
24.10.2011 14:55 314 trxxxxxx.sql
04.11.2011 09:44 <DIR> !Daxx
16.12.2011 13:11 <DIR> !Shxxxxx
29.11.2011 14:28 61.731 QA_REP~2.CSV qaxxxxxxxxxxx.csv
08.11.2011 09:23 <DIR> DOKUME~1 Doxxxxxxxxxxx
08.07.2011 10:20 <DIR> TALEND~2 Taxxxxxxxxxxxxxxx
10.10.2011 11:13 <DIR> DB2-ST~1 DBxxxxxxxxxxxx
20.12.2011 09:36 9.920 MAPPIN~4.XML maxxxxxxxxxxxxxxx
15.09.2011 14:26 52.078 MB-SEI~2.XLS MBxxxxxxxxxxxxxxxxxxxxxx.xls
14.09.2011 14:44 <DIR> PROJEC~1 Prxxxxxxxxxxxxxxx
[...]
Volume in drive H is 242
Volume Serial Number is 0000-0096
Directory of H:\opt
22.11.2011 14:05 <DIR> .
20.12.2011 12:46 <DIR> .. ..
22.11.2011 14:05 <DIR> app
0 File(s) 0 bytes
3 Dir(s) 78.405.907.456 bytes free
-
- Posts: 7
- Joined: Fri 26 Dec, 2008 23:19
Re: Current 2.0 build shows "." directory on network drives
Works! Thanks for implementing it so fast...