The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
vmware-server-kernel-modules-2.6.22 task.
** Changed in: vmware-server-kernel-modules-2.6.22 (Ubuntu)
Status: Confirmed => Won't Fix
cancel that, I found a tutorial that was simple and easy to follow. I
now have vmware-server 1.0.7 installed and functioning on 8.0.4
--
No vmnet module for -386er Kernel
https://bugs.launchpad.net/bugs/185415
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
chris,
I think I do not know enough about linux..the script above produces errors
when I run it, it can't find vmware-server-kernel-modules or
build-essentials... however I believe build-essentials is already installed,
there are other errors as follows :
[EMAIL PROTECTED]:~$ sudo bash
[EM
Hi Gene,
the script builds and installs a personal deb package from the source
for you.
Regards,
Chris
Gene Caldwell wrote:
> I'm sorry, I don't see how this is a work around... I still do not see
> any vmware packages in the repros. how does this work around add them to
> the package manager
I'm sorry, I don't see how this is a work around... I still do not see
any vmware packages in the repros. how does this work around add them to
the package manager so that they can be installed ? I thought the
sources.list was responsible for adding new repros to synaptic ?
--
No vmnet module for
Here is the Workaround:
#!/bin/sh
aptitude install vmware-server-kernel-modules build-essentials
export TMPDIR=`mktemp -d`
mkdir -p $TMPDIR
cd $TMPDIR
tar xvjf /usr/src/vmware-server.tar.bz2
cd modules/vmware-server-kernel/
export KPKG_DEST_DIR=/root/deb/ # otherwise fakeroot won't work
mkdir $K
with the new vmware server version 1.0.6, the any-any update is no
longer needed, so when will we see vmware returned to the repros ? I
have searched and searched and find nothing about when we can expect
anything at all in the partners repro. Can we get some kind of comment
from ubuntu or a dev th
There are still no vmnet modules for the -386 kernel. So vmware is not
usable at systems with a -386er kernel.
--
No vmnet module for -386er Kernel
https://bugs.launchpad.net/bugs/185415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I should correct myself: each of the first three machines were using
their kernel versions' "generic".
--
No vmnet module for -386er Kernel
https://bugs.launchpad.net/bugs/185415
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Changed in: vmware-server-kernel-modules-2.6.22 (Ubuntu)
Status: New => Confirmed
--
No vmnet module for -386er Kernel
https://bugs.launchpad.net/bugs/185415
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
I tested vmware-server on three different machines, and it worked fine,
then on a fourth, this problem. Turns out the first three machines were
2.6.22-14-generic, and the fourth one was 2.6.22-14-386.
--
No vmnet module for -386er Kernel
https://bugs.launchpad.net/bugs/185415
You received this b
11 matches
Mail list logo
