Linked by David Adams on Mon 24th Aug 2009 09:21 UTC
Thread beginning with comment 380355
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Whats wrong with a logical file system?
by Soulbender on Mon 24th Aug 2009 19:00
in reply to "RE[4]: Whats wrong with a logical file system?"
Maybe a system file is a file that is required by the system and should not be deleted?
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.
Browse to \Program Files\Program and there are your files.
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.
Your user files are either there or in \Documents and Settings\User\AppData on XP, and in \Users\User\AppData in Vista.
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"?
RE[6]: Whats wrong with a logical file system?
by dragossh on Mon 24th Aug 2009 19:30
in reply to "RE[5]: Whats wrong with a logical file system?"
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.
People aren't idiots, they can figure this stuff out when they need to.
While you and me can figure out what goes into /etc, most people get afraid only by looking at its name. But if the system is cleanly designed, the user will not be afraid to experiment (see Amiga).
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.
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.
Can you tell me which sane piece of software installs things in \Windows? And Common Files are… common files used by the apps?
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"?
How is "Documents and Settings" and "User" any easier to understand than "/home"?
It’s not. In fact, /home is more user-friendly. Again, I’m not saying x is easier to understand than y. They are all equal. I’m talking about the illusion of user-friendliness (yes, there is one).





Member since:
2008-12-16
Gee, I don't know. Maybe a system file is a file that is required by the system and should not be deleted? And maybe Program Files contains the files needed by programs to run. Wow! It is logical.
Browse to \Program Files\Program and there are your files. Your user files are either there or in \Documents and Settings\User\AppData on XP, and in \Users\User\AppData in Vista.