Version: 2004-Nov-15
Copyright © 1997-2004 International Business Machines Corporation and
others. All Rights Reserved.
Today's software market is a global one in which it is desirable to develop and maintain one application (single source/single binary) that supports a wide variety of languages. The International Components for Unicode (ICU) libraries provide robust and full-featured Unicode services on a wide variety of platforms to help this design goal. The ICU libraries provide support for:
ICU has a sister project ICU4J that extends the internationalization capabilities of Java to a level similar to ICU. The ICU C/C++ project is also called ICU4C when a distinction is necessary.
This document describes how to build and install ICU on your machine.
For other information about ICU please see the following table of
links.
The ICU homepage also links to related information about writing
internationalized software.
| ICU Homepage | http://oss.software.ibm.com/icu/index.html |
| ICU4J Homepage | http://oss.software.ibm.com/icu4j/index.html |
| FAQ - Frequently Asked Questions about ICU | http://oss.software.ibm.com/icu/userguide/icufaq.html |
| ICU User's Guide | http://oss.software.ibm.com/icu/userguide/index.html |
| Download ICU Releases | http://oss.software.ibm.com/icu/download/index.html |
| API Documentation Online | http://oss.software.ibm.com/icu/apiref/index.html |
| Online ICU Demos | http://oss.software.ibm.com/icu/demo/index.html |
| Contacts and Bug Reports/Feature Requests | http://oss.software.ibm.com/icu/archives/index.html |
Important: Please make sure you understand the Copyright and License Information.
The following list concentrates on changes that affect existing applications migrating from previous ICU releases. For more news about this release, see the ICU 3.2 download page.
Starting in ICU 3.2, the unicode/utypes.h and unicode/putil.h headers are no longer circularly dependent on each other. This means that if you use any of the functions from unicode/putil.h and only included unicode/utypes.h, you will now have to include unicode/putil.h too. No stable API functions have been removed from these headers, but some internal function declarations (marked with @internal) have been moved to internal headers.
This change was announced on the icu mailing list, and it was done to fix some header dependency issues that appeared while trying to make some changes to the utf.h header macros.
There are two ways to download ICU releases:
In the descriptions below, <ICU> is the
full path name of the ICU directory (the top level directory from the
distribution archives) in your file system. You can also view the ICU Architectural
Design section of the User's Guide to see which libraries you need for
your software product. You need at least the data ([lib]icudt
)
and the common ([lib]icuuc
) libraries in order to use ICU.
| File | Description |
|---|---|
| readme.html | Describes the International Components for Unicode (this file) |
| license.html | Contains the text of the ICU license |
| Directory | Description |
|---|---|
| <ICU>/source/common/ | The core Unicode and support functionality, such as resource bundles, character properties, locales, codepage conversion, normalization, Unicode properties, Locale, and UnicodeString. |
| <ICU>/source/i18n/ | Modules in i18n are generally the more data-driven, that is to say resource bundle driven, components. These deal with higher-level internationalization issues such as formatting, collation, text break analysis, and transliteration. |
| <ICU>/source/data/ |
This directory contains the source data in text format, which is compiled into binary form during the ICU build process. It contains several subdirectories, in which the data files are grouped by function. Note that the build process must be run again after any changes are made to this directory.
If you are creating a special ICU build, you can set the ICU_DATA environment variable to the out/ or the out/build/ directories, but this is generally discouraged because most people set it incorrectly. You can view the ICU Data Management section of the ICU User's Guide for details. |
| <ICU>/source/test/intltest/ | A test suite including all C++ APIs. For information about running the test suite, see the users' guide. |
| <ICU>/source/test/cintltst/ | A test suite written in C, including all C APIs. For information about running the test suite, see the users' guide. |
| <ICU>/source/test/testdata/ | Source text files for data, which are read by the tests. It contains the subdirectories out/build/ which is used for intermediate files, and out/ which contains testdata.dat. |
| <ICU>/source/tools/ | Tools for generating the data files. Data files are generated by invoking <ICU>/source/data/build/makedata.bat on Win32 or <ICU>/source/make on UNIX. |
| <ICU>/source/samples/ | Various sample programs that use ICU |
| <ICU>/source/extra/ | Non-supported API additions. Currently, it contains the 'ustdio' file i/o library |
| <ICU>/source/layout/ | Contains the ICU layout engine (not a rasterizer). |
| <ICU>/packaging/ <ICU>/debian/ |
These directories contain scripts and tools for packaging the final ICU build for various release platforms. |
| <ICU>/source/config/ | Contains helper makefiles for platform specific build commands. Used by 'configure'. |
| <ICU>/source/allinone/ | Contains top-level ICU workspace and project files, for instance to build all of ICU under one MSVC project. |
| <ICU>/include/ | Contains the headers needed for developing software that uses ICU on Windows. |
| <ICU>/lib/ | Contains the import libraries for linking ICU into your Windows application. |
| <ICU>/bin/ | Contains the libraries and executables for using ICU on Windows. |
| Operating system | Compiler | Testing frequency |
|---|---|---|
| Windows 2000 with Cygwin | Microsoft Visual C++ 6.0 | Reference platform |
| Windows XP | Microsoft Visual C++ .NET 2003 (7.1) | Reference platform |
| Red Hat Linux 9 | gcc 3.2.2 | Reference platform |
| AIX 5.2 | Visual Age C++ 6.0 | Reference platform |
| Solaris 7 (SunOS 5.7) | Workshop Pro (Forte) CC 6.0 | Reference platform |
| HP-UX 11.11 | aCC A.03.50 cc B.11.11.08 |
Reference platform |
| Windows XP with Cygwin | Microsoft Visual C++ .NET 2002 (7.0) | Regularly tested |
| Windows 98/2000/XP | Microsoft Visual C++ 6.0 | Regularly tested |
| Red Hat Linux 7.2 | gcc 2.96 | Regularly tested |
| Red Hat Linux 8.0 | gcc 3.2 | Regularly tested |
| Mac OS X (10.2) | gcc 3.1 (Developer Tools, July 2002) |
Regularly tested |
| Solaris 8 (SunOS 5.8) | Workshop Pro CC 4.2 (use 'runConfigureICU SOLARISCC/W4.2') |
Regularly tested |
| Solaris 2.6 (SunOS 5.6) | gcc 2.95.2 | Regularly tested |
| FreeBSD 4.8 | gcc 2.95.4 | Regularly tested |
| AIX 5.1.0 L | Visual Age C++ 5.0 | Regularly tested |
| AIX 4.3.3 | Visual Age C++ 6.0 | Regularly tested |
| z/OS 1.3 | cxx 1.3 | Regularly tested |
| OS/400 (iSeries) V5R3 | iCC | Regularly tested |
| Cygwin | gcc 2.95.3 | Rarely tested |
| Red Hat Linux Advanced Server 2.1 | Intel C++ Compiler 6.0.1 | Rarely tested |
| SuSE Linux Enterprise Server 9 (PPC) | Visual Age 7.0 | Rarely tested |
| Red Hat Alpha Linux 7.2 | gcc 2.96 | Rarely tested |
| Red Hat Alpha Linux 7.2 | Compaq C++ Compiler 3.2 Compaq C Compiler 6.5.6 |
Rarely tested |
| HP-UX 11.01 | aCC A.03.13 cc A.11.01.00 |
Rarely tested |
| QNX | gcc | Rarely tested |
| NetBSD, OpenBSD | gcc | Rarely tested |
| BeOS | gcc | Rarely tested |
| SGI/IRIX | MIPSpro CC | Rarely tested |
| Tru64 (OSF) | Compaq's cxx compiler | Rarely tested |
| HP-UX 11.01 | CC A.03.10 | Rarely tested |
| MP-RAS | NCR MP-RAS C/C++ Compiler | Rarely tested |
Building International Components for Unicode requires:
(If you want to build with Microsoft Visual C++ 6, please refer to the note about building with Visual C++ 6 below.)
The steps are:
Using MSDEV At The Command Line Note: You can build ICU from the command line. Assuming that you have properly installed Microsoft Visual C++ to support command line execution, you can run the following command, 'devenv.com <ICU>\source\allinone\allinone.sln /build Release'. You can also use Cygwin with this compiler to build ICU, and you can refer to the How To Build And Install On Windows with Cygwin section for more details.
Setting Active Configuration Note: To set the active configuration, two different possibilities are:
Batch Configuration Note: If you want to build the Debug and Release configurations at the same time, choose "Build" menu, and select "Batch Build...". Click the "Select All" button, and then click the "Rebuild" button.
Microsoft Visual Studio 6.0 Note: ICU will build with Microsoft Visual Studio 6. It is recommended that you use the "<ICU>\source\allinone\allinone.dsw" workspace to build ICU. The instructions for building with Visual Studio 6 are similar to the instructions for Visual Studio .NET. If you have Microsoft Visual Studio .NET 2002, it is recommended that you build from the command line with Cygwin. The Cygwin building instructions are in How To Build And Install On Windows with Cygwin section of this document.
Building International Components for Unicode requires:
The steps are:
Building International Components for Unicode with this configuration requires:
There are two ways you can build ICU with Cygwin. You can build with gcc or Microsoft Visual C++. If you use gcc, the resulting libraries and tools will depend on the Cygwin environment. If you use Microsoft Visual C++, the resulting libraries and tools do not depend on Cygwin and can be more easily distributed to other Windows computers (the generated man pages and shell scripts still need Cygwin). To build with gcc, please follow the "How To Build And Install On UNIX" instructions, while you are inside a Cygwin bash shell. To build with Microsoft Visual C++, please use the following instructions:
Configuring ICU on Windows NOTE: In addition to the Unix configuration note the following configure options currently do not work on Windows with Microsoft's compiler. Some options can work by manually editing icu/source/common/unicode/pwin32.h, but manually editing the files is not recommended.
Building International Components for Unicode on UNIX requires:
Here are the steps to build ICU:
Configuring ICU NOTE: Type "./runConfigureICU --help" for help on how to run it and a list of supported platforms. You may also want to type "./configure --help" to print the available configure options that you may want to give runConfigureICU. If you are not using the runConfigureICU script, or your platform is not supported by the script, you may need to set your CC, CXX, CFLAGS and CXXFLAGS environment variables, and type "./configure". Some of the more frequently used options to configure are --disable-64bit-libs to create 32-bit libraries, and --srcdir to do out of source builds (build the libraries in the current location). HP-UX user's, please see this note regarding HP-UX multithreaded build issues with newer compilers. Solaris user's, please see this note regarding Solaris multithreaded build issues.
Running The Tests From The Command Line NOTE: You may have to set certain variables if you with to run test programs individually, that is apart from "gmake check". The environment variable ICU_DATA can be set to the full pathname of the data directory to indicate where the locale data files and conversion mapping tables are when you are not using the shared library (e.g. by using the .dat archive or the individual data files). The trailing "/" is required after the directory name (e.g. "$Root/source/data/out/" will work, but the value "$Root/source/data/out" is not acceptable). You do not need to set ICU_DATA if the complete shared data library is in your library path.
Installing ICU NOTE: Some platforms use package management tools to control the installation and uninstallation of files on the system, as well as the integrity of the system configuration. You may want to check if ICU can be packaged for your package management tools by looking into the "packaging" directory. (Please note that if you are using a snapshot of ICU from CVS, it is probable that the packaging scripts or related files are not up to date with the contents of ICU at this time, so use them with caution).
You can install ICU on z/OS or OS/390 (the previous name of z/OS), but IBM tests only the z/OS installation. These platforms commonly are called "MVS". You install ICU in a z/OS UNIX system services file system such as HFS or zFS. On this platform, it is important that you understand a few details:
z/OS introduced the concept of Extra Performance Linkage (XPLINK) to
bring performance improvement opportunities to call-intensive C and C++
applications such as ICU. XPLINK is enabled on a DLL-by-DLL basis, so
if you are considering using XPLINK in your application that uses ICU,
you should consider building the XPLINK-enabled version of ICU. You
need to set ICU's environment variable OS390_XPLINK=1
prior to invoking the make process to produce binaries that are enabled
for XPLINK.
Note: XPLINK, which is enabled for z/OS 1.2 and later, requires the PTF PQ69418 to build XPLINK enabled binaries.
--with-iostream=old
configure
option when using runConfigureICU. This will prevent applications that
use the icuio library from crashing.When you build ICU on a system such as z/OS 1.2, the binaries that result can run on that level of the operating system and later, such as z/OS 1.3 and z/OS 1.4. It's possible that you may have a z/OS 1.4 system, but you may need to deliver binaries on z/OS 1.2 and above. z/OS gives you this ability by targeting the complier and linker to run at the older level, thereby producing the desired binaries.
To set the compiler and LE environment to OS/390 2.10, specify the
following, "./runConfigureICU OS390V2R10
"
To set the compiler and LE environment to z/OS 1.2 specify the
following, "./runConfigureICU zOSV1R2
"
By default, ICU builds its libraries into the UNIX file system (HFS). In addition, there is a z/OS specific environment variable (OS390BATCH) to build some libraries into the z/OS native file system. This is useful, for example, when your application is externalized via Job Control Language (JCL).
The OS390BATCH environment variable enables non-UNIX support including the batch environment. When OS390BATCH is set, the libicuucXX.dll, libicudtXXe.dll, and libicudtXXe_stub.dll binaries are built into data sets (the native file system). Turning on OS390BATCH does not turn off the normal z/OS UNIX build. This means that the z/OS UNIX (HFS) DLLs will always be created.
Two additional environment variables indicate the names of the z/OS data sets to use. The LOADMOD environment variable identifies the name of the data set that contains the dynamic link libraries (DLLs) and the LOADEXP environment variable identifies the name of the data set that contains the side decks, which are normally the files with the .x suffix in the UNIX file system.
A data set is roughly equivalent to a UNIX or Windows file. For most kinds of data sets the operating system maintains record boundaries. UNIX and Windows files are byte streams. Two kinds of data sets are PDS and PDSE. Each data set of these two types contains a directory. It is like a UNIX directory. Each "file" is called a "member". Each member name is limited to eight bytes, normally EBCDIC.
Here is an example of some environment variables that you can set prior to building ICU:
OS390BATCH=1 LOADMOD=USER.ICU.LOAD LOADEXP=USER.ICU.EXP
The PDS member names for the DLL file names are as follows:
IXMIXXIN --> libicui18nXX.dll IXMIXXUC --> libicuucXX.dll IXMIXXDA --> libicudtXXe.dll IXMIXXD1 --> libicudtXXe_stub.dll (Only when OS390_STUBDATA=1)
You should point the LOADMOD environment variable at a partitioned data set extended (PDSE) and point the LOADEXP environment variable at a partitioned data set (PDS). The PDSE can be allocated with the following attributes:
Data Set Name . . . : USER.ICU.LOAD Management class. . : **None** Storage class . . . : BASE Volume serial . . . : TSO007 Device type . . . . : 3390 Data class. . . . . : LOAD Organization . . . : PO Record format . . . : U Record length . . . : 0 Block size . . . . : 32760 1st extent cylinders: 1 Secondary cylinders : 5 Data set name type : LIBRARY
The PDS can be allocated with the following attributes:
Data Set Name . . . : USER.ICU.EXP Management class. . : **None** Storage class . . . : BASE Volume serial . . . : TSO007 Device type . . . . : 3390 Data class. . . . . : **None** Organization . . . : PO Record format . . . : FB Record length . . . : 80 Block size . . . . : 3200 1st extent cylinders: 3 Secondary cylinders : 3 Data set name type : PDS
Before you start building ICU, ICU requires the following:
The following describes how to setup and build ICU. For background information, you should look at the UNIX build instructions.
CRTLIB LIB(libraryname)
ADDENVVAR ENVVAR(CC) VALUE('/usr/bin/icc') ADDENVVAR ENVVAR(CXX) VALUE('/usr/bin/icc') ADDENVVAR ENVVAR(MAKE) VALUE('/usr/bin/gmake') ADDENVVAR ENVVAR(OUTPUTDIR) VALUE('libraryname')libraryname identifies target as400 library for *module, *pgm and *srvpgm objects.
There are many ways that a person can package ICU with their software products. Usually only the libraries need to be considered for packaging.
On UNIX, you should have used "gmake install" to make it easier to develop and package ICU. The bin, lib and include directories are needed to develop applications that use ICU. These directories will be created relative to the "--prefix=dir" configure option (See the UNIX build instructions). When ICU is built on Windows, a similar directory structure is built.
When changes have been made to the standard ICU distribution, it is recommended that at least one of the following guidelines be followed for special packaging.
Following these guidelines prevents other applications that use a standard ICU distribution from conflicting with any libraries that you need. On operating systems that do not have a standard C++ ABI (name mangling) for compilers, it is recommended to do this special packaging anyway. More details on customizing ICU are available in the User's Guide. The ICU Source Code Organization section of this readme.html gives a more complete description of the libraries.
| Library Name | Windows Filename | Linux Filename | Comment |
|---|---|---|---|
| Data Library | icudtXYl.dll | libicudata.so.XY.Z | Data required by the Common and I18n libraries. There are many ways to package and customize this data, but by default this is all you need. |
| Common Library | icuucXY.dll | libicuuc.so.XY.Z | Base library required by all other ICU libraries. |
| Internationalization (i18n) Library | icuinXY.dll | libicui18n.so.XY.Z | A library that contains many locale based internationalization (i18n) functions. |
| Layout Engine | iculeXY.dll | libicule.so.XY.Z | An optional engine for doing font layout. |
| Layout Extensions Engine | iculxXY.dll | libiculx.so.XY.Z | An optional engine for doing font layout that uses parts of ICU. |
| ICU I/O (Unicode stdio) Library | icuioXY.dll | libicuio.so.XY.Z | An optional library that provides a stdio like API with Unicode support. |
| Tool Utility Library | icutuXY.dll | libicutu.so.XY.Z | An internal library that contains internal APIs that are only used by ICU's tools. If you do not use ICU's tools, you do not need this library. |
Normally only the above ICU libraries need to be considered for packaging. The versionless symbolic links to these libraries are only needed for easier development. The X, Y and Z parts of the name are the version numbers of ICU. For example, ICU 2.0.2 would have the name libicuuc.so.20.2 for the common library. The exact format of the library names can vary between platforms due to how each platform can handles library versioning.
Upon the first usage of most ICU APIs, the global mutex will get
initialized properly, but you can use the u_init()
function
from uclean.h to ensure that it is initialized properly. Without calling
this function from a single thread, the data caches inside ICU may get
initialized more than once from multiple threads, which may cause memory
leaks and other problems. There is no harm in calling u_init()
in a single threaded application.
If you are building ICU with a newer aCC compiler and you are planning on using the older <iostream.h> instead of the newer <iostream>, you will need to use a special configure flag before building ICU. By default, the aCC -AA flag is used on HP-UX when the compiler supports that option in order to make ICU thread safe with RogueWave and other libraries using the 2.0 Standard C++ library. Your applications that use ICU will also need to use the -AA compiler flag. To turn off this behavior in ICU, you will need to use the --with-iostream= old configure option when you first use runConfigureICU.
ICU's tests use usleep()
, which is multithread unsafe on
versions of Solaris before version 9. This does not mean that ICU is not
thread safe because only ICU's test code uses usleep()
. The
sleep()
and nanosleep()
functions could be used
in ICU's multithreaded tests, but sleep()
and
nanosleep()
are not a stable API between versions of Solaris.
Solaris 9 fixes usleep so that it is multithread safe.
This hanging behavior tends to appear on multi-CPU machines. Single CPU Solaris 8 machines do not seem to show this behavior.
In a future version of ICU, we hope to find a portable solution to this problem that will work between the modern versions of Solaris.
Solaris 8, and earlier, has outstanding thread deadlocking issues that may be problematic for applications using either native, or POSIX, threading on these platforms. Sun states that Solaris 9 does not have the deadlock problems. Deadlocks may occur either during initialization of the Solaris threading library, or at any other time.
Sun Microsystems has provided a Sun Alert Notification regarding the issue. Users should consider applying the latest OS patches to their Solaris installations in order to help avoid deadlock. Further information regarding the issue, and links to applicable patches, may be found at:
[1] "Applications Linked to libthread May Hang", Sun Alert
Notification, Sun Microsystems, Inc., 04-Sep-2002
http://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=fsalert%2F46867&zone_32=4663077
Sun is not providing patches for Solaris 6 (2.6), or earlier.
Sun states that by applying the patch users will avoid the deadlock issues. However, with all applicable patches applied, deadlock may still be seen, as demonstrated by the ICU Mutex unit tests. The unit test will hang indefinitely. No bug exists in ICU. However, a latent bug still exists in Solaris, which Sun Microsystems has yet to resolve. In order to avoid this, users are suggested to modify their LD_LIBRARY_PATH according to the guidelines specified by Sun Microsystems in the Sun Alert Notification.
In order to avoid synchronization and threading issues, developers are suggested to strictly follow the compiling and linking guidelines for multithreaded applications, specified in the following document from Sun Microsystems. Most notably, pay strict attention to the following statements from Sun:
To use libthread, specify -lthread before -lc on the ld command line, or last on the cc command line.
To use libpthread, specify -lpthread before -lc on the ld command line, or last on the cc command line.
Failure to do this may cause spurious lock conflicts, recursive mutex failure, and deadlock.
[2] "Solaris Multithreaded Programming Guide, Compiling and
Debugging", Sun Microsystems, Inc., Apr 2004
http://docs.sun.com/db/doc/806-6867/6jfpgdcob?a=view
If you are building on the Win32 platform, it is important that you understand a few of the following build details.
As delivered, the International Components for Unicode build as several DLLs, which are placed in the "<ICU>\bin" directory. You must add this directory to the PATH environment variable in your system, or any executables you build will not be able to access International Components for Unicode libraries. Alternatively, you can copy the DLL files into a directory already in your PATH, but we do not recommend this. You can wind up with multiple copies of the DLL and wind up using the wrong one.
Note: When packaging a Windows application for distribution and installation on user systems, copies of the ICU DLLs should be included with the application, and installed for exclusive use by the application. This is the only way to insure that your application is running with the same version of ICU, built with exactly the same options, that you developed and tested with. Refer to Microsoft's guidelines on the usage of DLLs, or search for the phrase "DLL hell" on msdn.microsoft.com.
If you are building on a UNIX platform, and if you are installing ICU in a non-standard location, you may need to add the location of your ICU libraries to your LD_LIBRARY_PATH or LIBPATH environment variable (or the equivalent runtime library path environment variable for your system). The ICU libraries may not link or load properly without doing this.
Note that if you do not want to have to set this variable, you may instead use the --enable-rpath option at configuration time. This option will instruct the linker to always look for the libraries where they are installed. You will need to use the appropriate linker options when linking your own applications and libraries against ICU, too. Please refer to your system's linker manual for information about runtime paths. The use of rpath also means that when building a new version of ICU you should not have an older version installed in the same place as the new version's installation directory, as the older libraries will used during the build, instead of the new ones, likely leading to an incorrectly build ICU. (This is the proper behavior of rpath.)
If you are using ICU's Makefiles to build ICU on a new platform, there are a few places where you will need to add or modify some files. If you need more help, you can always ask the icu4c-support mailing list. Once you have finished porting ICU to a new platform, it is recommended that you contribute your changes back to ICU via the icu4c-support mailing list. This will make it easier for everyone to benefit from your work.
For some people, it may not be necessary for completely build ICU. Most of the makefiles and build targets are for tools that are used for building ICU's data, and an application's data (when an application uses ICU resource bundles for its data).
Data files can be built on a different platform when both platforms share the same endianness and the same charset family. This assertion does not include platform dependent DLLs/shared/static libraries. For details see the User Guide ICU Data chapter.
ICU 2.8 removes the requirement that ICU be completely built in the native operating environment. It adds the icuswap tool which can be run on any platform to turn binary ICU data files from any one of the three formats into any one of the other data formats. This allows a application to use ICU data built anywhere to be used for any other target platform.
WARNING! Building ICU without running the tests is not recommended. The tests verify that ICU is safe to use. It is recommended that you try to completely port and test ICU before using the libraries for your own application.
Try to follow the build steps from the UNIX build instructions. If the configure script
fails, then you will need to modify some files. Here are the usual steps
for porting to a new platform:
The platform dependencies have been mostly isolated into the following files in the common library. This information can be useful if you are porting ICU to a new platform.
It is possible to build each library individually without our Makefiles.
They must be built in the following order:
Copyright © 1997-2004 International Business Machines Corporation
and others. All Rights Reserved.
IBM Globalization Center of Competency - San José
5600 Cottle Road
San José, CA 95193
USA


A long time ago, in a galaxy far, far from Silicon Beach, I was born at St. John's Hospital in Santa Monica, and raised in Venice. My roots lie primarily in the LA punk rock and hip hop cultures. My dad bought a Mac SE in the late 80's, and i used it to play a lot of Dark Castle. I guess you could say that computers have been as much of a constant in my life as almost anything else.
My childhood dream was (Surprise!) to work in the music business, a goal which I accomplished in 2007, when I got my first "Official Gig" as an audio engineer. Between then and now, I've been blessed to work with artists whose posters I had on my wall, as well as the privilege of calling some of them my friends. I've toured the US, and have Canadian, British, Italian, and Mexican stamps in my passport. I'd say 15 year-old me is pretty stoked.
Last year, I became a partner at Wolf's Head, a premium men's clothing store and barbershop located in Santa Barbara that I'm still involved with, and very passionate about. I'm lucky to have 2 amazing business partners and close friends.
It was while teaching myself to do basic SEO for our site that I first considered coding as a career that I could excel in. I mean, I was already used to sitting for 12 or more hours in front of a computer screen while mixing for the likes of DJ Muggs, co-producing one of The Source Magazine's "Top 50 Hip-Hop Songs of 2010", and engineering"Piñata", which came in at number six on Rolling Stone's "40 Best Rap Albums of 2014". All of that was accomplished via knowledge I gained from a trade school, so I didn't see why the same couldn't be true for venturing into a tech career of some sort.
After much internal debate and careful consideration, I chose to attend General Assembly's Web Development Immersive program in Santa Monica. Over the course of 12 weeks, I received over 420 hours of instruction, and at least as many working independently to build a strong foundation in JavaScript, Node.js, MongoDB,
Angular.js, SQL Databases, and Ruby on Rails.
I've exceeded my own expectations of what I could accomplish in 12 weeks. I led the only group to receive a perfect score on a project, and won an attendance award (Which, if I were to tell you of my previous school endeavors outside of Musicians Institute, you would find as hilarious as I do). I never thought I'd be able to say with confidence that I'm a capable Web Developer in such a short time. But, then, I never thought I'd be able to say I worked on "Detox".
This app is a collaboration between myself and 2 classmates, designed with the idea of recycling household items in Los Angeles that would otherwise become part of the 12,000 tons of waste delivered to Puente Hills landfill each week. Puente Hills landfill is the largest rubbish dump in America.
This project was built in Node.js, Javascript, Express, and utilized MongoDB for the database. Views were rendered via EJS templates. I was responsible for Amazon s3 integration for the photo uploads, Google maps integration, Google GeoCoding integration, hand-rolled Passport authentication for the Facebook login, deployment to Heroku, managing the GitHub, as well as a good amount of the API build. We were the only group in our cohort to receive a perfect score on a project, and I'm very proud of that.
•Fully optimized for mobile.
•Project completed in a 5 day sprint.
Revisit is a digital diary created by myself and another classmate. Users can upload photos and make "Entries" (single posts), or multiple photos to create "Chapters" (albums). We also added the option to upload a song for each Chapter, as music is so integral to certain memories or experiences that one has in their life.
This is a MEAN Stack app. I built the back-end API, and integrated Amazon s3 for photo and video uploads. I also managed the GitHub repo.
•Project completed in a 5 day sprint.
An object-oriented JavaScript version of the classic card game. The card images are being fetched from a remote server. Other Technologies used: HTML & CSS
•Project completed in a 5 day sprint.
 Other Technologies used: HTML, CSS, Sass, Hand-rolled Authentication, PostgreSQL database, & Heroku.
•Fully optimized for mobile.
•Project completed in a 5 day sprint.


Who Am I?
I am a Full Stack developer and UX designer. I learned to program while I was attending the New York City Dev Bootcamp. I believe in simplicity, innovation, and creativity when designing and building web applications. When I am not cranking out elegant code or designing beautiful interfaces, you will find me riding my bike on the west side highway or drinking dark coffee at a local coffee shop.
What I am all about
New York is a beautiful place and especially during the winter months. Snowboarding is one of those sports I am not good at but I never give up. Occasionally you will find me at Thunder Ridge ski area as soon as the season begins. Although the majority of the year you will find me behind a computer screen, I do set aside time for family. Family is very important to me and I do believe everyone should take the time off in order to have a well-balanced life. Many people have played a key role in my career and I am very thankful. But I've also worked extremely hard to get to where I am today. Every challenge that I deal with on a day-to-day basis is always meaningful and rewarding. Bottom line: I love what I do and will continue doing what I love.


1. The Web
2. HTML
3. URL
4. HTTP
5. Web Applications
1. The World Wide Web
Its a collection of HTML(Hyper Text Markup Language) documents.
And the links between the page is called as Hyper links or links.
Invented in early 1990’s and its has 30 Billion pages.
2. HTML
Text content (what I see)
Markup (what it looks like)
References to other documents (eg: images + videos)
Links to others pages.
Note: to play html use
TAG
opening tag along with contents & closing tag is called as elements
* B - Bold
* em - emphasis - italics
* Attribute
* Image
Its end with a void tag (A void tag (>) is something that doesn’t have any content).
* Whitespace
br tag is called as inline and it also calles as void tag.


VIRT-INSTALL
Section: Virtual Machine Install Tools (1)Updated: 2011-07-28
Index Return to Main Contents
NAME
virt-install - provision new virtual machinesSYNOPSIS
virt-install [OPTION]...DESCRIPTION
virt-install is a command line tool for creating new KVM, Xen, or Linux container guests using the "libvirt" hypervisor management library. See the EXAMPLES section at the end of this document to quickly get started.virt-install tool supports both text based & graphical installations, using VNC or SDL graphics, or a text serial console. The guest can be configured to use one or more virtual disks, network interfaces, audio devices, physical USB or PCI devices, among others.
The installation media can be held locally or remotely on NFS, HTTP, FTP servers. In the latter case "virt-install" will fetch the minimal files necessary to kick off the installation process, allowing the guest to fetch the rest of the OS distribution as needed. PXE booting, and importing an existing disk image (thus skipping the install phase) are also supported.
Given suitable command line arguments, "virt-install" is capable of running completely unattended, with the guest 'kickstarting' itself too. This allows for easy automation of guest installs. An interactive mode is also available with the --prompt option, but this will only ask for the minimum required options.
OPTIONS
Most options are not required. Minimum requirements are --name, --ram, guest storage (--disk, --filesystem or --nodisks), and an install option.- -h, --help
- Show the help message and exit
- --connect=CONNECT
-
Connect to a non-default hypervisor. The default connection is chosen based
on the following rules:
-
- xen
- If running on a host with the Xen kernel (checks against /proc/xen)
- qemu:///system
- If running on a bare metal kernel as root (needed for KVM installs)
- qemu:///session
-
If running on a bare metal kernel as non-root
It is only necessary to provide the "--connect" argument if this default prioritization is incorrect, eg if wanting to use QEMU while on a Xen kernel.
-
General Options
General configuration parameters that apply to all types of guest installs.- -n NAME, --name=NAME
- Name of the new guest virtual machine instance. This must be unique amongst all guests known to the hypervisor on the connection, including those not currently active. To re-define an existing guest, use the virsh(1) tool to shut it down ('virsh shutdown') & delete ('virsh undefine') it prior to running "virt-install".
- -r MEMORY, --ram=MEMORY
- Memory to allocate for guest instance in megabytes. If the hypervisor does not have enough free memory, it is usual for it to automatically take memory away from the host operating system to satisfy this allocation.
- --arch=ARCH
- Request a non-native CPU architecture for the guest virtual machine. If omitted, the host CPU architecture will be used in the guest.
- --machine=MACHINE
- The machine type to emulate. This will typically not need to be specified for Xen or KVM, but is useful for choosing machine types of more exotic architectures.
- -u UUID, --uuid=UUID
- UUID for the guest; if none is given a random UUID will be generated. If you specify UUID, you should use a 32-digit hexadecimal number. UUID are intended to be unique across the entire data center, and indeed world. Bear this in mind if manually specifying a UUID
- --vcpus=VCPUS[,maxvcpus=MAX][,sockets=#][,cores=#][,threads=#]
-
Number of virtual cpus to configure for the guest. If 'maxvcpus' is specified,
the guest will be able to hotplug up to MAX vcpus while the guest is running,
but will startup with VCPUS.
CPU topology can additionally be specified with sockets, cores, and threads. If values are omitted, the rest will be autofilled prefering sockets over cores over threads.
- --cpuset=CPUSET
-
Set which physical cpus the guest can use. "CPUSET" is a comma separated list of numbers, which can also be specified in ranges or cpus to exclude. Example:
0,2,3,5 : Use processors 0,2,3 and 5 1-5,^3,8 : Use processors 1,2,4,5 and 8
If the value 'auto' is passed, virt-install attempts to automatically determine an optimal cpu pinning using NUMA data, if available.
- --numatune=NODESET,[mode=MODE]
-
Tune NUMA policy for the domain process. Example invocations
--numatune 1,2,3,4-7 --numatune \"1-3,5\",mode=preferred
Specifies the numa nodes to allocate memory from. This has the same syntax as "--cpuset" option. mode can be one of 'interleave', 'preferred', or 'strict' (the default). See 'man 8 numactl' for information about each mode.
The nodeset string must use escaped-quotes if specifying any other option.
- --cpu MODEL[,+feature][,-feature][,match=MATCH][,vendor=VENDOR]
-
Configure the CPU model and CPU features exposed to the guest. The only
required value is MODEL, which is a valid CPU model as listed in libvirt's
cpu_map.xml file.
Specific CPU features can be specified in a number of ways: using one of libvirt's feature policy values force, require, optional, disable, or forbid, or with the shorthand '+feature' and '-feature', which equal 'force=feature' and 'disable=feature' respectively
Some examples:
-
- --cpu core2duo,+x2apic,disable=vmx
- Expose the core2duo CPU model, force enable x2apic, but do not expose vmx
- --cpu host
- Expose the host CPUs configuration to the guest. This enables the guest to take advantage of many of the host CPUs features (better performance), but may cause issues if migrating the guest to a host without an identical CPU.
-
- --description
- Human readable text description of the virtual machine. This will be stored in the guests XML configuration for access by other applications.
- --security type=TYPE[,label=LABEL]
- Configure domain security driver settings. Type can be either 'static' or 'dynamic'. 'static' configuration requires a security LABEL. Specifying LABEL without TYPE implies static configuration.
Installation Method options
- -c CDROM, --cdrom=CDROM
- File or device use as a virtual CD-ROM device for fully virtualized guests. It can be path to an ISO image, or to a CDROM device. It can also be a URL from which to fetch/access a minimal boot ISO image. The URLs take the same format as described for the "--location" argument. If a cdrom has been specified via the "--disk" option, and neither "--cdrom" nor any other install option is specified, the "--disk" cdrom is used as the install media.
- -l LOCATION, --location=LOCATION
-
Distribution tree installtion source. virt-install can recognize
certain distribution trees and fetches a bootable kernel/initrd pair to
launch the install.
With libvirt 0.9.4 or later, network URL installs work for remote connections. virt-install will download kernel/initrd to the local machine, and then upload the media to the remote host. This option requires the URL to be accessible by both the local and remote host.
The "LOCATION" can take one of the following forms:
-
- DIRECTORY
- Path to a local directory containing an installable distribution image
- nfs:host:/path or nfs://host/path
- An NFS server location containing an installable distribution image
- http://host/path
- An HTTP server location containing an installable distribution image
- ftp://host/path
- An FTP server location containing an installable distribution image
-
Some distro specific url samples:
- Fedora/Red Hat Based
- http://download.fedoraproject.org/pub/fedora/linux/releases/10/Fedora/i386/os/
- Debian/Ubuntu
- http://ftp.us.debian.org/debian/dists/etch/main/installer-amd64/
- Suse
- http://download.opensuse.org/distribution/11.0/repo/oss/
- Mandriva
- ftp://ftp.uwsg.indiana.edu/linux/mandrake/official/2009.0/i586/
-
- --pxe
- Use the PXE boot protocol to load the initial ramdisk and kernel for starting the guest installation process.
- --import
- Skip the OS installation process, and build a guest around an existing disk image. The device used for booting is the first device specified via "--disk" or "--filesystem".
- --init=INITPATH
- Path to a binary that the container guest will init. If a root "--filesystem" is has been specified, virt-install will default to /sbin/init, otherwise will default to /bin/sh.
- --livecd
- Specify that the installation media is a live CD and thus the guest needs to be configured to boot off the CDROM device permanently. It may be desirable to also use the "--nodisks" flag in combination.
- -x EXTRA, --extra-args=EXTRA
- Additional kernel command line arguments to pass to the installer when performing a guest install from "--location". One common usage is specifying an anaconda kickstart file for automated installs, such as --extra-args ``ks=http://myserver/my.ks''
- --initrd-inject=PATH
-
Add PATH to the root of the initrd fetched with "--location". This can be
used to run an automated install without requiring a network hosted kickstart
file:
--initrd-inject=/path/to/my.ks --extra-args ``ks=file:/my.ks''
- --os-type=OS_TYPE
-
Optimize the guest configuration for a type of operating system (ex. 'linux',
'windows'). This will attempt to pick the most suitable ACPI & APIC settings,
optimally supported mouse drivers, virtio, and generally accommodate other
operating system quirks.
By default, virt-install will attempt to auto detect this value from the install media (currently only supported for URL installs). Autodetection can be disabled with the special value 'none'
See "--os-variant" for valid options.
- --os-variant=OS_VARIANT
-
Further optimize the guest configuration for a specific operating system
variant (ex. 'fedora8', 'winxp'). This parameter is optional, and does not
require an "--os-type" to be specified.
By default, virt-install will attempt to auto detect this value from the install media (currently only supported for URL installs). Autodetection can be disabled with the special value 'none'.
If the special value 'list' is passed, virt-install will print the full list of variant values and exit. The printed format is not a stable interface, DO NOT PARSE IT.
If the special value 'none' is passed, no os variant is recorded and OS autodetection is disabled.
Values for some recent OS options are:
-
- win7 : Microsoft Windows 7
- vista : Microsoft Windows Vista
- winxp64 : Microsoft Windows XP (x86_64)
- winxp : Microsoft Windows XP
- win2k8 : Microsoft Windows Server 2008
- win2k3 : Microsoft Windows Server 2003
- freebsd8 : FreeBSD 8.x
- generic : Generic
- debiansqueeze : Debian Squeeze
- debianlenny : Debian Lenny
- fedora16 : Fedora 16
- fedora15 : Fedora 15
- fedora14 : Fedora 14
- mes5.1 : Mandriva Enterprise Server 5.1 and later
- mandriva2010 : Mandriva Linux 2010 and later
- rhel6 : Red Hat Enterprise Linux 6
- rhel5.4 : Red Hat Enterprise Linux 5.4 or later
- rhel4 : Red Hat Enterprise Linux 4
- sles11 : Suse Linux Enterprise Server 11
- sles10 : Suse Linux Enterprise Server
- ubuntuoneiric : Ubuntu 11.10 (Oneiric Ocelot)
- ubuntunatty : Ubuntu 11.04 (Natty Narwhal)
- ubuntumaverick : Ubuntu 10.10 (Maverick Meerkat)
- ubuntulucid : Ubuntu 10.04 (Lucid Lynx)
- ubuntuhardy : Ubuntu 8.04 LTS (Hardy Heron)
-
Use '--os-variant list' to see the full OS list
-
- --boot=BOOTOPTS
-
Optionally specify the post-install VM boot configuration. This option allows
specifying a boot device order, permanently booting off kernel/initrd with
option kernel arguments, and enabling a BIOS boot menu (requires libvirt
0.8.3 or later)
--boot can be specified in addition to other install options (such as --location, --cdrom, etc.) or can be specified on it's own. In the latter case, behavior is similar to the --import install option: there is no 'install' phase, the guest is just created and launched as specified.
Some examples:
-
- --boot cdrom,fd,hd,network,menu=on
- Set the boot device priority as first cdrom, first floppy, first harddisk, network PXE boot. Additionally enable BIOS boot menu prompt.
- --boot kernel=KERNEL,initrd=INITRD,kernel_args=console=/dev/ttyS0
- Have guest permanently boot off a local kernel/initrd pair, with the specified kernel options.
-
Storage Configuration
- --disk=DISKOPTS
-
Specifies media to use as storage for the guest, with various options. The
general format of a disk string is
--disk opt1=val1,opt2=val2,...
To specify media, the command can either be:
--disk /some/storage/path,opt1=val1
or explicitly specify one of the following arguments:
-
- path
-
A path to some storage media to use, existing or not. Existing media can be
a file or block device. If installing on a remote host, the existing media
must be shared as a libvirt storage volume.
Specifying a non-existent path implies attempting to create the new storage, and will require specifyng a 'size' value. If the base directory of the path is a libvirt storage pool on the host, the new storage will be created as a libvirt storage volume. For remote hosts, the base directory is required to be a storage pool if using this method.
- pool
- An existing libvirt storage pool name to create new storage on. Requires specifying a 'size' value.
- vol
- An existing libvirt storage volume to use. This is specified as 'poolname/volname'.
-
Other available options:
- device
- Disk device type. Value can be 'cdrom', 'disk', or 'floppy'. Default is 'disk'. If a 'cdrom' is specified, and no install method is chosen, the cdrom is used as the install media.
- bus
- Disk bus type. Value can be 'ide', 'scsi', 'usb', 'virtio' or 'xen'. The default is hypervisor dependent since not all hypervisors support all bus types.
- perms
- Disk permissions. Value can be 'rw' (Read/Write), 'ro' (Readonly), or 'sh' (Shared Read/Write). Default is 'rw'
- size
- size (in GB) to use if creating new storage
- sparse
-
whether to skip fully allocating newly created storage. Value is 'true' or
'false'. Default is 'true' (do not fully allocate).
The initial time taken to fully-allocate the guest virtual disk (sparse=false) will be usually by balanced by faster install times inside the guest. Thus use of this option is recommended to ensure consistently high performance and to avoid I/O errors in the guest should the host filesystem fill up.
- cache
- The cache mode to be used. The host pagecache provides cache memory. The cache value can be 'none', 'writethrough', or 'writeback'. 'writethrough' provides read caching. 'writeback' provides read and write caching.
- format
-
Image format to be used if creating managed storage. For file volumes, this
can be 'raw', 'qcow2', 'vmdk', etc. See format types in
<http://libvirt.org/storage.html> for possible values. This is often
mapped to the driver_type value as well.
With libvirt 0.8.3 and later, this option should be specified if reusing and existing disk image, since libvirt does not autodetect storage format as it is a potential security issue. For example, if reusing an existing qcow2 image, you will want to specify format=qcow2, otherwise the hypervisor may not be able to read your disk image.
- driver_name
- Driver name the hypervisor should use when accessing the specified storage. Typically does not need to be set by the user.
- driver_type
- Driver format/type the hypervisor should use when accessing the specified storage. Typically does not need to be set by the user.
- io
- Disk IO backend. Can be either ``threads'' or ``native''.
- error_policy
- How guest should react if a write error is encountered. Can be one of ``stop'', ``none'', or ``enospace''
- serial
- Serial number of the emulated disk device. This is used in linux guests to set /dev/disk/by-id symlinks. An example serial number might be: WD-WMAP9A966149
-
See the examples section for some uses. This option deprecates "--file", "--file-size", and "--nonsparse".
-
- --filesystem
-
Specifies a directory on the host to export to the guest. The most simple
invocation is:
--filesystem /source/on/host,/target/point/in/guest
Which will work for recent QEMU and linux guest OS or LXC containers. For QEMU, the target point is just a mounting hint in sysfs, so will not be automatically mounted.
The following explicit options can be specified:
-
- type
- The type or the source directory. Valid values are 'mount' (the default) or 'template' for OpenVZ templates.
- mode
- The access mode for the source directory from the guest OS. Only used with QEMU and type=mount. Valid modes are 'passthrough' (the default), 'mapped', or 'squash'. See libvirt domain XML documentation for more info.
- source
- The directory on the host to share.
- target
- The mount location to use in the guest.
-
- --nodisks
- Request a virtual machine without any local disk storage, typically used for running 'Live CD' images or installing to network storage (iSCSI or NFS root).
- -f DISKFILE, --file=DISKFILE
- This option is deprecated in favor of "--disk path=DISKFILE".
- -s DISKSIZE, --file-size=DISKSIZE
- This option is deprecated in favor of "--disk ...,size=DISKSIZE,..."
- --nonsparse
- This option is deprecated in favor of "--disk ...,sparse=false,..."
Networking Configuration
- -w NETWORK, --network=NETWORK,opt1=val1,opt2=val2
-
Connect the guest to the host network. The value for "NETWORK" can take
one of 3 formats:
-
- bridge=BRIDGE
- Connect to a bridge device in the host called "BRIDGE". Use this option if the host has static networking config & the guest requires full outbound and inbound connectivity to/from the LAN. Also use this if live migration will be used with this guest.
- network=NAME
- Connect to a virtual network in the host called "NAME". Virtual networks can be listed, created, deleted using the "virsh" command line tool. In an unmodified install of "libvirt" there is usually a virtual network with a name of "default". Use a virtual network if the host has dynamic networking (eg NetworkManager), or using wireless. The guest will be NATed to the LAN by whichever connection is active.
- user
- Connect to the LAN using SLIRP. Only use this if running a QEMU guest as an unprivileged user. This provides a very limited form of NAT.
-
If this option is omitted a single NIC will be created in the guest. If there is a bridge device in the host with a physical interface enslaved, that will be used for connectivity. Failing that, the virtual network called "default" will be used. This option can be specified multiple times to setup more than one NIC.
Other available options are:
- model
- Network device model as seen by the guest. Value can be any nic model supported by the hypervisor, e.g.: 'e1000', 'rtl8139', 'virtio', ...
- mac
- Fixed MAC address for the guest; If this parameter is omitted, or the value "RANDOM" is specified a suitable address will be randomly generated. For Xen virtual machines it is required that the first 3 pairs in the MAC address be the sequence '00:16:3e', while for QEMU or KVM virtual machines it must be '52:54:00'.
-
- --nonetworks
- Request a virtual machine without any network interfaces.
- -b BRIDGE, --bridge=BRIDGE
- This parameter is deprecated in favour of "--network bridge=bridge_name".
- -m MAC, --mac=MAC
- This parameter is deprecated in favour of "--network NETWORK,mac=12:34..."
Graphics Configuration
If no graphics option is specified, "virt-install" will default to '--graphics vnc' if the DISPLAY environment variable is set, otherwise '--graphics none' is used.- --graphics TYPE,opt1=arg1,opt2=arg2,...
-
Specifies the graphical display configuration. This does not configure any
virtual hardware, just how the guest's graphical display can be accessed.
Typically the user does not need to specify this option, virt-install will
try and choose a useful default, and launch a suitable connection.
General format of a graphical string is
--graphics TYPE,opt1=arg1,opt2=arg2,...
For example:
--graphics vnc,password=foobar
The supported options are:
-
- type
-
The display type. This is one of:
vnc
Setup a virtual console in the guest and export it as a VNC server in the host. Unless the "port" parameter is also provided, the VNC server will run on the first free port number at 5900 or above. The actual VNC display allocated can be obtained using the "vncdisplay" command to "virsh" (or virt-viewer(1) can be used which handles this detail for the use).
sdl
Setup a virtual console in the guest and display an SDL window in the host to render the output. If the SDL window is closed the guest may be unconditionally terminated.
spice
Export the guest's console using the Spice protocol. Spice allows advanced features like audio and USB device streaming, as well as improved graphical performance.
Using spice graphic type will work as if those arguments were given:
--video qxl --channel spicevmc
none
No graphical console will be allocated for the guest. Fully virtualized guests (Xen FV or QEmu/KVM) will need to have a text console configured on the first serial port in the guest (this can be done via the --extra-args option). Xen PV will set this up automatically. The command 'virsh console NAME' can be used to connect to the serial device.
- port
- Request a permanent, statically assigned port number for the guest console. This is used by 'vnc' and 'spice'
- tlsport
- Specify the spice tlsport.
- listen
- Address to listen on for VNC/Spice connections. Default is typically <IP_ADDRESS> (localhost only), but some hypervisors allow changing this globally (for example, the qemu driver default can be changed in /etc/libvirt/qemu.conf). Use <IP_ADDRESS> to allow access from other machines. This is use by 'vnc' and 'spice'
- keymap
- Request that the virtual VNC console be configured to run with a specific keyboard layout. If the special value 'local' is specified, virt-install will attempt to configure to use the same keymap as the local system. A value of 'none' specifically defers to the hypervisor. Default behavior is hypervisor specific, but typically is the same as 'local'. This is used by 'vnc'
- password
- Request a VNC password, required at connection time. Beware, this info may end up in virt-install log files, so don't use an important password. This is used by 'vnc' and 'spice'
- passwordvalidto
-
Set an expiration date for password. After the date/time has passed,
all new graphical connections are denyed until a new password is set.
This is used by 'vnc' and 'spice'
The format for this value is YYYY-MM-DDTHH:MM:SS, for example 2011-04-01T14:30:15
-
- --vnc
- This option is deprecated in favor of "--graphics vnc,..."
- --vncport=VNCPORT
- This option is deprecated in favor of "--graphics vnc,port=PORT,..."
- --vnclisten=VNCLISTEN
- This option is deprecated in favor of "--graphics vnc,listen=LISTEN,..."
- -k KEYMAP, --keymap=KEYMAP
- This option is deprecated in favor of "--graphics vnc,keymap=KEYMAP,..."
- --sdl
- This option is deprecated in favor of "--graphics sdl,..."
- --nographics
- This option is deprecated in favor of "--graphics none"
- --noautoconsole
- Don't automatically try to connect to the guest console. The default behaviour is to launch a VNC client to display the graphical console, or to run the "virsh" "console" command to display the text console. Use of this parameter will disable this behaviour.
Virtualization Type options
Options to override the default virtualization type choices.- -v, --hvm
- Request the use of full virtualization, if both para & full virtualization are available on the host. This parameter may not be available if connecting to a Xen hypervisor on a machine without hardware virtualization support. This parameter is implied if connecting to a QEMU based hypervisor.
- -p, --paravirt
- This guest should be a paravirtualized guest. If the host supports both para & full virtualization, and neither this parameter nor the "--hvm" are specified, this will be assumed.
- --container
- This guest should be a container type guest. This option is only required if the hypervisor supports other guest types as well (so for example this option is the default behavior for LXC and OpenVZ, but is provided for completeness).
- --virt-type
- The hypervisor to install on. Example choices are kvm, qemu, xen, or kqemu. Availabile options are listed via 'virsh capabilities' in the <domain> tags.
- --accelerate
- Prefer KVM or KQEMU (in that order) if installing a QEMU guest. This behavior is now the default, and this option is deprecated. To install a plain QEMU guest, use '--virt-type qemu'
- --noapic
- Force disable APIC for the guest.
- --noacpi
- Force disable ACPI for the guest.
Device Options
- --host-device=HOSTDEV
-
Attach a physical host device to the guest. Some example values for HOSTDEV:
- --soundhw MODEL
-
Attach a virtual audio device to the guest. MODEL specifies the emulated
sound card model. Possible values are ich6, ac97, es1370, sb16, pcspk,
or default. 'default' will be AC97 if the hypervisor supports it,
otherwise it will be ES1370.
This deprecates the old boolean --sound model (which still works the same as a single '--soundhw default')
- --watchdog MODEL[,action=ACTION]
-
Attach a virtual hardware watchdog device to the guest. This requires a
daemon and device driver in the guest. The watchdog fires a signal when
the virtual machine appears to hung. ACTION specifies what libvirt will do
when the watchdog fires. Values are
-
MODEL is the emulated device model: either i6300esb (the default) or ib700. Some examples:
Use the recommended settings:
--watchdog default
Use the i6300esb with the 'poweroff' action
--watchdog i6300esb,action=poweroff
- --parallel=CHAROPTS
- --serial=CHAROPTS
-
Specifies a serial device to attach to the guest, with various options. The
general format of a serial string is
--serial type,opt1=val1,opt2=val2,...
--serial and --parallel devices share all the same options, unless otherwise noted. Some of the types of character device redirection are:
-
- --serial pty
- Pseudo TTY. The allocated pty will be listed in the running guests XML description.
- --serial dev,path=HOSTPATH
- Host device. For serial devices, this could be /dev/ttyS0. For parallel devices, this could be /dev/parport0.
- --serial file,path=FILENAME
- Write output to FILENAME.
- --serial pipe,path=PIPEPATH
- Named pipe (see pipe(7))
- --serial tcp,host=HOST:PORT,mode=MODE,protocol=PROTOCOL
-
TCP net console. MODE is either 'bind' (wait for connections on HOST:PORT)
or 'connect' (send output to HOST:PORT), default is 'connect'. HOST defaults
to '<IP_ADDRESS>', but PORT is required. PROTOCOL can be either 'raw' or 'telnet'
(default 'raw'). If 'telnet', the port acts like a telnet server or client.
Some examples:
Connect to localhost, port 1234:
--serial tcp,host=:1234
Wait for connections on any address, port 4567:
--serial tcp,host=<IP_ADDRESS>:4567,mode=bind
Wait for telnet connection on localhost, port 2222. The user could then connect interactively to this console via 'telnet localhost 2222':
--serial tcp,host=:2222,mode=bind,protocol=telnet
- --serial udp,host=CONNECT_HOST:PORT,bind_host=BIND_HOST:BIND_PORT
-
UDP net console. HOST:PORT is the destination to send output to (default
HOST is '<IP_ADDRESS>', PORT is required). BIND_HOST:BIND_PORT is the optional
local address to bind to (default BIND_HOST is <IP_ADDRESS>, but is only set if
BIND_PORT is specified). Some examples:
Send output to default syslog port (may need to edit /etc/rsyslog.conf accordingly):
--serial udp,host=:514
Send output to remote host <IP_ADDRESS>, port 4444 (this output can be read on the remote host using 'nc -u -l 4444'):
--serial udp,host=<IP_ADDRESS>:4444
- --serial unix,path=UNIXPATH,mode=MODE
- Unix socket, see unix(7). MODE has similar behavior and defaults as --serial tcp,mode=MODE
-
- --channel
-
Specifies a communication channel device to connect the guest and host
machine. This option uses the same options as --serial and --parallel
for specifying the host/source end of the channel. Extra 'target' options
are used to specify how the guest machine sees the channel.
Some of the types of character device redirection are:
-
- --channel SOURCE,target_type=guestfwd,target_address=HOST:PORT
- Communication channel using QEMU usermode networking stack. The guest can connect to the channel using the specified HOST:PORT combination.
- --channel SOURCE,target_type=virtio[,name=NAME]
- Communication channel using virtio serial (requires 2.6.34 or later host and guest). Each instance of a virtio --channel line is exposed in the guest as /dev/vport0p1, /dev/vport0p2, etc. NAME is optional metadata, and can be any string, such as org.linux-kvm.virtioport1. If specified, this will be exposed in the guest at /sys/class/virtio-ports/vport0p1/NAME
- --channel spicevmc,target_type=virtio[,name=NAME]
- Communication channel for QEMU spice agent, using virtio serial (requires 2.6.34 or later host and guest). NAME is optional metadata, and can be any string, such as the default com.redhat.spice.0 that specifies how the guest will see the channel.
-
- --console
-
Connect a text console between the guest and host. Certain guest and
hypervisor combinations can automatically set up a getty in the guest, so
an out of the box text login can be provided (target_type=xen for xen
paravirt guests, and possibly target_type=virtio in the future).
Example:
-
- --console pty,target_type=virtio
- Connect a virtio console to the guest, redirected to a PTY on the host. For supported guests, this exposes /dev/hvc0 in the guest. See http://fedoraproject.org/wiki/Features/VirtioSerial for more info. virtio console requires libvirt 0.8.3 or later.
-
- --video=VIDEO
- Specify what video device model will be attached to the guest. Valid values for VIDEO are hypervisor specific, but some options for recent kvm are cirrus, vga, qxl, or vmvga (vmware).
- --smartcard=MODE[,OPTS]
-
Configure a virtual smartcard device.
Mode is one of host, host-certificates, or passthrough. Additional options are:
-
An example invocation:
-
See "http://libvirt.org/formatdomain.html#elementsSmartcard" for complete details.
-
Miscellaneous Options
- --autostart
- Set the autostart flag for a domain. This causes the domain to be started on host boot up.
- --print-xml
-
If the requested guest has no install phase (--import, --boot), print the
generated XML instead of defining the guest. By default this WILL do storage
creation (can be disabled with --dry-run).
If the guest has an install phase, you will need to use --print-step to specify exactly what XML output you want. This option implies --quiet.
- --print-step
- Acts similarly to --print-xml, except requires specifying which install step to print XML for. Possible values are 1, 2, 3, or all. Stage 1 is typically booting from the install media, and stage 2 is typically the final guest config booting off hardisk. Stage 3 is only relevant for windows installs, which by default have a second install stage. This option implies --quiet.
- --noreboot
- Prevent the domain from automatically rebooting after the install has completed.
- --wait=WAIT
- Amount of time to wait (in minutes) for a VM to complete its install. Without this option, virt-install will wait for the console to close (not neccessarily indicating the guest has shutdown), or in the case of --noautoconsole, simply kick off the install and exit. Any negative value will make virt-install wait indefinitely, a value of 0 triggers the same results as noautoconsole. If the time limit is exceeded, virt-install simply exits, leaving the virtual machine in its current state.
- --force
- Prevent interactive prompts. If the intended prompt was a yes/no prompt, always say yes. For any other prompts, the application will exit.
- --dry-run
- Proceed through the guest creation process, but do NOT create storage devices, change host device configuration, or actually teach libvirt about the guest. virt-install may still fetch install media, since this is required to properly detect the OS to install.
- --prompt
- Specifically enable prompting for required information. Default prompting is off (as of virtinst 0.400.0)
- --check-cpu
- Check that the number virtual cpus requested does not exceed physical CPUs and warn if they do.
- -q, --quiet
- Only print fatal error messages.
- -d, --debug
- Print debugging information to the terminal when running the install process. The debugging information is also stored in "$HOME/.virtinst/virt-install.log" even if this parameter is omitted.
 Resource usage is capped at 512 MB of ram and 2 host cpus:
# virt-install \ --connect lxc:/// \ --name httpd_guest \ --ram 512 \ --vcpus 2 \ --init /usr/bin/httpd
Install a paravirtualized Xen guest, 500 MB of RAM, a 5 GB of disk, and Fedora Core 6 from a web server, in text-only mode, with old style --file options:
# virt-install \ --paravirt \ --name demo \ --ram 500 \ --file /var/lib/xen/images/demo.img \ --file-size 6 \ --graphics none \ --location http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os/
Create a guest from an existing disk image 'mydisk.img' using defaults for the rest of the options.
# virt-install \ --name demo --ram 512 --disk /home/user/VMs/mydisk.img --import
Test a custom kernel/initrd using an existing disk image, manually specifying a serial device hooked to a PTY on the host machine.
# virt-install \ --name mykernel --ram 512 --disk /home/user/VMs/mydisk.img --boot kernel=/tmp/mykernel,initrd=/tmp/myinitrd,kernel_args="console=ttyS0" --serial pty
AUTHORS
Written by Daniel P. Berrange, Hugh Brock, Jeremy Katz, Cole Robinson and a team of many other contributors. See the AUTHORS file in the source distribution for the complete list of credits.BUGS
Please see http://virt-manager.org/page/BugReportingCOPYRIGHT
Copyright (C) 2006-2011 Red Hat, Inc, and various contributors. This is free software. You may redistribute copies of it under the terms of the GNU General Public License "http://www.gnu.org/licenses/gpl.html". There is NO WARRANTY, to the extent permitted by law.SEE ALSO
virsh(1), "virt-clone(1)", "virt-manager(1)", the project website "http://virt-manager.org"
Index
This document was created by man2html, using the manual pages.
Time: 05:29:12 GMT, December 24, 2015


README
GeoInfo
City
module
GeoInfo
Defined in:
city.cr
geoinfo.cr
Constant Summary
ADDRESS
=
"https://geo-info.co/"


This file is just to illustrate the folder structure. You can delete the folder content and copy your wordpress code base in it.


Mumbai
kolkata
delhi
chennai
west bengal
maharastra
Krables
Market
Gurugram
Mumbai
kolkata
delhi
chennai
west bengal
maharastra
electronics
food
home decoration
meal
new godds
maharastra
1800-000-0000
Offers
Help
3
My Account
My Orders
My Wishlist
My Cart
My Wallet
My Address
Login
Logout
Home
cat1
My Account
My Orders
My Wishlist
My Cart
My Wallet
My Address
cat2
My Account
My Orders
My Wishlist
My Cart
My Wallet
My Address
cat3
My Account
My Orders
My Wishlist
My Cart
My Wallet
My Address
cat4
My Account
My Orders
My Wishlist
My Cart
My Wallet
My Address
cat5
My Account
My Orders
My Wishlist
My Cart
My Wallet
My Address
cat1
My Account
My Orders
My Wishlist
My Cart
My Wallet
My Address
cat2
My Account
My Orders
My Wishlist
My Cart
My Wallet
My Address
cat3
My Account
My Orders
My Wishlist
My Cart
My Wallet
My Address
cat4
My Account
My Orders
My Wishlist
My Cart
My Wallet
My Address
cat5
My Account
My Orders
My Wishlist
My Cart
My Wallet
My Address
Cart
Home
Cat 1
fdg
fdg
fdg
Cat 1
fdg
fdgg
fdg
Home
/
My Orders
1
Delivery Address
Home
Office
Other
Name*
Email*
Flat / House / Office No.*
Street / Society / Office Name*
Pincode*
Locality*
Save
Next
2
Delivery Time & Date
Today
Tomorrow
8.00AM - 10.00AM
10.00AM - 12.00PM
12.00PM - 2.00PM
2.00PM - 4.00PM
4.00PM - 6.00PM
Proceed To Pay
3
Payment
Cash on Delivery
Credit / Debit Card
Place Order
Order Summary
4% OFF
Product Title Here
$15
$18
4% OFF
Product Title Here
$15
$18
4% OFF
Product Title Here
$15
$18
Gambo Super Market
$15
Delivery Charges
$1
Total Saving
$3
Total
$16
Secure Checkout
Have A Promocode?
Apply


We are a Astrophysics team under SSERD IPD working on finding a relation that accounts for the mass transfer from a companion star to a black hole, which would help us conclude the mass conservation and find if there is any discrepancy, which we call as the ghost mass and use reference systems for validation of ghost mass problem and accounting for the discrepancy using models/computation.
Having been inspired from the Cygnus-X1 system, the goal was to set up a similar binary system model and analyse some fundamental properties. We introduce a hypothetical binary system that consists of a stellar mass black hole, and an intermediate mass main sequence star. The base model builds up on the fact that mass from the star transfers to the black-hole via accretion. This leads to the inclusion of different types of mass transfers that take place in this whole process: Mass transfers due to stellar winds, Roche lobe overflows, advective outflows from the accretion disk, and astrophysical jets.
Upon closer look, these mass transfers are actually the cause of mass losses that occurs during the transfer from a star to a black-hole. So, not all the mass is conserved. This mass discrepancy we term as Ghost Mass. The mass gained by the black-hole is not equivalent to the mass lost by the star.
Our work in summary started off with intense literature review of what systems we could take into consideration, and what mass transfers we could account for. Having singled those out, we then proceeded with our analysis in the following manner:
We obtained the following results for the 3 systems:
And a simulation of a binary system in Unity made by our Adrian boii (Adhiraj)
We are really enthusiastic and hopeful to talk with you and exchange ideas, recieve feedback and answer queries. Please feel free to drop a message using any of the mediums below. It was nice meeting you. Themks xD


Created by Charlotte Verweij
Click below to jump to a section
This guide is a quick-reference guide with many tips and tricks enabling you to start using the OSMAND app very quickly
Many of the tips given will hopefully be a good way to learn about how to use the application. So that you can use it by yourself
The OSMAND application
The tips here serve as a general guidance and depending on the context of usage may require a different approach.
Each page will provide a tip and a brief description. If you want to find out more about a particular tip then press down on your keyboard or swipe. Here you can find more information and links to resources providing further reading and learning materials.
Text here will indicate when you can press down
When navigating downwards the resulting pages will contain additional information and learning materials about the tip.
Ask yourself: Will I be collecting a lot of data? If the answer is “no”, then this application should be used. But if the answer is “yes” then it’s advised to use an open data kit. For more information about the open data kit click here, or ask your attendant.
The second question you need to ask yourself is: “How frequently will the application need to update?” If the update frequency is once per month, then you can use this application. If the update frequency is several times per hour as is the case for Haiti where we added thousands of buildings in the past week, then you have to use OSM live. Note, that costs are involved on a monthly basis in the order of 1.20 dollars.
If you want the application to use your current location, you will have to turn on the GPS functionality on your device. Note, that it is not required to use GPS. You can also just search for the location in the application.
GPS icon
In the app store search for the app called OSMAND. After answering several questions, you can download the application.
To edit OpenStreetMap (OSM), follow these instructions: instruction. In order to upload the data back into OSM you will need an OSM account. Credentials should be set in the application. You can make an OSM account here: made an account. If you want to use the data from your OSM account you will have to log-in in OSM. Select Plugins and then select OSM editing. Press the down-arrow button for more details.
First click on the menu shown in the bottom left corner of the screen. Search for the “Plugins” item and click it. Then scroll down and search for the “OSM editing” item. Press the down-arrow button for more details.
First you have to turn on the OSM editing by clicking on its icon. Then you have to click on the three dots and select the “option settings”. To use OSM, you will need to log-in with your OSM account.
In the bottom left corner of the screen you will find an icon with three lines. By clicking on that icon a menu will appear. The menu contains many options to select from.
One of the many options in the menu is to download maps. Click on the item “Download maps”.
Use the Search bar to search for your map. For now we are searching for Haiti. A number of search results will appear. Select the map of your interest by clicking on the arrow icon pointing downwards.
First go back to the menu by clicking on the arrow shown on the top left of the screen. Then from the menu select the option “OSM Live”.
Now that we have downloaded the map, it’s time to add the map. Simply click on the ‘+ ‘ symbol in OSM Live. This will add the map. live. With doing that the map is there.
Now that we have added the map, we can view the map. You will see that your downloaded map is shown in green. In order to view the world map, see the next step.
In order to view the world map, go back to the menu and click on “Download maps”. Scroll downwards until you find the item “World overview map”.
An easy way to find your location, is to turn on GPS on your smartphone. That will automatically indicate your location. In case you do not want to use GPS, then go to the next step.
Another way to navigate is to go to your location. After locating that manually, click the location and do not move the map. Soon an orange marker will appear.
You will find your location and are now ready to navigate by clicking on the blue arrow appearing in a white box.
In order to navigate to a destination, select your means of transport.
The next step is to select your departure location. You can do this by clicking on the small arrow icon. Several different options are then presented to you. If GPS is turned on, you can select “my position”. In case no GPS is used, the options “select map” or “address” are shown.
The final step is to select your destination location. You can fill-in the address or select a location on the map.
In case you have done this before you can skip this step and continue with the next step. Otherwise, go to the menu item icon, select item “Plugins” and then click on the icon for the item “OSM editing”.
First select the map you want to add the data to. Maybe it’s a map you downloaded previously. If you zoom in on the map you will be able to see more information about the map and its orange markers.
First you have to look for the location where you want to add data to. You can use GPS for this, or simply search for it manually. After finding the location, don’t move the map. Soon an orange marker will appear.
When an orange marker appears, click on the three dots shown in the bottom right corner of the screen.
By clicking on the three dots a list of options will appear. Click on the item “Create POI”. If you don't have the option “Create POI”, press down.
In case the item “Create POI” is not listed, go back to the menu, click on “Plugins” and then click on “OSM editing”.
After clicking on the item “Create POI”, assign a name to the location. You will need to do this for each location that you add to the map.
It is important to add tags to your locations, so that all viewers know which locations were added by you. To do that first go to the “Advanced” tab, which is shown in the white bar of the screen.
Now you are in the “Advanced” tab. First click on “Add Tags” and then add your tags.
In this screen you can add tags. Tags have a name and a value. First enter a name and then a value. Examples of tags that are used in Haiti, are:
Please follow these steps to learn how to import GPX files into OSMAND.
You have now completed all the necessary steps. Did you have any difficulty with any of the instructions? If not, great! If yes, then simply re-visit those sections and repeat the instructions.


Seeing in high definition
by Manila Standard LifestyleItalian eyewear brand Polar, known for its polarized lenses, is now available in the country at Sarabia Optical.
The brand promises that glare, which happens when light hits a smooth, reflective surface, will be a thing in the past with its lenses with polarized filters. The lenses offer crisp visual experience with more natural and vivid colors, with a perfect amount of contrast, accurate detail perception, and better depth perception.
Polar lenses also have an anti-scratch coating as well as oil- and water-resistant coating to enhance each pair’s durability. They also feature a UVA, UVB, and UVC protection filter perfect for those who love to explore.
It also offers a variety of frames and lenses in different tints and colors, as well as bold frame shapes and sizes—from the famous aviators to eccentric hexagons.
Polar is available at Sarabia Optical nationwide.


--- layout: page title: About permalink: /about/ --- This is the base Jekyll theme. You can find out more info about customizing your Jekyll theme, as well as basic Jekyll usage documentation at [jekyllrb.com](http://jekyllrb.com/) You can find the source code for the Jekyll new theme at: [github.com/jglovier/jekyll-new](https://github.com/jglovier/jekyll-new) You can find the source code for Jekyll at [github.com/jekyll/jekyll](https://github.com/jekyll/jekyll)
Testing the type scale.
This is the base Jekyll theme. You can find out more info about customizing your Jekyll theme, as well as basic Jekyll usage documentation at Jekyll. This is the base Jekyll theme. You can find out more info about customizing your Jekyll theme, as well as basic Jekyll usage documentation at


Safari IT Books Language Constructs Functional Programming Haskell Safari IT Books Programming Programming Programming Bryan O'Sullivan Donald Bruce Stewart John Goerzen O'Reilly Media, Inc. Real World Haskell, 1st Edition1.5. ListsA list is surrounded by square brackets; the elements are separated by
commas: ghci> [1, 2, 3]
[1,2,3]
NOTE
Some languages permit the last element in a list to be
followed by an optional trailing comma before a closing bracket, but
Haskell doesn't allow this. If you leave in a trailing comma (e.g.,
[1,2,]), you'll get a parse error. A list can be of any length. An empty list is written
[]: ghci> []
[]
ghci> ["foo", "bar", "baz", "quux", "fnord", "xyzzy"]
["foo","bar","baz","quux","fnord","xyzzy"] All elements of a list must be of the same type. Here, we
violate this rule. Our list starts with two Bool values, but
ends with a string: ghci> [True, False, "testing"]
<interactive>:1:14:
Couldn't match expected type `Bool' against inferred type `[Char]'
In the expression: "testing"
In the expression: [True, False, "testing"]
In the definition of `it': it = [True, False, "testing"]
Once again, ghci's
error message is verbose, but it's simply telling us that there is no way
to turn the string into a Boolean value, so the list expression isn't
properly typed. If we write a series of elements using
enumeration notation, Haskell will fill in the contents of the list for us: ghci> [1..10]
[1,2,3,4,5,6,7,8,9,10]
Here, the ..
characters denote an enumeration. We can only use
this notation for types whose elements we can enumerate. It makes no sense
for text strings, for instance—there is not any sensible, general way to
enumerate ["foo".."quux"]. By the way, notice that the preceding use of range
notation gives us a closed interval; the list
contains both endpoints. When we write an enumeration, we can optionally specify
the size of the step to use by providing the first two elements, followed
by the value at which to stop generating the enumeration: ghci> [1.0,1.25..2.0]
[1.0,1.25,1.5,1.75,2.0]
ghci> [1,4..15]
[1,4,7,10,13]
ghci> [10,9..1]
[10,9,8,7,6,5,4,3,2,1] In the latter case, the list is quite sensibly missing the
endpoint of the enumeration, because it isn't an element of the series we
defined. We can omit the endpoint of an enumeration. If a type
doesn't have a natural "upper bound," this will produce
values indefinitely. For example, if you type [1..] at the ghci prompt, you'll have to interrupt or kill
ghci to stop it from printing an
infinite succession of ever-larger numbers. If you are tempted to do this,
hit C to halt the enumeration. We will find later on that infinite lists
are often useful in Haskell. | Beware of enumerating floating-point numbers Here's a nonintuitive bit of behavior: ghci> [1.0..1.8]
[1.0,2.0]
Behind the scenes, to avoid floating-point roundoff
problems, the Haskell implementation enumerates from 1.0 to
1.8+0.5. Using enumeration notation over floating-point numbers
can pack more than a few surprises, so if you use it at all, be careful.
Floating-point behavior is quirky in all programming languages; there is
nothing unique to Haskell here. |
|
1.5.1. Operators on ListsThere are two ubiquitous operators for working with
lists. We concatenate two lists using the (++) operator: ghci> [3,1,3] ++ [3,7]
[3,1,3,3,7]
ghci> [] ++ [False,True] ++ [True]
[False,True,True] More basic is the (:) operator, which adds an element to the
front of a list (this is pronounced "cons" [short for
"construct"]): ghci> 1 : [2,3]
[1,2,3]
ghci> 1 : []
[1] You might be tempted to try writing
[1,2]:3 to add an element to the end of a list, but
ghci will reject this with an error
message, because the first argument of (:) must be an element, and the second must
be a list.
|