Linked by David Adams on Mon 24th Aug 2009 09:21 UTC
Permalink for comment 380366
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2005-08-18
Oh you mean like any file outside the users own file space? Again, once you actually get to the point that you have to or want to screw around with system files it does not matter if it's called "System Files", "Windows" or "/etc" or "/bin".
People aren't idiots, they can figure this stuff out when they need to.
Except the ones that goes in "Common Files", "c:\Windows" or one of it's many subfolders. This is of course only "documented" in the undocumented file format the particular installer system the application used, if at all.
Yes, I can see clearly now how that is much better than to actually have a built-in system for keeping track of what files goes where.
It's nice to see that Microsoft has learned from *nix to give each users his/hers own file space.
How is "Documents and Settings" and "User" any easier to understand than "/home"?