[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111114114350.GA4901@openwall.com>
Date: Mon, 14 Nov 2011 15:43:50 +0400
From: Solar Designer <solar@...nwall.com>
To: owl-users@...ts.openwall.com
Subject: Re: VMWare tools
Misha, Galaxy -
On Mon, Nov 14, 2011 at 11:06:46AM +0400, misha shiposh wrote:
> On Mon, Nov 14, 2011 at 9:31 AM, (GalaxyMaster) <galaxy@...nwall.com> wrote:
> > ... 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.
It sounds like the two of you could write some tutorials (such as on our
wiki) based on your experience with this. Then maybe others in here
would be able to propose how to simplify them. I am totally unfamiliar
with VMware, so I can't help right now, but having seen the exact steps
that you have to take on each machine now I might be able to suggest
something or we might even make relevant changes to Owl itself (e.g.,
reducing the number of customization steps needed for VMware tools).
Thanks,
Alexander
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.
