Where can I find ibSystem.B.dylib?

First, it should be libSystem.B.dylib and second, it normally resides in /usr/lib/ and, in /Developer/SDKs/MacOSX10.7/usr/lib/ if Xcode installed.

Use the free EasyFind, it finds everything, hidden or not.

Or just find (in Terminal):

find / -iname libSystem.B.dylib 2>/dev/null

/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS5.0.sdk/usr/lib/li bSystem.B.dylib

/Developer/SDKs/MacOSX10.6.sdk/usr/lib/libSystem.B.dylib

/Developer/SDKs/MacOSX10.6.sdk/usr/libexec/oah/Shims/libSystem.B.dylib

/Developer/SDKs/MacOSX10.7.sdk/usr/lib/libSystem.B.dylib

/usr/lib/libSystem.B.dylib

BTW, just looked at EasyFind, looks good.

Tony T1 wrote:

BTW, just looked at EasyFind, looks good.

Sometimes a GUI hleps especially if your dslectic that can't speel. 😝

ds store wrote:

Sometimes a GUI hleps especially if your dslectic that can't speel. 😝

I was referring to myself of coruse. 🙂

I prefer setting Spotlight to search System files and invisibles, by name, (saved search for that). There are only a handful that it won't report. For the others, since I prefer searching by name, is to update the locate database and use Terminal. I use the uncrippled locate.updatedb command from Leopard.

baltwo wrote:

I use the uncrippled locate.updatedb command from Leopard.

Shhh, don't tell Apple, 10.5 is taboo.

Oh, they know. I've posted many a thread documenting that. IIRC, I've even posted the uncrippled script. If not, here it is:

#!/bin/sh

#

# Copyright (c) September 1995 Wolfram Schneider <wosch@FreeBSD.org>. Berlin.

# All rights reserved.

#

# Redistribution and use in source and binary forms, with or without

# modification, are permitted provided that the following conditions

# are met:

# 1. Redistributions of source code must retain the above copyright

# notice, this list of conditions and the following disclaimer.

# 2. Redistributions in binary form must reproduce the above copyright

# notice, this list of conditions and the following disclaimer in the

# documentation and/or other materials provided with the distribution.

#

# THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND

# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE

# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS

# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT

# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY

# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF

# SUCH DAMAGE.

#

# updatedb - update locate database for local mounted filesystems

#

# $FreeBSD: src/usr.bin/locate/locate/updatedb.sh,v 1.20 2005/11/12 12:45:08 grog Exp $

if [ "$(id -u)" = "0" ]; then

echo ">>> WARNING" 1>&2

echo ">>> Executing updatedb as root. This WILL reveal all filenames" 1>&2

echo ">>> on your machine to all login users, which is a security risk." 1>&2

fi

: ${LOCATE_CONFIG="/etc/locate.rc"}

if [ -f "$LOCATE_CONFIG" -a -r "$LOCATE_CONFIG" ]; then

. $LOCATE_CONFIG

fi

# The directory containing locate subprograms

: ${LIBEXECDIR:=/usr/libexec}; export LIBEXECDIR

: ${TMPDIR:=/tmp}; export TMPDIR

if ! TMPDIR=`mktemp -d $TMPDIR/locateXXXXXXXXXX`; then

exit 1

fi

PATH=$LIBEXECDIR:/bin:/usr/bin:$PATH; export PATH

: ${mklocatedb:=locate.mklocatedb} # make locate database program

: ${FCODES:=/var/db/locate.database} # the database

: ${SEARCHPATHS:="/"} # directories to be put in the database

: ${PRUNEPATHS:="/tmp /var/tmp */Backups.backupdb"} # unwanted directories

: ${FILESYSTEMS:="hfs ufs"} # allowed filesystems

: ${find:=find}

case X"$SEARCHPATHS" in

X) echo "$0: empty variable SEARCHPATHS"; exit 1;; esac

case X"$FILESYSTEMS" in

X) echo "$0: empty variable FILESYSTEMS"; exit 1;; esac

# Make a list a paths to exclude in the locate run

excludes="! (" or=""

for fstype in $FILESYSTEMS

do

excludes="$excludes $or -fstype $fstype"

or="-or"

done

excludes="$excludes ) -prune"

case X"$PRUNEPATHS" in

X) ;;

*) for path in $PRUNEPATHS

do

excludes="$excludes -or -path $path -prune"

done;;

esac

tmp=$TMPDIR/_updatedb$$

trap 'rm -f $tmp; rmdir $TMPDIR; exit' 0 1 2 3 5 10 15

# search locally

# echo $find $SEARCHPATHS $excludes -or -print && exit

if $find -s $SEARCHPATHS $excludes -or -print 2>/dev/null |

$mklocatedb -presort > $tmp

then

case X"`$find $tmp -size -257c -print`" in

X) cat $tmp > $FCODES;;

*) echo "updatedb: locate database $tmp is empty"

exit 1

esac

fi

Nice thnx, could be helpful one day,

BTW, did you get the DigiNotar root certificates pulled on your 10.5/10.4 box(s) by Apple update or did they just ignore you?

Sorry, I'm not familiar with the DigiNotar stuff.

Keychain Access > System Roots > DigiNotar ?

All I want to know is if Apple provided a update for 10.5 or not and pulled it, I cant' boot off my old 10.5 disk to find out myself. 🙂

According to what I've read only 10.6/10.7 was the violated certificates pulled, I've been telling people Apple hasn't updated the 10.5 certificates to get them to upgrade to 10.6 as I'm thinking it's a security issue. Wondering if I was correct in what I read or not about it as I cant' find the article about the update if it included 10.5 or not.

https://en.wikipedia.org/wiki/DigiNotar

The one on my G-4's Leopard volume has a 31 Mar '25 expiration date. There's none on my SL or Lion volumes. Is that sufficient info?

baltwo wrote:

The one on my G-4's Leopard volume has a 31 Mar '25 expiration date. There's none on my SL or Lion volumes. Is that sufficient info?

Guess what I read was right then.

Thanks. 🙂

Ah, yes here it is, right in front of my nose:

On September 9, 2011, Apple issued Security Update 2011-005 for Mac OS X 10.6.8 and 10.7.1, which removes DigiNotar from the list of trusted root certificates and EV certificate authorities. ^[27] Without this update, Safari and Mac OS X do not detect the certificate's revocation, and users must use the Keychain utility to manually delete the certificate.

Well now we both know. 🙂