Linked by David Adams on Mon 24th Aug 2009 09:21 UTC
Permalink for comment 380284
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



Member since:
2007-08-17
...not bin, sbin, opt, boot, usr, mnt, media, etc....
What is not logical about that? Just because you have not bothered to take the 30 minutes or so, that it would take to read up on and gain a good understanding of the Linux File Hierarchy Standard? If they put the binaries in boot, mounted removable media to bin and the bootloader files in mnt - I might see why that is not logical.
installing a program in linux is a guessing game as to where the files actually went.
Yes, because 'rpm -ql <packagename>' or 'dpkg -L <packagename>' is so very difficult - compared to a Windows installer which provides no straightforward means to find out what files it has placed on your harddisk.
The Linux File Hierarchy Standard and package management tools may not be obvious to use, they may not even be 'easy to use at first'. That does not mean they are not easy to use, nor does it mean they are not user friendly.