Linked by Thom Holwerda on Mon 30th Jan 2012 20:39 UTC
Thread beginning with comment 505192
To view parent comment, click here.
To read all comments associated with this story, please click here.
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
in reply to "RE[3]: Wow, That Was Simple"
RE[5]: Wow, That Was Simple
by shotsman on Tue 31st Jan 2012 16:48
in reply to "RE[4]: Wow, That Was Simple"
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.
RE[5]: Wow, That Was Simple
by frderi on Tue 31st Jan 2012 21:11
in reply to "RE[4]: Wow, That Was Simple"
RE[4]: Wow, That Was Simple
by leech on Mon 30th Jan 2012 23:15
in reply to "RE[3]: Wow, That Was Simple"
"/users
/system
/programs (or /Apps, in this day and age).
More is not needed at root.
/system
/programs (or /Apps, in this day and age).
More is not needed at root.
That looks a lot like:
Documents and Settings
Windows
Program Files
Just sayin' "
Yeah, and those that actually have to dig through file locations occasionally find the "windows way" a nightmare! I need to find where a file is on Linux? There are a ton of ways. I need the actual location of an executable? Use 'which <program>' and it'll show you the full path. You need to know what package a file belongs to? dpkg -S <filename> (at least on Debian based distributions.)
The Windows way is a mess, because while you have Program Files or Program Files (x86), not all installers default to put things there, and even then you can change the default so not all systems will have files in the same place.... Then you have the fact that some installers want to put the company name in there, so you end up getting a huge mess. A good example is Steam. C:\Program Files (x86)\Steam\SteamApps\common\rainbow six 3 gold\Mods\ is where I have to install mods to. Not all mod installers detect where it is installed, so I manually have to drop files in there.
Far easer to have /usr/games/doom/ and throw the files in there, wouldn't you say?
RE[5]: Wow, That Was Simple
by dorin.lazar on Tue 31st Jan 2012 01:21
in reply to "RE[4]: Wow, That Was Simple"
RE[5]: Wow, That Was Simple
by lucas_maximus on Tue 31st Jan 2012 01:22
in reply to "RE[4]: Wow, That Was Simple"
RE[4]: Wow, That Was Simple
by dorin.lazar on Tue 31st Jan 2012 01:19
in reply to "RE[3]: Wow, That Was Simple"
RE[4]: Wow, That Was Simple
by l3v1 on Tue 31st Jan 2012 07:01
in reply to "RE[3]: Wow, That Was Simple"





Member since:
2009-03-09
/system
/programs (or /Apps, in this day and age).
More is not needed at root.
That looks a lot like:
Documents and Settings
Windows
Program Files
Just sayin'