First of all VI stands for Visual (nothing visual about it) and VIM stands for visual improved.
Move cursor to the end of the file
:$
Move to the beginning of the file (1 stands for first line)
:1 or :0
Search and Replace (c Stand for confirmation)
:s/old_string/new_string/gc
Search for Words
:/string_to_locate
Page UP
CTRL + B
Page Down
CTRL + F
Useful Web sites
Vim book
http://www.truth.sk/vim/vimbook-OPL.pdf
Vi manual
:help
Copy an entire directory from one server to another recursively:
scp -r FOLDER_FROM_LOCAL USERNAME@SERVER:/var/www/REMOTEFOLDER
scp -r USERNAME@SERVER:/path/to/REMOTEFOLDER /var/www/LOCALFOLDER or to current folder scp -r USERNAME@SERVER:/path/to/REMOTEFOLDER .
Useful Web sites
http://www.hypexr.org/linux_scp_help.php
Pear (PHP Extension and Application Repository) packages are 100% php code. They are just PHP codes that are structured based on Pear’s standards and that are deposited in a local directory and referenced in php.ini.
PECL packages are php extensions and need to be compiled and the resulted .so files must be deposited in the extensions directory (extension_dir in php.ini).
When you run a command such as
yum install php5-gd
or
apt-get install php5-gd
The dynamic shared library file (.so) is generated and installed for you automatically.
Pear http://pear.php.net/manual/en/ PECL http://pecl.php.net/packages.php Introduction to extension writing http://devzone.zend.com/303/extension-writing-part-i-introduction-to-php-and-zend/ Wrapping C++ Classes in a PHP Extension http://devzone.zend.com/1435/wrapping-c-classes-in-a-php-extension/ phpize info http://us.php.net/manual/en/install.pecl.phpize.php Writing Php Extensions http://www.tuxradar.com/practicalphp/20/0/0 About php extensions http://www.boutell.com/newfaq/creating/phpextensions.html PHP Coding Standards http://pear.php.net/manual/en/standards.php
If you script runs fine within the command line interface but fails when you run it within the task scheduler, it might be because the script does not have enough permissions to run within the task scheduler context.
Make sure that "Run with the highest privileges" is selected as shown below:
uname -a
is returning the right version 3.2.0-30-generic however the vmware tools script is complaining.
Solution to create a couple of symlinks
ln -s /lib/modules/3.2.0-30-generic/build/include/generated/utsrelease.h /lib/modules/3.2.0-30-generic/build/include/linux/utsrelease.h ln -s /lib/modules/3.2.0-30-generic/build/include/generated/autoconf.h /lib/modules/3.2.0-30-generic/build/include/linux/autoconf.h
Then run the vmware perl script again
/vmware-install.pl
