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 505593
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: Wow, That Was Simple
by siride on Thu 2nd Feb 2012 04:51 UTC in reply to "RE[5]: Wow, That Was Simple"
siride
Member since:
2006-01-02

You can blame programs that hardcode paths like System32. Yes, in 64-bit Windows, System32 holds the 64-bit system files and SysWOW64 holds the 32-bit system files. But it wasn't a good technical design decision, it had to do with crappy 3rd party software. Since Microsoft is in the business of actually allowing 3rd party software and drivers to work consistently, they have to make compromises like this (and this one isn't a problem, just an oddity).

Reply Parent Score: 2