Re:Understanding the bin, sbin, usr/bin , usr/sbin split (2010)
by Pxtl on Friday May 06, 2016 @08:52PM
(#11647794)
Still, clutters and confuses new users. In wonder if some of the fs apis could hide the silly/redundant directories?
[ Parent
| on HN ]
Re:Understanding the bin, sbin, usr/bin , usr/sbin split (2010)
by yrro on Saturday May 07, 2016 @06:00AM
(#11649017)
I much prefer compatibility symlinks actually existing in the file system over some complex, hidden pathname resolution override riles lurking in the kernel. That way, Windows lies.
Re:Understanding the bin, sbin, usr/bin , usr/sbin split (2010)
by arthur2e5 on Thursday May 19, 2016 @07:37PM
(#11734702)
> lurking in the kernel. That way, Windows lies.
Windows implements many overrides (e.g. "My Documents") as NTFS junctions with some hidden (+ system?) property set. (Sometimes you will find a proper hidden property handy, like in this case.)
Stuff like CON, NUL in non-UNC paths do hurt, though. Device files from an age without directories....
Re:Understanding the bin, sbin, usr/bin , usr/sbin split (2010)
by yrro on Friday May 20, 2016 @02:43PM
(#11740401)
Don't get me started on Windows' bizarre, barely-documented behaviour. Magical filenames pointing to devices and file virtualization are bad enough... just try to decipher whether a given registry path is what it appears, or is redirected through yet more hidden virtualization magic some time. And we haven't even come to the truly wondrous series of overrides that occur when looking up names in the NT object namespace...