Michal Hrusecky wrote:
Linda Walsh - 12:25 28.07.12 wrote:
Nelson Marques wrote:
Ever heard of FHS? It's stands for Filesystem Hierarchy Standard.
Enjoy the reading :)
It is based on really screwed up reasoning. Why was it accepted?
Regardless, Suse doesn't follow it now, so why not move ahead with a more soundly reasoned solution.
AFAIK, we follow it, do you have any counterexample?
I gave a bunch of statistics 35% of the binaries in bin are 64bit. bin contains only 25% of the overall packages, so only 20% of the libraries in lib & lib64 are 32-bit. The rest are 64-bit. The original reasoning was continued and widespread usage of 32-bit programs. However, If I look at what those 32-bit programs are supporting -- in bin: master-boot-code-1.22-7.1.2.i586 sas_ir_snmp-3.17-1092.i386 sas_snmp-3.17-1092.i386 sas_snmp-3.17-1092.i386 sas_ir_snmp-3.17-1092.i386 sas_ir_snmp-3.17-1092.i386 ---- Suse's boot code. and some 3rd party snmp HW drivers that I don't run or need. So we have 20% of the libraries reserving 65% of /usr/lib for 1 suse program? Um... is that a good enough counter example?
You might need 32-bit and 64-bit libraries at the same time as you may have 32bit program requiring it and different 64bit one at the same time. On the other hand having both 32bit version and 64bit version of program doesn't really make huge sense apart from few minor specialized cases.
---- Can't think of too many examples, most are because they haven't gotten a new version out yet. Can you think of a counter-example? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org