| 1 |
Apparently, though unproven, at 17:38 on Monday 02 May 2011, Davide Carnovale |
| 2 |
did opine thusly: |
| 3 |
|
| 4 |
> Hi all! |
| 5 |
> i was going through a world update today and during --depclean emerge throw |
| 6 |
> an error complaining about possible corrupted binaries or hw failure. |
| 7 |
> since then it has stopped working, no matter what i try to emerge, the |
| 8 |
> command simply return to the shell without any kind of error or any other |
| 9 |
> output at all. |
| 10 |
> i fired and usb stick with the gentoo 11 live dvd and i copied over both |
| 11 |
> bash and emerge binaries to my machine, in case they were corrupted (bash |
| 12 |
> was given as the most likely) but nothing changed. |
| 13 |
> now i simply have no clue on what's wrong and how can i fix it, apart from |
| 14 |
> a full reinstall, which i'd like to avoid. |
| 15 |
> |
| 16 |
> can anyone point me somewhere to solve this problem? |
| 17 |
|
| 18 |
Unless you can post some real error messages it's going to be very difficult |
| 19 |
to help you - there can be many causes for a failure such as that. Start with |
| 20 |
the usual: |
| 21 |
|
| 22 |
- go through any relevant logs looking for related entries then post them |
| 23 |
- do an fsck on your filesystems |
| 24 |
- anything useful returned by revdep-rebuild? |
| 25 |
|
| 26 |
Copying over scripts is unlikely to achieve much. bash is not actually related |
| 27 |
after emerge launches and emerge itself is a python script - the guts of the |
| 28 |
work is done elsewhere. In fact you might have done more harm than good as the |
| 29 |
emerge script version now does not match everything else installed by the |
| 30 |
portage ebuild. |
| 31 |
|
| 32 |
You will probably need to remerge portage from a live CD environment as step |
| 33 |
1. |
| 34 |
|
| 35 |
|
| 36 |
|
| 37 |
|
| 38 |
-- |
| 39 |
alan dot mckinnon at gmail dot com |
Archives