SEO

#1 (**permalink**) 02-21-2008, 09:10 AM

I goofed......did a emerge depclean, and out went libattr and libacl. Now
the system won't boot. Google offers a couple of solutions;

1)
USE="-acl" emerge coreutils && revdep-rebuild

2)
Copy liattr* and libacl* files, from Gentoo liveCD, into /lib.

I wanted to try out 1, but can't seem to add a '=' sign.......how do I do
that??

I've tried 2, and had no succes....it says upon boot "libacl.so.1 too
short", meaning I have not copied the right libacl.so.1. But where do I find
the right one then?. I run a fully up2date Gentoo system, on vanilla-2.6.10
kernel.

Tips are greatly appreciated ;o)

/Stig

#2 (**permalink**) 02-21-2008, 09:11 AM

Stig Mogensen wrote:
> I goofed......did a emerge depclean, and out went libattr and libacl.
welcome to the club :-)
did the same stupid thing half a year ago and lost my libacl, too.

> I've tried 2, and had no succes....
is the *.so symlinked to *.so.1?
did u symlink /usr/lib/blah to /lib/blah, too?

see my symlinks here ..

matt@gentoo:/usr/lib> ls -al libattr.so
lrwxrwxrwx 1 root root 15 Nov 13 16:54 libattr.so -> /lib/libattr.so
matt@gentoo:/usr/lib> ls -al libacl.so
lrwxrwxrwx 1 root root 14 Nov 13 16:55 libacl.so -> /lib/libacl.so
matt@gentoo:/usr/lib> cd /lib/
matt@gentoo:/lib> ls -al libacl.so
lrwxrwxrwx 1 root root 11 Nov 13 16:55 libacl.so -> libacl.so.1
matt@gentoo:/lib> ls -al libattr.so
lrwxrwxrwx 1 root root 12 Nov 13 16:54 libattr.so -> libattr.so.1

just relink ev'rything and yr gentoo should be fine.

HTH
Matt

#3 (**permalink**) 02-21-2008, 09:11 AM

> > I goofed......did a emerge depclean, and out went libattr and libacl.
> welcome to the club :-)
> did the same stupid thing half a year ago and lost my libacl, too.

Thank you very much for your post.

I guess some of us, learn the hard way ;o)

> just relink ev'rything and yr gentoo should be fine.

Seems to work, to the extend that I know get a different errormessage.

Now the system seems to think it needs libstdc++.so.6 to boot. I ran
"emerge -s stdc", and all it found was a masked package, that wasn't even
installed??.

/Stig

#4 (**permalink**) 02-21-2008, 09:11 AM

Now the system seems to think it needs libstdc++.so.6 to boot. I ran
> "emerge -s stdc", and all it found was a masked package, that wasn't even
> installed??.

Can I just run;

ACCEPT_KEYWORDS="~x86" emerge libstdc++-v3

and then expect the system to boot??. It should be pretty straightforward to
remove that again, after the system is up and running again?.

/Stig

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

libacl.so.1 missing