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 505193
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Wow, That Was Simple
by phoenix on Mon 30th Jan 2012 21:50 UTC in reply to "RE[3]: Wow, That Was Simple"
phoenix
Member since:
2005-07-11

Windows 7 is closer:
\Users
\Windows
\Program files
\Program files(x86)

Reply Parent Score: 5

RE[5]: Wow, That Was Simple
by shotsman on Tue 31st Jan 2012 16:48 in reply to "RE[4]: Wow, That Was Simple"
shotsman Member since:
2005-07-22

And the Windows directory layout is a paragon of logical thought?

Why is the 'hosts' file buried in WINDOWS/System32/Drivers/etc?

'System32'? of an 64bit OS?

I've been using a variety of Operating Systems since DEC Dos V8 on the same PDP-11 as K&R, VMS, i/OS through to the likes of Android and IOS.

I have to say that the LSB version of 'where things are put' works for me.

Finally, I'd really like to shake the hand of whoever thought it would be neat to default some critical directories (eg Program Files in windows) to contain a SPACE character.
I'd give them a 'Glasgow Handshake'.

Frankly every OS has its oddities.

Reply Parent Score: 4

RE[6]: Wow, That Was Simple
by siride on Thu 2nd Feb 2012 04:51 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

RE[5]: Wow, That Was Simple
by frderi on Tue 31st Jan 2012 21:11 in reply to "RE[4]: Wow, That Was Simple"
frderi Member since:
2011-06-17

Mac OS X Since 10.0 :

/Users
/System
/Applications

Reply Parent Score: 0