From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10539 invoked by uid 1002); 5 Jan 2003 15:19:13 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 608 invoked from network); 5 Jan 2003 15:19:12 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Bart Lauwers To: gentoo-dev Date: Sun, 5 Jan 2003 16:17:03 +0100 User-Agent: KMail/1.4.3 References: <200301022027.08364.zhen@gentoo.org> <200301051530.23640.werner.van.belle@vub.ac.be> <1041777696.1422.32.camel@localhost> In-Reply-To: <1041777696.1422.32.camel@localhost> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200301051617.03191.blauwers@gentoo.org> Subject: Re: [gentoo-dev] Announcing new Prelinking Guide X-Archives-Salt: 91dc3b7b-5028-49e1-ab1b-910f491e1619 X-Archives-Hash: 2c5d8152a6836430043c87dea965f4a4 > I am not saying prelink isn't buggy BTW. > > The -f flag is needed if you have prelinked binaries already on the > system, otherwise it will abort, that is another matter..... > > If you use -f you get around that problem, but you then encounter the > other one, you are between a rock and a hard place it seems. I've found that the only way around the problem seems to be: prelink -ua= ,=20 followed by a reboot and prelink -a. reboot. (with an occasional tendency= to=20 break things.) I've been wondering about the impact on portage however. Will portage kn= ow to=20 unmerge these prelinked binaries still? My guess would be no. General remark: Prelinking definitely promises to be great but unless yo= ur=20 willing to deal with some 'early adoption' quirks it isn't for you yet. I= 've=20 broken my system once or twice severely trying to gauge it's state. I wou= ld=20 say that some challenges remain before it is ready for the masses. -- gentoo-dev@gentoo.org mailing list