Re: VMware on debian: module compilation

1999-09-06 Thread Manoj Srivastava
Hi, >>"Regis" == Regis Duchesne <[EMAIL PROTECTED]> writes: Regis> Thank you. My personal take on this is that these reasons were true Regis> with libc5 and they are not true anymore with libc6. What makes you think that? I see nothing, really, that has changed since the libc5 days tha

Re: VMware on debian: module compilation

1999-08-20 Thread Regis Duchesne
Brian Servis <[EMAIL PROTECTED]> writes: > Excellent, I can't wait. > > Is the install process truely dependent on the currently running kernel > matching the kernel headers that the user points to? Being able to > compile the modules for other kernels without having to reboot into > that kern

Re: VMware on debian: module compilation

1999-08-20 Thread Brian Servis
*- On 20 Aug, Regis Duchesne wrote about "Re: VMware on debian: module compilation" > is to know what to do with vmware. I will probably modify the install > script so that it prompts the user for the location of the running > kernel headers. > Excellent, I can't wait

Re: VMware on debian: module compilation

1999-08-20 Thread Regis Duchesne
Brian, > Thanks for taking the time to let us know that you are listening. You are welcome. That's what I like in companies with a Linux product: they are far more aware of their customer's needs. > I can only point you to documentation that explains the reasons for > Debian's choice. The first

Re: VMware on debian: module compilation

1999-08-20 Thread Brian Servis
Regis, Thanks for taking the time to let us know that you are listening. *- On 19 Aug, Regis Duchesne wrote about "VMware on debian: module compilation" > I'm the only software engineer here at VMware who uses (and has been using > for 3 years) Debian. If VMware in

VMware on debian: module compilation

1999-08-19 Thread Regis Duchesne
Hi guys, >Bob Nielsen wrote: >> >> On Sat, Aug 14, 1999 at 01:02:45AM +1000, Hamish Moffatt wrote: >> > On Fri, Aug 06, 1999 at 05:26:27AM +0300, Alex Shnitman wrote: >> > > You have to have the kernel source, or at least the headers part of >> > > it, in /usr/src/linux. Sometimes that's not enoug