Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!bywater!arnor!arnor!marc
From: marc@arnor.uucp
Newsgroups: comp.unix.aix
Subject: Re: LIBPATH (was Re: /usr/etd/biod 0 'is very bad for your health'
Message-ID: <MARC.90Nov16092655@marc.watson.ibm.com>
Date: 16 Nov 90 14:26:55 GMT
References: <12325@fsg.UUCP> <1028@casbah.acns.nwu.edu>
	<1990Nov14.215702.11117@panews>
Sender: news@arnor.uucp (NNTP News Poster)
Organization: IBM T.J. Watson Research Center, Hawthorne, New York
Lines: 30
In-Reply-To: jsalter@slo's message of 14 Nov 90 21:57:02 GMT

The safe way to test a new version of libc.a is to 

mount /whatever/libc.a /lib/libc.a

and see if it works.  This will cause all subsequent uses of libc.a
to be the new one BUT, if you crash and reboot you're back to the old
one.

The safe way to replace libc.a is:

cd /lib
cp libc.a libc.a.orig (if you don't already have a backup IN /lib
cp /whatever/libc.a libc.a.new
sync
mv libc.a.new libc.a

mv is atomic - you'll either have the new or the old even if you crash
right then and there.

It is possible to fix libc.a if you've trashed it.

boot from diskettes.

/etc/continue hdisk0 exit

which stops the start up before anything is mounted.

you can then mount /dev/hd4 someplace and restore libc.a.  (At that
point, there is a copy in /lib/libc.a (from the diskette) which will
work.)  Make sure the diskettes are at the same level as the machine.