| 1 |
On Sat, Feb 1, 2014 at 1:18 PM, Tanstaafl <tanstaafl@×××××××××××.org> wrote: |
| 2 |
> On 2014-02-01 10:45 AM, Daniel Frey <djqfrey@×××××.com> wrote: |
| 3 |
>> |
| 4 |
>> On 02/01/2014 07:13 AM, Tanstaafl wrote: |
| 5 |
>>> |
| 6 |
>>> I'm getting an error I start it, but it says it starts: |
| 7 |
>>> |
| 8 |
>>>> dinkumthinkum : Sat Feb 01, 09:52:46 : ~ |
| 9 |
>>>> # /etc/init.d/vmware-tools start |
| 10 |
>>>> * /tmp/VMwareDnD: correcting mode |
| 11 |
>>>> * /proc/fs/vmblock/mountPoint: creating directory |
| 12 |
>>>> * checkpath: mkdir: No such file or directory |
| 13 |
>>>> * Mounting vmblock ... |
| 14 |
>>>> mount: mount point /proc/fs/vmblock/mountPoint does not exist [ !! ] |
| 15 |
>>>> * Starting vmware-tools ... [ ok ] |
| 16 |
> |
| 17 |
> |
| 18 |
>> vmblock needs fuse enabled in the kernel. I'm not sure if it needs a |
| 19 |
>> module or not, I know my kernels use fuse as a module. |
| 20 |
>> |
| 21 |
>> If fuse is set in the kernel already, then app-emulation/open-vm-tools |
| 22 |
>> is not built with the 'fuse' USE flag. |
| 23 |
> |
| 24 |
> |
| 25 |
> Bingo - thanks Daniel. |
| 26 |
> |
| 27 |
> So... shouldn't this be considered a 'bug' then? If open-vm-tools requires |
| 28 |
> the fuse USE flag, it should be set by default. |
| 29 |
> |
| 30 |
|
| 31 |
It isn't needed if you don't use vmblock I guess. I just changed IUSE |
| 32 |
to enable it by default anyway. |
Archives