On 26/04/2013 18:54, Jarry wrote:
> On 26-Apr-13 18:41, Alan McKinnon wrote:
>> On 26/04/2013 18:37, Jarry wrote:
>>> On 26-Apr-13 18:11, Tanstaafl wrote:
>>>> compile fails with lots of
>>>>
>>>> "...error "No Module support in this kernel. Please configure with
>>>> CONFIG_MODULES"
>>>>
>>>> Please tell me that I'm not going to have to enable modules just so I
>>>> can use the vmware tools??
>>>
>>> Yes you are. If you want to use vm-tools ("open" or "vmware"),
>>> you have to enable kernel modules. And also some strange options
>>> (i.e. vmware-graphics). And as I told you previously, updating
>>> to new kernel is really pain in a**. That's why I got rid of
>>> the whole vm-stuff and I'm happy without it...
>>
>> Are you aware of "module-rebuild rebuild"?
> 
> Yes I am. Believe me or not, but this did not work.
> 
>> Nice little scriplet that reduces all that pain to running one single
>> command after installing a new built kernel.
> 
> I mean there is a problem with new kernel version. Not sure
> but I suppose open-vm-tools sources are installed into kernel
> sources tree. And if you install new kernel, open-vm-tools
> sources are not moved to the new kernel-sources tree.
> Whenever I installed new kernel-sources and re-created link
> /usr/src/linux pointing to the new sources, I had to re-emerge
> open-vm-tools too...

I don't use open-vm-tools so I don't know how they work. I do know
vmware and virtualbox's stuff though - basically the same as any
out-of-tree module package. The ebuild takes care of the nitty-gritty
and builds the modules against whatever /usr/src/linux points to. Is
open-vm-tools the same?

Deploying a new kernel version is a complex affair anyway. You have to
configure the thing, carefully look out for new and changed config
options, run FOUR make commands, edit grub.conf and do a lot of testing.
Now you have to add one extra tiny little command to the end. It's one
little bullet point in your process.

Surely you can't be claiming that is a huge problem for you?


-- 
Alan McKinnon
alan.mckin...@gmail.com


Reply via email to