| 1 |
Thanks to all of you who have tried to help me. |
| 2 |
|
| 3 |
As it turned out, comparing MD5 sum is intractable, |
| 4 |
/usr/lib64 alone contained more than 500,000 files ! |
| 5 |
|
| 6 |
The /etc tree didn't show significant differences. |
| 7 |
|
| 8 |
So, I resorted to keep my 4 cores busy over the weekend to |
| 9 |
re-emerge the whole machine. |
| 10 |
|
| 11 |
That's the price for a highly configurable and up-to-date system like |
| 12 |
Gentoo - but I like it. But it's the first time I needed to do it since |
| 13 |
several years, now. |
| 14 |
|
| 15 |
Helmut. |
| 16 |
|
| 17 |
On 05/17/2011 10:21:16 PM, Volker Armin Hemmann wrote: |
| 18 |
> On Tuesday 17 May 2011 17:57:42 Blakawk wrote: |
| 19 |
> |
| 20 |
> > As far as i remember, i don't see why modification times will |
| 21 |
> enter |
| 22 |
> in |
| 23 |
> > the md5sum computation process, as they are not part of the file |
| 24 |
> but of |
| 25 |
> > the filesystem's inode... it's definitely possible to compare two |
| 26 |
> > binaries on two different system if they are compiled with the |
| 27 |
> same |
| 28 |
> > compiler version and libraries |
| 29 |
> |
| 30 |
> in theory. In practice only a slight change here and there - might |
| 31 |
> result in |
| 32 |
> huge changes. 'Almost identical' but the things that are not |
| 33 |
> identical |
| 34 |
> will |
| 35 |
> screw you up. Almost identical is like 'totally different' in this |
| 36 |
> case. |
| 37 |
> |
| 38 |
> Instead wasting time comparing the machines, he should find the |
| 39 |
> culprit for |
| 40 |
> the segfault. KDE's backtracking tool (drkonqi) and strace help a lot |
| 41 |
> with |
| 42 |
> that. If he knows where it fails, he at least has a chance to find |
| 43 |
> out |
| 44 |
> why. |
| 45 |
> |
| 46 |
> |
| 47 |
> |
| 48 |
> |
Archives