[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKS9Q2yJ7pX727WidPCHh2euQyEepRt+rDbPQBgtpdCs=KdyAQ@mail.gmail.com>
Date: Mon, 14 Nov 2011 11:06:46 +0400
From: misha shiposh <netsferato@...il.com>
To: owl-users@...ts.openwall.com
Subject: Re: VMWare tools
On Mon, Nov 14, 2011 at 9:31 AM, (GalaxyMaster) <galaxy@...nwall.com> wrote:
> On Sat, Nov 12, 2011 at 08:48:15PM +0400, misha shiposh wrote:
>> In any case we need to rebuild kernel.
>
> Why do one need this? VMware modules can be compiled and loaded into
> the currently running kernel with no issues. Just follow the official
> VMware procedure in regard to adding their modules into the running
> kernel. Well, you may need to tweak their Makefile a bit to specify the
> proper location of the kernel sources.
Anywhere it's not so easy as i expected...
We have about 5 or 8 owl in our product virtualization, and as a
result i must do this steps on each machine. I just thought that there
are anothe way without having to build kernel or modules for
installing tools.
Thanks for your answer.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
