[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensuse
Subject:    Re: [opensuse] Re: Why bin & no bin64? => lets fix lib64=>lib, bin(32),lib(32)=>/usr32/{bin,lib}
From:       Werner Flamme <werner.flamme () email ! de>
Date:       2012-07-31 12:26:21
Message-ID: 5017CEED.40302 () email ! de
[Download RAW message or body]

[31.07.2012 14:17] [Linda Walsh]:
> Michal Hrusecky wrote:
>> Linda Walsh - 11:08 30.07.12 wrote:
>>> 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.
>> 
>> I was asking for examples where we do not follow FHS ;-)
> By putting 64-bit native programs in the native /usr/lib directory.

Yes, and a lot of them:
for DAT in /usr/lib/*; do file $DAT >> usrlib.txt; done
grep -c '64-bit' usrlib.txt
19
ls -l /usr/lib | wc -l
806

19 of 806 files are in the wrong directory! openSUSE violates FHS! Alarm!

> Why the intermix 32 and 64 bit programs though is a bit odd...

One of them is /usr/lib/chrome_sandbox. Maybe you should ask google.com
why they mix.

Just my 2¢
Werner
-- 
To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse+owner@opensuse.org

[prev in list] [next in list] [prev in thread] [next in thread]