Should frn: enumerate all the associated file names of a hardlinked file?
"One" hardlinked file, known as both r.exe & rr.exe.
(It might end up being the same sort of situation as:
Should Everything Be Seeing [new] Hard Links?
&
Hard Link Oddity)
Everything Shows Hardlink(s), but only one frn:
Everything Shows Hardlink(s), but only one frn:
Everything Shows (all) Hardlink(s) of a [same named] filename, but only one frn: to a particular file.
Should frn: enumerate all the associated file names of a hardlinked file?
"One" hardlinked file, known as both r.exe & rr.exe.
(It might end up being the same sort of situation as:
Should Everything Be Seeing [new] Hard Links?
&
Hard Link Oddity)
Should frn: enumerate all the associated file names of a hardlinked file?
"One" hardlinked file, known as both r.exe & rr.exe.
(It might end up being the same sort of situation as:
Should Everything Be Seeing [new] Hard Links?
&
Hard Link Oddity)
Re: Everything Shows Hardlink(s), but only one frn:
(In the same vein ... food for thought...
Bitness
Redirectors
Links
in particular with Windows files
32-bit Everything may (does?), 32-bit applications may (does?) go through windows "redirector" (System32 vs SysWOW64 kind of thing)
so a hard link to a file, or even a link to a file, what is shown, returned, is within the context of bitness/redirectors
so you may get back different results based on who you start out looking for something, & what a particular program "sees"
hmm...?
where is 'notepad' on windows seven)
Bitness
Redirectors
Links
in particular with Windows files
32-bit Everything may (does?), 32-bit applications may (does?) go through windows "redirector" (System32 vs SysWOW64 kind of thing)
so a hard link to a file, or even a link to a file, what is shown, returned, is within the context of bitness/redirectors
so you may get back different results based on who you start out looking for something, & what a particular program "sees"
hmm...?
where is 'notepad' on windows seven)
Re: Everything Shows Hardlink(s), but only one frn:
This is currently a limitation with Everything.
Looks like the first instance of the hard link is shown for frn:
I've added to my TODO list: look up all hard links when using frn:
I'm even considering indexing file frns, which would allow for finding hardlinks (duplicated frns).
Everything tries to avoid system32 (and other) redirections. I'm aiming to show the file system exactly as it is, which does cause some issues with gathering unindexed file information or opening certain system files. Everything disables windows folder redirection where possible.
I'll consider an option to show the redirected paths.
The main aim of frn: is to find the original filename of a file after it was mangled or detected as corrupt from a chkdsk operation.
eg: Attribute record (128, "") from the file record segment 857930 is corrupt.
Looks like the first instance of the hard link is shown for frn:
I've added to my TODO list: look up all hard links when using frn:
I'm even considering indexing file frns, which would allow for finding hardlinks (duplicated frns).
Everything tries to avoid system32 (and other) redirections. I'm aiming to show the file system exactly as it is, which does cause some issues with gathering unindexed file information or opening certain system files. Everything disables windows folder redirection where possible.
I'll consider an option to show the redirected paths.
The main aim of frn: is to find the original filename of a file after it was mangled or detected as corrupt from a chkdsk operation.
eg: Attribute record (128, "") from the file record segment 857930 is corrupt.