Install VMwareTools in Fedora 10

Issue: Cannot use share-folder after VMWareTools installed in Fedora 10.

After googling, found a solution from internet. With the following steps, the share-folder issue has been fixed. (My machine is WinXP-SP2 with v6.0.0 build-45731 VMware installed.)

1. Download open-vm-tools source from
"http://sourceforge.net/project/showfiles.php?group_id=204462&package_id=244023".
2. Do the compilation
# tar zxvf open-vm-tools-2009.02.18-148847.tar.gz
# cd open-vm-tools-2009.02.18-148847
# ./configure --disable-unity --without-gtkmm --without-dnet --without-icu
// Need --disable-unity --without-gtkmm --without-dnet --without-icu on my machine.
# make
3. Create needed tar files for VMwareTools.
# cd open-vm-tools-2009.02.18-148847/modules/linux
# for i in *; do mv ${i} ${i}-only; tar -cf ${i}.tar ${i}-only; done
// vmblock.tar, vmci.tar, vmhgfs.tar, vmmemctl.tar, vmsync.tar and vmxnet.tar will be created.
3. Untar VMwareTools-6.0.0-45731.tar.gz, the source is from VMware software itself.
4. Copy all tar files created by open-vm-tools to vmware-tools-distrib/lib/modules/source.
5. Run VMwareTools installation
# cd vmware-tools-distrib
# ./vmware-install.pl
6. Besides, "RgbPath" is not a valid keyword in /etc/X11/xorg.conf, "startx" cannot be activated due to the error. Please comment it from L:13 of /etc/X11/xorg.conf.

Reference:
http://diamondsw.dyndns.org/Home/Et_Cetera/Entries/2008/4/25_Linux_2.6.24_and_VMWare.html

Install Ser SIP server

Files needed:
ser-0.9.4_src.tar.gz
mysqld/mysqladmin
phpMyAdmin-2.6.4-pl3.tar.bz2

1. Compilation
# tar zxvf ser-0.9.4_src.tar.gz
# cd ser-0.9.4
# make
# make modules
# make install
// The default installed path is /usr/local/sbin.
// The configuration file will be placed under /usr/local/etc/ser.

2. Activate Ser service
# cp ser-0.9.4/rpm/ser.ini /etc/init.d/ser
# chkconfig ser reset
# chkconfig ser on
# service ser start

3. Activate and Configure MySQL
# chkconfig mysqld on
# service mysqld start
// Setup password for MySQL. (root/root)
# mysqladmin –u root password root
//Setup Ser database in MySQL：
# /usr/sbin/ser_mysql.sh create

4. Install phpMyAdmin to manage MySQL:
# tar jxvf phpMyAdmin-2.6.4-pl3.tar.bz2
# vi /etc/httpd/conf/httpd.conf
// Alias /php /home/phpMyAdmin-2.6.4-pl3
// Run http://IP-Address/php and use phpMyAdmin to modify permission and password of Ser service.

5. Add SIP users
# export SIP_DOMAIN=”porter10.mydomain.intra” serctl add
# /usr/local/sbin/serctl add 230 230 230@192.168.1.1
# /usr/local/sbin/serctl add 232 232 232@192.168.1.1

Booting from CF card

Using CF card or micro hardisk to construct a simple embedded system:

1. Format CF card (The CF card is connected to Slave IDE-1.)
# fdisk /dev/hdc
// d 1 (Delete the partition)→ n (Create a new partition)→ w (Confirm the change and store the setting.)
# mke2fs /dev/hdc1 (Do Ext2 format) or
# mke2fs –j /dev/hdc1 (Do Ext3 format) or
# mkfs.ext3 /dev/hdc1 (Do Ext3 format)

2. Create new directories and files
# cd /mnt
# mkdir CF
# mount –t ext2 /dev/hdc1 CF
# mkdir CF/boot
# mkdir CF/boot/grub
# cp /boot/grub/* CF/boot/grub/
// Copy all grub relevance files to CF card.

3. Modify grub.conf and menu.lst
{
default=0
timeout=10
#splashimage=(hd0,0)/grub/splash.xpm.gz
title Embedded Linux On CF
root (hd0,0)
kernel (hd0,0)/boot/vmlinuz ro root=/dev/hdc1
#CF card is on Slave IDE，thus the root is /dev/hdc1.
initrd (hd0,0)/boot/initrd-new.img
}

4. Construct boot sector on CF card
# grub > root (hd1,0)
// Since the CF card is not current bootup hard disk, thus the parameter here is hd1, not hd0
// The fist is hd0, 2nd is hd1, ....
# grub > setup (hd1)
// Install grub to CF card.
# grub > quit

5. Create kernel image.
The CF card is on the same x86 machine, thus we can use the original vmlinuz image which is under /boot directory.

6. Create root file system.
The CF card is on the same x86 machine, thus we can use the original initrd image which is under /boot directory.

Build ARM ToolChain - II

Do the same building test with some updated sources.

Files needed:
binutils-2.14.tar.gz
gcc-3.2.1.tar.gz
glibc-2.2.3.tar.gz
glibc-linuxthreaders-2.2.3.tar.gz

1. Binutils
// Same with Compilation - I.

2. Bootstrap compiler GCC
#cd ${PROJECT-PATH}/build-tools/
#tar zxvf gcc-3.2.1.tar.gz
#cd ${PROJECT-PATH}/build-tools/build-boot-gcc
// Do not do the compilation under the original untar directory.
#../gcc-3.2.1/configure --target=arm-linux --prefix=${PROJECT-PATH}/tools --with-headers=/usr/include --with-newlib --enable-languages=c --disable-shared
// The gcc 3.2.1 won't be created successfully without the flag "--disable-shared" for configuring.
// Headers for "--with-headers" actually should be generated by glibc building first.

3. Glibc
#cd ${PROJECT-PATH}/build-tools/
#tar zxvf glibc-2.2.3.tar.gz
#tar -zxvf glibc-linuxthreaders-2.2.3.tar.gz \ > --directory=glibc-2.2.3
#cd ${PROJECT-PATH}/build-tools/build-glibc/
// Do not do the compilation under the original untar directory.
#CC=arm-linux-gcc ../glibc-2.2.3/configure --host=arm-linux --prefix=”/usr” --enable-add-ons --with-headers=${PROJECT-PATH}/tools/arm-linux/include –-disable-profile –-without-fp
#make
// If errors on "weak precede definition" are found, we can modify the execution order of:
// ${PROJECT-PATH}/build-tools/glibc-2.2.3/sysdeps/unix/sysv/linux/arm/errlst.c (42L)
// 1. weak_alias (__old_sys_nerr, _old_sys_nerr)
// 2. strong_alias (__old_sys_nerr, _old_sys_nerr);
// 3. /*weak_alias (__old_sys_nerr, _old_sys_nerr)*/
#make install_root=${PROJECT-PATH}/tools/arm-linux \ > prefix=”” install
// If the following errors are found:
// ./stdio.texi:3269: First argument to cross-reference may not be empty.
// ./stdio.texi:3270: First argument to cross-reference may not be empty.
// Directly modify build-tools/glibc-2.2.3/manual/stdio.texi, and remove @ref{} to pass the compilation.
// Then several libraries will be generated under tools/arm-linux/lib.
// Modify ${PROJECT-PATH}/tools/arm-linux/lib/libc.so to remove absolute path, GROUP( libc.so.6 libc_nonshared.a )

4. GCC Compiler
#cd ${PROJECT-PATH}/build-tools/build-gcc/
// Do not do the compilation under the original untar directory.
#../gcc-3.2.1/configure --target=arm-linux --prefix=${PROJECT-PATH}/tools --enable-languages=c,c++ --with-headers=${PROJECT-PATH}/tools/arm-linux/include --with-libs=${PROJECT-PATH}/tools/lib --with-float=soft --enable-threads
#make all
#make install

I cannot build KS8695P-2.4.16-rmk2 kernel successfully with my arm-linux-gcc v3.2.1 tool, and will suffer hardware fp and software fp compiling errors. Didn't solve the issue yet, maybe the kernel source is too old, should have a try on 2.4.18 later version.

Build ARM ToolChain - I (Cont.)

4. GCC compiler
# cd ${PROJECT-PATH}/build-tools/build-gcc/
// Do not do the compilation under the original untar directory
// ../gcc-2.95.3/configure --target=arm-linux \
// --prefix=${PROJECT-PATH}/tools \
// --enable-languages=c,c++
// make all
// If there is no --with-headers and --with-libs flags, the compilation will be failed.
#../gcc-2.95.3/configure --target=arm-linux --prefix=${PROJECT-PATH}/tools --enable-languages=c,c++ --with-headers=${PROJECT-PATH}/tools/arm-linux/include --with-libs=${PROJECT-PATH}/tools/lib --with-float=soft --enable-threads
#make all
#make install
// Then, arm-linux-g++, arm-linux-c++, etc. will be created under tools/bin/ and overwrite previous bootstrap compiler binaries.

5. uClibc
// We need uClibc for our target, an embedded device.
#cd ${PROJECT-PATH}/build-tools/
#tar jxvf uClibc-0.9.16.tar.bz2
#cd ${PROJECT-PATH}/build-tools/uClibc-0.9.16
#make CROSS=arm-linux- menuconfig
// Configure the menu：
// Linux kernel header location = “${PROJECT-PATH}/kernel/linux-2.4.16-rmk2”
// Shared library loader path = /lib
// uClibc development environment directory = “${PROJECT-PATH}/tools/uClibc”
// Have to check FPU option, otherwise the compilation will complain symbolic errors.
#make CROSS=arm-linux-
#make CROSS=arm-linux- PREFIX=”” install
// Finally, uClibc components will be installed to ${PROJECT-PATH}/tools/uclibc.
// And arm-uclibc-gcc will be created as well.

Those new arm-uclibc-XXX, not arm-linux-XXX, binaries are what we needed for our embedded target. Those wrappers will help our applications to be built and linked with uClibc.