4 ms·
> The FHS at least has some semantic meaning that is more-or-less consistent or can be easily deduced, but Windows is just a hodgepodge. Really? C:\Windows -
by TazeTSchnitzel 11y ago
> The FHS at least has some semantic meaning that is more-or-less consistent or can be easily deduced, but Windows is just a hodgepodge.
Really?
C:\Windows - Windows itself
C:\Program Files - Applications
C:\Users - User data
- johnchristopher 11y agoIt seems clearer but when you install wamp or xampp you'll find a php.ini in c:\wamp\apache and c:\wamp\php (or sthg). Nice names (be it /etc or C:\Users) don't prevent developers to put their config file wherever they can read it. Usually in C:\Users\Alice\Ubisoft if they are in the game business. Or C:\Program Files\Steam\Steamapss if they are in the game business.
- wvenable 11y agoTalking about where PHP (a unix program) puts it's configuration on Windows is hardly a valid point. Even on Linux, that sucker can be hard to find. On my Linux server it is at least 5 levels deep and I have to run phpinfo() just to find it.
- johnchristopher 11y ago> Talking about where PHP (a unix program) puts it's configuration on Windows is hardly a valid point. That's because it's not my point but an example of "it's up to the dev to be consistent or to follow the platform's guideline" which is my point along and with "`Program Files' is a nice folder name but you are going to find some user configuration files in there'". If I remember correctly Foobar asks you when installing where to put its configuration files: user home, or program files. It should not. It should be in C:\Users\Alice\Local Settings (or was it LocalApps ?).
- chinpokomon 11y agoThere are guidelines for where developers are supposed to store configuration, and since Vista, it isn't in Program Files. In fact, making changes in Program Files is restricted to the System, or elevated processes. It is often times an indicator that a program is violating accepted practices if it requires elevation of privilege to run. Changes like that are supposed to be stored in the users AppData directory. For backwards compatibility. Vista and descendants provides a virtualized space where writes to restricted directories are allowed, but they are committed to a different isolated space on the disk, preventing a rogue program from, modifying files for which it should not have access. Neither Windows or Linux are perfect in this respect, but for a decade, Microsoft has been trying to unify how applications store user specific data and configuration. There are still ways for developers to abuse the system, but they are considerably restricted from the most glaring mistakes and in general it has gotten better with each revision.
- deleted 11y ago[deleted]
- vezzy-fnord 11y agoYes, you're completely ignoring all the special folders, the shell namespace and then of course everything at the bottom level of what you listed. Various NTFS features like reparse points and ADS do not help the case.
- pjc50 11y agoApplications go in Program Files (or is it Program Files (x86) or good old PROGRA~1), which is why you can find Chrome in C:\Users\username\AppData\Local\Google\Chrome\Application\chrome.exe User data goes in C:\Users\username\My Documents, except when it's a savedgame or the user saves it to the desktop or the application decides to keep it in AppData instead. Or if the user installs or inserts another disk. Windows is confined to Windows, apart from the bootloader. But sometimes, with an especially hapless error, you can get Windows to reassign the drive letter for C:, and all hell breaks loose. It sounds like people actually want Windows CE (no drive letters, everything OEM installed goes into \Windows, no exceptions)
- UnoriginalGuy 11y ago> which is why you can find Chrome in %AppData% Chrome installs in %AppData% so a non-admin user can install it and a non-admin process can update it. It is debatable if this is good behaviour, but it has nothing to do with the supposed confusion over Program Files. > Program Files (or is it Program Files (x86) or good old PROGRA~1) On 64 bit Windows 64 bit installations go in Program Files and 32 bit installations go into Program Files (x86). This is transparent to the installers themselves as Windows directs the installation appropriately based on bitness. 8.3 filenames are depreciated and only exist for backwards compatibility with MS Dos applications. > User data goes in C:\Users\username\My Documents No user data goes in the aptly named AppData folder (i.e. %AppData% or C:\Users\[user]\AppData). Personal files go in the Documents folder (it hasn't been called "My Documents" in approx. five years). > But sometimes, with an especially hapless error, you can get Windows to reassign the drive letter for C:, and all hell breaks loose. Your above issues are pretty sketchy but this one is now getting into the realm of absurd. You're effectively arguing that when you go out of your way to try and break Windows it, well, breaks. That is an astounding revelation. > It sounds like people actually want Windows CE (no drive letters, everything OEM installed goes into \Windows, no exceptions) People want a container model where everything is together.