Linked by Thom Holwerda on Mon 30th Jan 2012 20:39 UTC
General Unix Finally something really interesting to talk about. If you've used UNIX or any of its derivatives, you've probably wondered why there's /bin, /sbin, /usr/bin, /usr/sbin in the file system. You may even have a rationalisation for the existence of each and every one of these directories. The thing is, though - all these rationalisations were thought up after these directories were created. As it turns out, the real reasoning is pretty damn straightforward.
Thread beginning with comment 505303
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: Wow, That Was Simple
by lucas_maximus on Tue 31st Jan 2012 16:36 UTC in reply to "RE[6]: Wow, That Was Simple"
Member since:

I have re-read your original comment 3 times.

Pretty much every installer I use puts it all it files under the installation directory. Modern programs put their user settings in /Users/AppData.

If it has the same "bitness" as the installation then it goes in Program Files, if it is 32bit ... Program Files(x86). This seems pretty straight forward to me.

I really get what the problem is?

The shit thing on Windows 64bit is for compatibility, using system32 for 64bit programs and WOW64 for 32bit programs.

Reply Parent Score: 2

RE[8]: Wow, That Was Simple
by bogomipz on Tue 31st Jan 2012 18:35 in reply to "RE[7]: Wow, That Was Simple"
bogomipz Member since:

I really get what the problem is?

You wouldn't say that if you weren't so lucky to be using an English version of Windows. Over here in Norway, half the programs install to "C:\Program Files" and the other half to "C:\Programfiler". Depends on whether the guy writing the installer used the proper API to get the directory or just hardcoded the path.

Reply Parent Score: 4

lucas_maximus Member since:

Not really the fault of the system though.

Reply Parent Score: 2