I have run into the YP problem myself in the past. I am embarrassed to
say that I didn't file a bug report. As a work around, I changed
nsswitch.conf to remove the nis entries. I think there is a bug in one of
the nis libraries. Once I get past the upgrade, I restore the nis entries.
In normal operation I don't seem to have any more YP related problems.
--
Steve Herber [EMAIL PROTECTED] work: 206-221-7262
Security Engineer, UW Medicine, IT Services home: 425-454-2399
On Tue, 29 Mar 2005, Andreas Vinsander wrote:
> Hi!
>
> Started the installation of 64 bit gentoo yesterday (when I saw that
> 2005.0 was available)... everything went smooth, until I rebooted into
> my new shiny system.
>
> The tar command keeps segfaulting on me when bootin directly into the
> system. The same binary works flawlessly when chrooting from the livecd
> into the system.
>
> Running stable amd64 (with one exception see below)
> * Tried running memtest86+ for 3 hours without any errors
> * Tried kernel gentoo-sources-2.6.11-r4 (gentoo-sources-2.6.9-r14 seems
> a bit old?) but that didn't make tar work
> * Re-emerged glibc and tar (both from amd64 stable), still non-working tar
> * I haven't looked at the core file dumped by tar yet
>
> Now to what I did find out:
> * According to strace (strace dump attached) it seems like tar barely
> gets through loading some libs, bailing out when reaching yp stuff.
> Hmmm... I don't run ypbind when chrooting into the system from the
> livecd, but I do run it on the fully booted system. Might be something
> to investigate a bit more... Yep, turning off ypbind makes tar complete
> unpacking any tar-archive... strange... Re-emergeing ypbind doesn't help...
> What might be the reason for this? I have run out of clues...
>
> Here's my make.conf USE, CFLAGS and CHOST variables:
> USE="-gtk -gnome -ipv6 alsa cdr dvd dvdr jack kde nptl ntplonly qt"
> CFLAGS="-march=k8 -O2 -pipe"
> CXXFLAGS="${CFLAGS}"
> CHOST="x86_64-pc-linux-gnu"
>
>
> /Andreas
>
--
gentoo-amd64@gentoo.org mailing list
