| 1 |
Am 29.05.2011 23:59, schrieb Alan McKinnon: |
| 2 |
> Apparently, though unproven, at 23:50 on Sunday 29 May 2011, Nicolai Beuermann |
| 3 |
> did opine thusly: |
| 4 |
> |
| 5 |
>> Hi, |
| 6 |
>> after updating to virtualbox-4.0.8 I cannot start a vm anymore. |
| 7 |
>> |
| 8 |
>> The following ebuilds are installed: |
| 9 |
>> app-emulation/virtualbox-4.0.8 |
| 10 |
>> app-emulation/virtualbox-additions-4.0.8 |
| 11 |
>> app-emulation/virtualbox-extpack-oracle-4.0.8 |
| 12 |
>> app-emulation/virtualbox-modules-4.0.8 |
| 13 |
>> |
| 14 |
>> The logs mention that symlinks are not permitted. /usr/lib64 is a |
| 15 |
>> symlink to /usr/lib on my system. |
| 16 |
> |
| 17 |
> Switch it to be the other way round which is how it should be. It works |
| 18 |
> perfectly here with the exact same packages: |
| 19 |
> |
| 20 |
> $ ls -al /usr/ |
| 21 |
> lrwxrwxrwx 1 root root 5 Oct 27 2010 lib -> lib64 |
| 22 |
Now it works. |
| 23 |
|
| 24 |
One question remains unanswered and that is how this wrong symbolic link |
| 25 |
was created??? By portage? |
| 26 |
|
| 27 |
> |
| 28 |
>> Please help. I don't have an idea. |
| 29 |
>> |
| 30 |
>> Nico |
| 31 |
> |
| 32 |
Thank you very much. |
| 33 |
Regards |
| 34 |
Nico |
Archives