背景：用vmware workstation 6.0 安装的是带xwindow的debian
(1)检查有没有安装gcc
可以通过which gcc或者whereis gcc查看。发现已安装
(2)安装内核头文件
内核头文件默认是会安装到/usr/src目录下。ls /usr/src查看发现目录为空，即没有安装。
hohoer@debian:~$ ls /cdrom
hohoer@debian:~$ mount /cdrom
mount: block device /dev/hdc is write-protected, mounting read-only
hohoer@debian:~$ ls /cdrom
autorun.bat dists isolinux pool README.mirrors.txt
autorun.inf doc md5sum.txt README.html README.txt
debian install pics README.mirrors.html tools
hohoer@debian:~$ uname -a
Linux debian 2.6.17-2-686 #1 SMP Wed Sep 13 16:34:10 UTC 2006 i686 GNU/Linux
hohoer@debian:~$ apt-cache search headers 2.6.17-2-686
linux-headers-2.6.17-2-686 - Header files for Linux 2.6.17 on PPro/Celeron/PII/P III/P4
hohoer@debian:~$ su
Password:
debian:/home/hohoer# apt-get install linux-headers-2.6.17-2-686
debian:/home/hohoer# ls /usr/src/
linux-headers-2.6.17-2 linux-headers-2.6.17-2-686 linux-kbuild-2.6.17
debian:/home/hohoer# ls /usr/src/linux-headers-2.6.17-2-686/
arch crypto fs init kernel Makefile Module.symvers scripts sound
block drivers include ipc lib mm net security usr
debian:/home/hohoer# ls /usr/src/linux-headers-2.6.17-2-686/include/
acpi asm asm-generic asm-i386 config keys linux math-emu media mtd net pcmcia rdma rxrpc scsi sound video
(3)开始安装vmware tools
从debian切出进windows，摁ctrl＋alt
反之，直接鼠标点debian界面就行了
菜单VM-install vmware tools
su到超级用户
#umount /cdrom
#unount /mnt
#mount -t iso9660 /dev/cdrom /mnt/
#ls /mnt
会看到有Vmwaretools的.rpm和.tar.gz的包
#cp /mnt/VMwaretools*.tar.gz /tmp/
#umount /dev/cdrom
#cd /tmp
/tmp#tar zxf Vmware*.tar.gz
/tmp#cd vmware-tools-distrib
/tmp#./vmware-install.pl
hohoer@debian:~$ cd /tmp/
hohoer@debian:/tmp$ ls
gconfd-hohoer orbit-hohoer VMwareTools-6.0.0-45731.tar.gz
gconfd-root orbit-root vmware-tools-distrib
keyring-UswtGY ssh-nvBKRA3909
mapping-hohoer virtual-hohoer.PdkSVF
hohoer@debian:/tmp$ cd vmware-tools-distrib/
hohoer@debian:/tmp/vmware-tools-distrib$ ls
bin doc etc FILES INSTALL installer lib vmware-install.pl
hohoer@debian:/tmp/vmware-tools-distrib$ ./vmware-install.pl
Please re-run this program as the super user.
Execution aborted.
hohoer@debian:/tmp/vmware-tools-distrib$ su
Password:
debian:/tmp/vmware-tools-distrib# ./vmware-install.pl
A previous installation of VMware Tools has been detected.
The previous installation was made by the tar installer (version 4).
Keeping the tar4 installer database format.
Uninstalling the tar installation of VMware Tools.
Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: done
The removal of VMware Tools 6.0.0 build-45731 for Linux completed successfully.
Thank you for having tried this software.
Installing VMware Tools. This may take from several minutes to over an hour
depending upon its size.
In which directory do you want to install the binary files?
[/usr/bin]
What is the directory that contains the init directories (rc0.d/ to rc6.d/)?
[/etc]
What is the directory that contains the init scripts?
[/etc/init.d]
In which directory do you want to install the daemon files?
[/usr/sbin]
In which directory do you want to install the library files?
[/usr/lib/vmware-tools]
The path "/usr/lib/vmware-tools" does not exist currently. This program is
going to create it, including needed parent directories. Is this what you want?
[yes]
In which directory do you want to install the documentation files?
[/usr/share/doc/vmware-tools]
The path "/usr/share/doc/vmware-tools" does not exist currently. This program
is going to create it, including needed parent directories. Is this what you
want? [yes]
The installation of VMware Tools 6.0.0 build-45731 for Linux completed
successfully. You can decide to remove this software from your system at any
time by invoking the following command: "/usr/bin/vmware-uninstall-tools.pl".
Before running VMware Tools for the first time, you need to configure it by
invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want
this program to invoke the command for you now? [yes] no
Enjoy,
--the VMware team
debian:/tmp/vmware-tools-distrib# /usr/bin/vmware-config-tools.pl
Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: done
Trying to find a suitable vmmemctl module for your running kernel.
None of the pre-built vmmemctl modules for VMware Tools is suitable for your
running kernel. Do you want this program to try to build the vmmemctl module
for your system (you need to have a C compiler installed on your system)?
[yes]
Using compiler "/usr/bin/gcc". Use environment variable CC to override.
What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/include]
The path "/usr/src/linux/include" is not an existing directory.
What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/include] /usr/src/linux-headers-2.6.17-2-686/include 【注意这里！】
Extracting the sources of the vmmemctl module.
Building the vmmemctl module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmemctl-only'
make -C /usr/src/linux-headers-2.6.17-2-686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.17-2-686'
CC [M] /tmp/vmware-config0/vmmemctl-only/os.o
SHIPPED /tmp/vmware-config0/vmmemctl-only/vmmemctl1.o
LD [M] /tmp/vmware-config0/vmmemctl-only/vmmemctl.o
Building modules, stage 2.
MODPOST
CC /tmp/vmware-config0/vmmemctl-only/vmmemctl.mod.o
LD [M] /tmp/vmware-config0/vmmemctl-only/vmmemctl.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.17-2-686'
cp -f vmmemctl.ko ./../vmmemctl.o
make: Leaving directory `/tmp/vmware-config0/vmmemctl-only'
The module loads perfectly in the running kernel.
Extracting the sources of the vmhgfs module.
Building the vmhgfs module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmhgfs-only'
make -C /usr/src/linux-headers-2.6.17-2-686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.17-2-686'
CC [M] /tmp/vmware-config0/vmhgfs-only/backdoor.o
CC [M] /tmp/vmware-config0/vmhgfs-only/backdoorGcc32.o
CC [M] /tmp/vmware-config0/vmhgfs-only/bdhandler.o
CC [M] /tmp/vmware-config0/vmhgfs-only/cpName.o
CC [M] /tmp/vmware-config0/vmhgfs-only/cpNameLinux.o
CC [M] /tmp/vmware-config0/vmhgfs-only/cpNameLite.o
CC [M] /tmp/vmware-config0/vmhgfs-only/dbllnklst.o
CC [M] /tmp/vmware-config0/vmhgfs-only/dentry.o
CC [M] /tmp/vmware-config0/vmhgfs-only/dir.o
CC [M] /tmp/vmware-config0/vmhgfs-only/eventManager.o
CC [M] /tmp/vmware-config0/vmhgfs-only/file.o
CC [M] /tmp/vmware-config0/vmhgfs-only/filesystem.o
CC [M] /tmp/vmware-config0/vmhgfs-only/fsutil.o
CC [M] /tmp/vmware-config0/vmhgfs-only/hgfsBd.o
CC [M] /tmp/vmware-config0/vmhgfs-only/hgfsUtil.o
CC [M] /tmp/vmware-config0/vmhgfs-only/inode.o
CC [M] /tmp/vmware-config0/vmhgfs-only/kernelStubsLinux.o
CC [M] /tmp/vmware-config0/vmhgfs-only/link.o
CC [M] /tmp/vmware-config0/vmhgfs-only/message.o
CC [M] /tmp/vmware-config0/vmhgfs-only/module.o
CC [M] /tmp/vmware-config0/vmhgfs-only/page.o
CC [M] /tmp/vmware-config0/vmhgfs-only/request.o
CC [M] /tmp/vmware-config0/vmhgfs-only/rpcin.o
CC [M] /tmp/vmware-config0/vmhgfs-only/rpcout.o
CC [M] /tmp/vmware-config0/vmhgfs-only/staticEscape.o
CC [M] /tmp/vmware-config0/vmhgfs-only/stubs.o
CC [M] /tmp/vmware-config0/vmhgfs-only/super.o
LD [M] /tmp/vmware-config0/vmhgfs-only/vmhgfs.o
Building modules, stage 2.
MODPOST
CC /tmp/vmware-config0/vmhgfs-only/vmhgfs.mod.o
LD [M] /tmp/vmware-config0/vmhgfs-only/vmhgfs.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.17-2-686'
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory `/tmp/vmware-config0/vmhgfs-only'
The module loads perfectly in the running kernel.
pcnet32 28420 0
Unloading pcnet32 module
Extracting the sources of the vmxnet module.
Building the vmxnet module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmxnet-only'
make -C /usr/src/linux-headers-2.6.17-2-686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.17-2-686'
CC [M] /tmp/vmware-config0/vmxnet-only/vmxnet.o
Building modules, stage 2.
MODPOST
CC /tmp/vmware-config0/vmxnet-only/vmxnet.mod.o
LD [M] /tmp/vmware-config0/vmxnet-only/vmxnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.17-2-686'
cp -f vmxnet.ko ./../vmxnet.o
make: Leaving directory `/tmp/vmware-config0/vmxnet-only'
The module loads perfectly in the running kernel.
Extracting the sources of the vmblock module.
Building the vmblock module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmblock-only'
make -C /usr/src/linux-headers-2.6.17-2-686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.17-2-686'
CC [M] /tmp/vmware-config0/vmblock-only/linux/block.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/control.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/dbllnklst.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/dentry.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/file.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/filesystem.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/inode.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/module.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/stubs.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/super.o
LD [M] /tmp/vmware-config0/vmblock-only/vmblock.o
Building modules, stage 2.
MODPOST
CC /tmp/vmware-config0/vmblock-only/vmblock.mod.o
LD [M] /tmp/vmware-config0/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.17-2-686'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/vmware-config0/vmblock-only'
The module loads perfectly in the running kernel.
[EXPERIMENTAL] The Virtual Machine Communication Interface (VMCI) service
provides a new communication capability with the Host, primarily for
development at the moment. Would you like to enable this feature? [no] yes 【这个功能不知咋用，我选了yes试试】
Extracting the sources of the vmci module.
Building the vmci module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmci-only'
make -C /usr/src/linux-headers-2.6.17-2-686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.17-2-686'
CC [M] /tmp/vmware-config0/vmci-only/dbllnklst.o
CC [M] /tmp/vmware-config0/vmci-only/kernelStubsLinux.o
CC [M] /tmp/vmware-config0/vmci-only/vmciDatagram.o
CC [M] /tmp/vmware-config0/vmci-only/vmci_drv.o
CC [M] /tmp/vmware-config0/vmci-only/vmciProcess.o
CC [M] /tmp/vmware-config0/vmci-only/vmciResource.o
CC [M] /tmp/vmware-config0/vmci-only/vmciSharedMemory.o
CC [M] /tmp/vmware-config0/vmci-only/vmciTest.o
CC [M] /tmp/vmware-config0/vmci-only/vmciUtil.o
LD [M] /tmp/vmware-config0/vmci-only/vmci.o
Building modules, stage 2.
MODPOST
CC /tmp/vmware-config0/vmci-only/vmci.mod.o
LD [M] /tmp/vmware-config0/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.17-2-686'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-config0/vmci-only'
The module loads perfectly in the running kernel.
Detected X.org version 7.1.
Please choose one of the following display sizes that X will start with (1 -
15):
[1] "640x480"
[2]< "800x600"
[3] "1024x768"
[4] "1152x864"
[5] "1280x800"
[6] "1152x900"
[7] "1280x1024"
[8] "1376x1032"
[9] "1400x900"
[10] "1400x1050"
[11] "1440x900"
[12] "1680x1050"
[13] "1600x1200"
[14] "1920x1200"
[15] "2364x1773"
Please enter a number between 1 and 15:
[2] 3 【这里分辨率选择我选的3，默认是2】
X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: UNKNOWN
Current Operating System: Linux debian 2.6.17-2-686 #1 SMP Wed Sep 13 16:34:10 UTC 2006 i686
Build Date: 04 September 2007
Before reporting problems, check
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/vmware-config0/XF86ConfigLog.4879", Time: Mon Oct 1 09:32:46 2007
(++) Using config file: "/tmp/vmware-config0/XF86Config.4879"
(EE) Failed to load module "void" (module does not exist, 0)
X is running fine with the new config file.
(EE) AIGLX: Screen 0 is not DRI capable
(EE) No Input driver matching `void'
xkb_keycodes { include "xfree86+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compatibility { include "complete" };
xkb_symbols { include "pc(pc105)+us" };
xkb_geometry { include "pc(pc104)" };
FreeFontPath: FPE "/usr/share/fonts/X11/misc" refcount is 2, should be 1; fixing.
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: done
Guest filesystem driver: done
Mounting HGFS shares: failed
Guest memory manager: done
Guest vmxnet fast network device: done
New Host-Guest communications path: done
Blocking file system: done
DMA setup: done
Guest operating system daemon: done
The configuration of VMware Tools 6.0.0 build-45731 for Linux for this running
kernel completed successfully.
You must restart your X session before any mouse or graphics changes take
effect.
You can now run VMware Tools by invoking the following command:
"/usr/bin/vmware-toolbox" during an X server session.
To use the vmxnet driver, restart networking using the following commands:
/etc/init.d/networking stop
rmmod pcnet32
rmmod vmxnet
modprobe vmxnet
/etc/init.d/networking start
If you wish to configure any experimental features, please run the following
command: "vmware-config-tools.pl --experimental".
Enjoy,
--the VMware team 【成功了！庆国庆！】
debian:/tmp/vmware-tools-distrib#
阅读(4786) | 评论(0) | 转发(2) |
