| 1 |
On Wed, Oct 19, 2011 at 2:05 PM, Stefan G. Weichinger <lists@×××××.at> wrote: |
| 2 |
> Am 14.10.2011 00:22, schrieb Stefan G. Weichinger: |
| 3 |
>> |
| 4 |
>> Anyone hitting the same issue? |
| 5 |
>> |
| 6 |
>> http://forums.gentoo.org/viewtopic-p-6824432.html?sid=ff31450ec4a661979b3545e662bdfbb1 |
| 7 |
>> |
| 8 |
>> AFAI understand glibc-2.13-r4 (as in ~amd64 right now) is too new |
| 9 |
>> for the vmware-binary? |
| 10 |
>> |
| 11 |
>> Did I understand correctly? |
| 12 |
>> |
| 13 |
>> Is there a workaround? Downgrading glibc is not the way to go, ey? |
| 14 |
>> ;-) |
| 15 |
> |
| 16 |
> So the answer is .... no? Or "noone" ;-) |
| 17 |
> |
| 18 |
> S |
| 19 |
|
| 20 |
I've decided to stick with vmware-player-3.1.4 for use as a Netflix VM |
| 21 |
only. All of my real work is done in Virtualbox VMs using both 32-bit |
| 22 |
NT and 64-bit Win 7. The only problem I've had recently is that my |
| 23 |
dual monitor Win 7 VM tends to 'abort' about 40% of the time when |
| 24 |
starting. Once it's up and running it's fine, but getting it started |
| 25 |
on any day is pretty much hit-or-miss. |
| 26 |
|
| 27 |
HTH, |
| 28 |
Mark |
Archives