public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Terje Kvernes <terjekv@math.uio.no>
To: Stefan Jones <cretin@gentoo.org>
Cc: gentoo-dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Announcing new Prelinking Guide
Date: 04 Jan 2003 23:18:49 +0100	[thread overview]
Message-ID: <wxx4r8opnhy.fsf@nommo.uio.no> (raw)
In-Reply-To: <1041691556.1454.27.camel@localhost>

Stefan Jones <cretin@gentoo.org> writes:

> On Fri, 2003-01-03 at 19:21, Terje Kvernes wrote:
>
> > I'm getting a lot of segfaults when I try to undo prelink.  any
> > suggestions to save me from rebuilding pretty much everything?
> > I'm not sure how to find broken libraries even, so I'm just
> > emergeing stuff that is broken when I find it to be so.
> 
> Lots of problems here. 

  ouch.  you have my sympathy.  thanks for testing, I hope you did so
  with careful planning?  :-)

> It seems that because of the disk space shortage some libraries must
> of got corrupted and thus are unfixable, they probably got
> truncated.

  good point.  I thought that should be easy enough to check so I
  created a small logical volume directory for testing.  I then ran
  prelink -v /mnt/prelink/*.so, and even if the partition was 100%
  full it ran okay.  well, seemingly at least.  nothing ended up as
  "data".  I wonder what libraries cause massive space usage?
 
> How much was the amount of space used up by prelink, details, so I
> can update my howto, for I think as you say, that was the source of
> the errors.

  I noticed the space on /usr having 50MiB free at one point, and
  dropping down to around 10MiB when I reran "prelink -u".  I'd say
  that 100MiB should be plenty, and probably give us a bit of
  headspace as well.  I'll try to reproduce the events under
  controlled circumstances.  

  anyhow, since /etc/prelink.conf contains all the stuff that can be
  broken, this find everything that is broken, and then some:

for build in $(
  for broken in $(
    for dir in $( grep -v '#' /etc/prelink.conf | cut -f2 -d' ' );
      do
       file $dir/* | grep ":.*data";
    done | cut -f1 -d: );
    do     
     qpkg -v -nc -f $broken;
  done | sort | uniq );
do echo "=$build"; done
  
  produces a nice list to feed emerge:

=dev-util/guile-1.4-r3
=gnome-base/gnome-panel-1.4.1
=kde-base/kdebase-3.0.5a
=kde-base/kdelibs-3.0.5a
=kde-base/kdemultimedia-3.0.5a
=media-video/transcode-0.6.0
=media-video/xawtv-3.80
=net-print/cups-1.1.18
=sys-libs/cracklib-2.7-r6
=sys-libs/db-1.85-r1
=x11-libs/qt-3.1.0-r1

  emerge $( for ... ) works as it should, and grabs the proper
  versions.

  the only false positive I find comes from /usr/lib/cracklib_dict.hwm
  and will require a remerge of cracklib, which isn't that bad.  one
  can of course just grep that away, if you know it's clean.  there is
  also the issue that ORBit2 required me to delete the broken
  libraries by hand, and also that packages have to be built in the
  correct order.  building kdelibs with a broken kdebase doesn't quite
  work.  but, at least the above script should ease ones pain.
  
-- 
Terje

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-01-04 22:20 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 [this message]
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
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=wxx4r8opnhy.fsf@nommo.uio.no \
    --to=terjekv@math.uio.no \
    --cc=cretin@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