To run Xen and a single OS from a binary release you need install no extra packages. To build Xen, XenLinux and documentation from source you will need: make, libncurses5-dev, libncurses5, gcc, libc6-dev, zlib1g-dev, python, python-dev, python-twisted, openssl, openssl-dev, bridge-utils, iproute, libcurl3, libcurl3-dev, bzip2, module-init-tools, latex, latex2html, transfig, and tgif.

Xen is a virtual machine monitor (VMM) for x86-compatible computers. Xen can securely execute multiple virtual machines, each running its own OS, on a single physical system with close-to-native performance.

Once the base system has been installed, you can complete the installation of your Debian GNU/Linux system by accessing packages on any (or several) of these media: dselect, Debian's user-interface program to its package system. (This will help you mount the device containing the Debian package files (if necessary), and then guide you through the selection of packages and their installation on your system.) Or, use dpkg directly to control the installation of individual packages.

Besides a web server (such as apache) you need perl and libxml-parser-perl. If you wish to use the history feature you must also install librrds-perl.

Please see http://www.debian-multimedia.org/ for the latest details. Packages for stable (etch), testing (lenny) and unstable (sid) are provided.

For more detailed description on this, read the New Maintainers' Guide, available in the maint-guide package, or at http://www.debian.org/doc/devel-manuals#maint-guide. previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ 6 ] [ 7 ] [ 8 ] [ 9 ] [ 10 ] [ 11 ] [ 12 ] [ 13 ] [ 14 ] [ 15 ] [ 16 ] [ next ]

If you are running Mac OS X, Cernlib is packaged under Fink by Remi Mommsen, with a small set of patches, mainly to allow the build infrastructure to recognize OS X. The packaging is split up into cernlib, a core set of Cernlib applications; cernlib-dev, the basic libraries and header files; cernlib-geant321, GEANT 3; cernlib-mclibs, the Monte Carlo libraries; and cernlib-paw++, the Paw++ program. These packages may only be available for OS X on PowerPC-based hardware.

There is a tool called "Alien" which converts Debian packages (.deb) to RedHat packages (.rpm) and vice-versa. See http://kitenet.net/programs/alien/ It would be advisable that you do not install packages which have been converted from other formats on your RedHat system. The reason being that no two Linux distributions follow the same conventions with respect to the directory structure and file locations. You can most certaily find RPMS for most packages at http://www.rpmfind.net

Xen is Open Source, and is released under terms of the GNU General Public License. Operating systems or other applications written to use Xen's hypercall interface are not derived works of Xen, hence may be licensed differently.

Here you go: http://linux-vserver.derjohn.de/ . There is also some stuff on backports.org, but my kernels are always 'devel' branch.

Yes indeed, that's part of the design of the distro. For versions up to and including 2.0, you need to enable a repository like the following: in /etc/apt/sources.list.d/64studio.list where 'uk' is your local Debian mirror, listed here: http://www.debian.org/mirror/list

Debian created by the Debian project, is a widely used distribution of free software developed through the collaboration of volounteers from around the world.

Everything you need to get started is in googleapi.jar. Advanced users may prefer to use their own Java SOAP implementations and use the WSDL file to generate client code.

To achieve such high performance, Xen requires that OSes are ported to run on it. See the Current status of OS ports The paravirtualized approach we use to get such high performance has not been usable directly for Windows to date. However Xen 3.0 added Intel VT-x support to enable the running of unmodified guest operating systems, including Windows XP & 2003 Server, using hardware virtualization technology. Xen 3.0.2 and later support AMD Pacifica technology as well.

There is both paid and volunteer support available for Xen. Commercial support is provided by Citrix Systems, Inc. (XenSource, Inc.), the proprietors of this wiki. Volunteer support is available via the Xen mailing lists and on Internet Relay Chat (IRC): channel ##xen ("about Xen") on irc.freenode.net is a slightly larger, unofficial channel which also provides support

If you want to compile QEMU from source, then you must. This is required. If you are using a binary package however, then it's not necessary (but it doesn't hurt either).

Xen currently runs only on the x86 architecture, requiring a "P6" or newer processor (that's any Intel or AMD x86 CPU purchased in the last five years). Multiprocessor machines are supported, including basic support for Hyper-Threading (SMT). Support for x86/64 is available since Xen 3.0. In addition a port to the IA64 architecture is approaching completion. We hope to add other architectures such as PPC and ARM in due course.

Debian GNU/Linux is a particular distribution of the Linux operating system, and numerous packages that run on it. In principle, users could obtain the Linux kernel via the Internet or from elsewhere, and compile it themselves. They could then obtain source code for many applications in the same way, compile the programs, then install them into their systems. For complicated programs, this process can be not only time-consuming but error-prone.

This is stable and well tested software, it changes if major security or usability fixes are incorporated. This is where packages that will be released as the next 'stable' are placed; they've had some testing in unstable but they may not be completely fit for release yet. This distribution is updated more often than 'stable', but not more often than 'unstable'. This is the version currently under development; it is updated continuously.

You can get the installation disks by downloading the appropriate files from one of the Debian mirrors. The installation system files are separated in subdirectories of dists/stable/main directory, and the names of these subdirectories correspond to your architecture like this: disks-arch (arch is "i386", "sparc", etc, check the site for an exact list).

Linux supports the ISO 9660 (CD-ROM) file system with Rock Ridge extensions (formerly known as "High Sierra". Several vendors provide Debian GNU/Linux in this format. Warning: When installing from CD-ROM, it is usually not a good idea to choose dselect's cdrom access method. This method is usually very slow.

Debian developers communicate with other Linux distribution creators in an effort to maintain binary compatibility across Linux distributions. Most commercial Linux products run as well under Debian as they do on the system upon which they were built. Debian GNU/Linux adheres to the Linux Filesystem Hierarchy Standard. However, there is room for interpretation in some of the rules within this standard, so there may be slight differences between a Debian system and other Linux systems.

Files under the directory /usr/local/ are not under the control of the Debian package management system. Therefore, it is good practice to place the source code for your program in /usr/local/src/. For example, you might extract the files for a package named "foo.tar" into the directory /usr/local/src/foo. After you compile them, place the binaries in /usr/local/bin/, the libraries in /usr/local/lib/, and the configuration files in /usr/local/etc/.

A list of packages which are still needed to be packaged for Debian exists, the Work-Needing and Prospective Packages list. For more details about adding the missing things, see How can I become a Debian software developer?, Section 12.1. Debian Policy requires that such symbolic links (to libfoo.so.x.y.z or similar) are placed in separate, development packages. Those packages are usually named libfoo-dev or libfooX-dev (presuming the library package is named libfooX, and X is a whole number).

In order to make sure that your system has been installed from the real Debian base disks check for the existence of /etc/debian_version file, which contains a single one-line entry giving the version number of the release, as defined by the package base-files.

The software that has been packaged for Debian GNU/Linux is available in one of several directory trees on each Debian mirror site. The dists directory is short for "distributions", and it is the canonical way to access the currently available Debian releases (and pre-releases). DOS utilities for creating boot disks, partitioning your disk drive, compressing/decompressing files, and booting Linux.

There are three distributions, the "stable" distribution, the "testing" distribution, and the "unstable" distribution. The "testing" distribution is sometimes 'frozen' (see What about "testing"? How is it 'frozen'?, Section 5.6.1).

You do not need to worry about installing any special packages. If a package is required and your server does not have it, then the install script will download it from the Internet. If you really want to know what packages it uses, please have a peek at the install script. It uses the yum utility to install packages.