Re: VMWare on current kernels

2007-02-06 Thread Freddy Freeloader
Greg Madden wrote: On Mon, 05 Feb 2007 23:15:00 -0200 Bruno Buys <[EMAIL PROTECTED]> wrote: Greg Folkert wrote: On Mon, 2007-02-05 at 20:38 +0100, Elimar Riesebieter wrote: On Mon, 05 Feb 2007 the mental interface of Jan Schledermann told: [...] A significant

Re: VMWare on current kernels

2007-02-05 Thread Greg Folkert
On Mon, 2007-02-05 at 18:10 -0900, Greg Madden wrote: > On Mon, 05 Feb 2007 23:15:00 -0200 > Bruno Buys <[EMAIL PROTECTED]> wrote: > > > Greg Folkert wrote: > > > On Mon, 2007-02-05 at 20:38 +0100, Elimar Riesebieter wrote: > > > > > >> On Mon, 05 Feb 2007 the mental interface of > > >> Jan Sch

Re: VMWare on current kernels

2007-02-05 Thread Greg Madden
On Mon, 05 Feb 2007 23:15:00 -0200 Bruno Buys <[EMAIL PROTECTED]> wrote: > Greg Folkert wrote: > > On Mon, 2007-02-05 at 20:38 +0100, Elimar Riesebieter wrote: > > > >> On Mon, 05 Feb 2007 the mental interface of > >> Jan Schledermann told: > >> > >> [...] > >> > >>> A significant differen

Re: VMWare on current kernels

2007-02-05 Thread Bruno Buys
Greg Folkert wrote: On Mon, 2007-02-05 at 20:38 +0100, Elimar Riesebieter wrote: On Mon, 05 Feb 2007 the mental interface of Jan Schledermann told: [...] A significant difference between the pre-compiled 2.6.18-1-686 kernel and the source code, is that the source code by default create

Re: VMWare on current kernels (was: debian rocks!)

2007-02-05 Thread Shobhit Jindal
some news myself just installed kernel 2.6.18-4-686 and vmware (vmware-config.pl) was configured without giving the error - no linux/version.h in /usr/src/include/linux not to mention 2.6.18-3-686 and 2.6.18-2-686 did give the error! On 2/5/07, Margarita Manterola <[EMAIL PROTECTED]> wrote: Hi

Re: VMWare on current kernels

2007-02-05 Thread Greg Folkert
On Mon, 2007-02-05 at 20:38 +0100, Elimar Riesebieter wrote: > On Mon, 05 Feb 2007 the mental interface of > Jan Schledermann told: > > [...] > > A significant difference between the pre-compiled 2.6.18-1-686 > > kernel and the source code, is that the source code by default > > creates version 2.

Re: VMWare on current kernels (was: debian rocks!)

2007-02-05 Thread Andrew Perrin
Take a look here: http://www.vmware.com/community/thread.jspa?messageID=76957&tstart=0 Essentially, vmware in its raw state doesn't compile with relatively newer kernels. You need patches to make them work. You can find these patches at http://platan.vc.cvut.cz/ftp/pub/vmware . Once you down

Re: VMWare on current kernels

2007-02-05 Thread Elimar Riesebieter
On Mon, 05 Feb 2007 the mental interface of Jan Schledermann told: [...] > A significant difference between the pre-compiled 2.6.18-1-686 > kernel and the source code, is that the source code by default > creates version 2.6.18 and NOT 2.6.18-1-686. This version > difference could cause the compil

Re: VMWare on current kernels (was: debian rocks!)

2007-02-05 Thread Jan Schledermann
Margarita Manterola wrote: > Hi! > > On 2/5/07, Shobhit Jindal <[EMAIL PROTECTED]> wrote: >> On 2/5/07, Bruno Buys <[EMAIL PROTECTED]> wrote: >> > The only >> > catch ins't debian related: vmware seems to not like my >> > /usr/src/include/linux, and asks for a new linux/version.h. >> >> i have b

Re: VMWare on current kernels (was: debian rocks!)

2007-02-05 Thread Bruno Buys
Margarita Manterola wrote: Hi! On 2/5/07, Shobhit Jindal <[EMAIL PROTECTED]> wrote: On 2/5/07, Bruno Buys <[EMAIL PROTECTED]> wrote: > The only > catch ins't debian related: vmware seems to not like my > /usr/src/include/linux, and asks for a new linux/version.h. i have been stuck to kernel 2