walt wrote: > On Tue, 18 Aug 2015 15:52:53 -0400 > Alan Grimes <alonz...@verizon.net> wrote: > >> Like a stupid dumbfuck, I tried to update my machine today.... >> >> tortoise ~ # revdep-rebuild >> /bin/bash: error while loading shared libraries: libtinfo.so.5: cannot >> open shared object file: No such file or directory >> tortoise ~ # ufed >> sh: error while loading shared libraries: libtinfo.so.5: cannot open >> shared object file: No such file or directory >> sh: error while loading shared libraries: libtinfo.so.5: cannot open >> shared object file: No such file or directory >> sh: error while loading shared libraries: libtinfo.so.5: cannot open >> shared object file: No such file or directory >> sh: error while loading shared libraries: libtinfo.so.5: cannot open >> shared object file: No such file or directory >> sh: error while loading shared libraries: libtinfo.so.5: cannot open >> shared object file: No such file or directory >> sh: error while loading shared libraries: libtinfo.so.5: cannot open >> shared object file: No such file or directory >> >> Couldn't determine EPREFIX and PORTDIR from Portage >> INIT failed--call queue aborted. >> tortoise ~ # >> >> !!!! >> >> GOOD JOB, PENGUINS!!! >> I won't even be able to reboot my machine!!! > In addition to the suggestions already made by other posters, it's good > to keep busybox in mind. Depending on how you boot your machine, there > is usually a way you can pass 'init=/bin/bb' to the kernel at boot time. > > You can do wonderful stuff with busybox when you're in a bind. > >
And for the future, this could be very handy. FEATURES="buildpkg" That goes in or added to the current line in make.conf. That little thing has saved my bacon more than once. Dale :-) :-)
