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 505230
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Wow, That Was Simple
by lucas_maximus on Tue 31st Jan 2012 01:22 UTC in reply to "RE[4]: Wow, That Was Simple"
lucas_maximus
Member since:
2009-08-18

99% of all installers let you modify the installation path ... just saying.

Reply Parent Score: 2

RE[6]: Wow, That Was Simple
by leech on Tue 31st Jan 2012 14:39 in reply to "RE[5]: Wow, That Was Simple"
leech Member since:
2006-01-10

Yeah, but doesn't that kind of negate having a simplified path? This was my point, if you manually have to track down where the data goes, then there is failure on the part of the installer in the first place.

Reply Parent Score: 2

RE[7]: Wow, That Was Simple
by lucas_maximus on Tue 31st Jan 2012 16:36 in reply to "RE[6]: Wow, That Was Simple"
lucas_maximus Member since:
2009-08-18

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