The macosxhints Forums - kernel panic everytime I use ping

The macosxhints Forums (http://hintsforums.macworld.com/index.php)

- UNIX - General (http://hintsforums.macworld.com/forumdisplay.php?f=16)

- - kernel panic everytime I use ping (http://hintsforums.macworld.com/showthread.php?t=60071)

Quote:

Originally Posted by voldenuit (Post 318640)

I tend to use full rather than delta system updater, perhaps that could make a difference ?

My system is newly rebuilt (after a hard drive crash), so is the result of a "combo" update (from Software Update)

Code:

% ls -d /Library/Receipts/MacOSX*

/Library/Receipts/MacOSX10.3.9.pkg

/Library/Receipts/MacOSX10.4.Universal.pkg

/Library/Receipts/MacOSXUpdCombo10.4.7PPC.pkg



% ls -d /Library/Receipts/Sec*

/Library/Receipts/SecUpd2006-004Ti.pkg

But the version of 'ping' that I have seems to be from the BaseSystem.pkg that was on the Tiger DVD:

Code:

% grep_pkg /sbin/ping

./sbin/ping     104555  0/0     33264   952160172

./sbin/ping6    104555  0/0     42748   2886917250

*** BaseSystem.pkg ***



% ls -ld /Library/Receipts/BaseSystem.pkg 

drwxrwxr-x   3 root  admin  102 Aug 16 19:04 /Library/Receipts/BaseSystem.pkg

Here's my 'grep_pkg' script:

Code:

#!/bin/sh



# grep_pkg

# This script searches the bom files in /Library/Receipts

# for the component name given as a command line argument

# It will show the info about that component from the bom file

# followed by the name of the pkg that contained that component

# Cameron Hayne (macdev@hayne.net), Sept 2004

 

name=$1

cd /Library/Receipts

for pkg in *.pkg; do

    find "$pkg" -name '*.bom' -print0 | xargs -0 lsbom | grep "$name"

    if [ $? = 0 ]; then

        echo "*** $pkg ***"

        echo "------------------------------"

    fi

done

Thanks for the very handy grep_pkg script, I didn't find any other occurrences of ping neither, even when searching just for /ping . How did you manage to get this receipt on a fresh Tiger install:

/Library/Receipts/MacOSX10.3.9.pkg ?

Now we all look Trevors way to find out how he managed to end up with a more recent version of ping on his system.
Compiled you own ping from a patched Darwin source, then forgot about it ;) ?

Quote:

Originally Posted by voldenuit (Post 318687)

How did you manage to get this receipt on a fresh Tiger install:

/Library/Receipts/MacOSX10.3.9.pkg ?

I wondered that too.
I hadn't looked at the contents of that pkg before, but now I see that it (and the MacOSX10.4.Universal.pkg) are actually badly named - they actually are part of the developers tools (supplying the libraries used when targeting other OS X versions than the one on the development system).
They only install stuff under /Developer:

Code:

% pkgsummary /Library/Receipts/MacOSX10.3.9.pkg | grep -v Developer



% pkgsummary /Library/Receipts/MacOSX10.4.Universal.pkg | grep -v Developer

Code:

% ls -d /Library/Receipts/MacOSX*

/Library/Receipts/MacOSX-File-0.66.pkg        /Library/Receipts/MacOSXUpdCombo10.4.5PPC.pkg /Library/Receipts/MacOSXUpdateCombo10.4.4.pkg

/Library/Receipts/MacOSX10.3.9.pkg            /Library/Receipts/MacOSXUpdCombo10.4.6PPC.pkg

/Library/Receipts/MacOSX10.4.Universal.pkg    /Library/Receipts/MacOSXUpdCombo10.4.7PPC.pkg



% ls -d /Library/Receipts/Sec*

/Library/Receipts/SecUpd2005-007Ti.pkg /Library/Receipts/SecUpd2006-002Ti.pkg /Library/Receipts/SecUpd2006-004Ti.pkg

/Library/Receipts/SecUpd2006-001Ti.pkg /Library/Receipts/SecUpd2006-003Ti.pkg



% grep_pkg /sbin/ping

./sbin/ping     104555  0/0     33264   1312972394

./sbin/ping6    104555  0/0     42748   2709568312

*** BaseSystem.pkg ***

------------------------------



% ls -ld /Library/Receipts/BaseSystem.pkg/

drwxrwxr-x   3 root  admin  102 Oct  5  2005 /Library/Receipts/BaseSystem.pkg/

In thinking about this a bit more, I have what I think is a reasonable guess/explanation for the difference. The computer in question is a PCI-express PowerMac G5 dual core 2 GHz. This computer was released after Tiger had been out for awhile, so the original install of OS X on this computer did not use a retail Tiger DVD.

It was initially shipped with a special build of 10.4.2?, if memory serves. Possibly the build shipped from Apple with the then-new hardware had slightly later compile dates for items than the compile dates of the stock Tiger build?

Trevor

That sounds like a very probable explanation.

It's astonishing that Apple will release such builds that seem to be from another branch than the stable distribution.

I'll keep that in mind when debugging in the future:
There could be different binaries on seemingly identical OS versions.

They just did it again with a custom build of 10.4.7 for the Mac Pro and that version even has an extra SecUpdate different from the main build...

Hopefully they'll be able to keep track of all these different builds, it could be really nasty to debug when you try to reproduce a problem on another machine, assuming they use identical OS components when they do not.