public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bart Lauwers <blauwers@gentoo.org>
To: gentoo-dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Announcing new Prelinking Guide
Date: Sun, 5 Jan 2003 16:17:03 +0100	[thread overview]
Message-ID: <200301051617.03191.blauwers@gentoo.org> (raw)
In-Reply-To: <1041777696.1422.32.camel@localhost>

> 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, 
followed by a reboot and prelink -a. reboot. (with an occasional tendency to 
break things.)

 I've been wondering about the impact on portage however. Will portage know to 
unmerge these prelinked binaries still? My guess would be no.

 General remark: Prelinking definitely promises to be great but unless your 
willing to deal with some 'early adoption' quirks it isn't for you yet. I've 
broken my system once or twice severely trying to gauge it's state. I would 
say that some challenges remain before it is ready for the masses.


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-01-05 15:19 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03  1:27 [gentoo-dev] Announcing new Prelinking Guide John P. Davis
2003-01-03  8:06 ` Terje Kvernes
2003-01-03  8:25   ` Terje Kvernes
2003-01-03  9:22     ` Stefan Jones
2003-01-03 16:52       ` Terje Kvernes
2003-01-03 19:21       ` Terje Kvernes
2003-01-03 20:54         ` Terje Kvernes
2003-01-04 15:55           ` Stefan Jones
2003-01-04 21:36             ` Terje Kvernes
2003-01-04 14:45         ` Stefan Jones
2003-01-04 22:18           ` Terje Kvernes
2003-01-04 23:11             ` Bart Verwilst
2003-01-04 23:24               ` William Kenworthy
2003-01-05 16:19                 ` Paul de Vrieze
2003-01-05  0:10               ` Terje Kvernes
2003-01-03 13:57   ` John P. Davis
2003-01-03 17:23     ` Terje Kvernes
2003-01-03 18:47       ` Toby Dickenson
2003-01-03 19:05         ` Terje Kvernes
2003-01-03 16:11 ` Paul de Vrieze
2003-01-05  1:09 ` Caleb Shay
2003-01-05  3:12   ` Terje Kvernes
2003-01-05  3:52     ` Caleb Shay
2003-01-05  4:39       ` Caleb Shay
2003-01-05  5:27         ` Terje Kvernes
2003-01-05  6:23           ` Caleb Shay
2003-01-05  7:13             ` Terje Kvernes
2003-01-05  8:01               ` Caleb Shay
2003-01-05 13:20                 ` Stefan Jones
2003-01-05 14:30                   ` Werner Van Belle
2003-01-05 14:41                     ` Stefan Jones
2003-01-05 15:10                       ` Dewet Diener
2003-01-05 15:17                       ` Bart Lauwers [this message]
2003-01-05 15:29                         ` Stefan Jones
2003-01-05 14:36         ` Dewet Diener
2003-01-05  5:25       ` Terje Kvernes
2003-01-07  4:02 ` Spider
2003-01-07  7:01   ` Viktor Lakics
2003-01-08 18:49     ` Stefan Jones

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200301051617.03191.blauwers@gentoo.org \
    --to=blauwers@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox