Linked by Kroc Camen on Fri 9th Apr 2010 10:29 UTC
Linux "To be clear about this article's intent, it's not to bash Microsoft, or Windows. Because to be fair, despite using Linux 95% of the time while I'm on the PC, I can find more faults with it than Windows. So, this article's goal is to highlight some of the major pluses of Linux, and also showcase where Windows could improve in the future, should Microsoft take heed of the suggestions."
Thread beginning with comment 418178
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: What about:
by renhoek on Fri 9th Apr 2010 21:18 UTC in reply to "What about:"
Member since:

mounts - volume mount points
hard links - mklink
sym links- junction point
watches - EGP-WP98
super computers - windows datacenter edition

i REALLY hates those lunix fanboys who have absolutely no knowledge of windows at all saying it's bad. Every os has it's strong and weak points, but please only comment if you know what you are talking about.

Reply Parent Score: 1

RE[2]: What about:
by jabjoe on Tue 13th Apr 2010 09:24 in reply to "RE: What about:"
jabjoe Member since:

You're making a big assumption about my knowledge of Windows.

Yes volume mounts are the same as mount. But few file system support them, only really NTFS to my knowledge.

Junction points are like folder only sym links. In fact junctions points, sym links and volume mounts are all NTFS reparse points. NTFS also supports hard links. mklink (which doesn't come as standard) does hard links, sym links and junction points. What really annoys me is how this all translates into how it's used. As the underlying functionality is only really NTFS, it can't be used. Explorer namespaces try and give you one file hierarchy, and you can do "mount" of a namespace at a folder, and shortcuts are used as sym links. But it might look right to a user, but because it's not actually an OS filesystem, it can't be used from code (not with the standard file calls) or command line, which greatly reduces its use. In code there seams to be some push towards using ITEMIDLIST instead of paths, so you can use namespace objects as files, but to me, it would be better to fix the underlying system and use paths.

Windows CE is not the same kernel as Windows NT. It's a different OS. Not the same. The embedded linux devices are running the same kernel as the super computer. Compiled for different architecture, with different options on and off, and maybe a few code tweaks, but basically the same kernel.

Windows super computers - not saying there aren't any, but there aren't many, least not at top of the league.

Reply Parent Score: 1