### Install VirtualBox and Prepare System Files

Source: https://www.virtualbox.org/wiki/Setup_Jail

This command installs the virtualbox-ose package within the chroot environment. It also creates an empty /etc/init.d/udev file, which might be a prerequisite or workaround for specific VirtualBox installation steps in certain Debian/Ubuntu versions.

```bash
sudo touch /etc/init.d/udev
sudo apt-get install virtualbox-ose

```

--------------------------------

### Launch VirtualBox GUI

Source: https://www.virtualbox.org/wiki/Setup_Jail

This command starts the VirtualBox graphical user interface. It requires root privileges and is typically run from within the chroot environment after all necessary configurations and installations are complete.

```bash
sudo virtualbox &

```

--------------------------------

### Linux Host: Install and Run VirtualBox

Source: https://www.virtualbox.org/wiki/VBoxInstallAndRun

Guide for setting up VirtualBox on Linux hosts, including kernel module loading, device node creation, and USB pass-through. It also provides steps for updating or cleaning the installation and disabling SELinux if necessary.

```bash
./loadall.sh
./loadall.sh -u
./load.sh
./load.sh -u
/usr/sbin/setenforce 0
```

--------------------------------

### Install Utilities for Bridged Networking

Source: https://www.virtualbox.org/wiki/Setup_Jail

Installs 'uml-utilities' and 'bridge-utils' packages, which provide tools necessary for creating and managing network bridges and TAP interfaces, essential for VirtualBox's bridged networking mode.

```bash
sudo apt-get install uml-utilities bridge-utils

```

--------------------------------

### Install VirtualBox in Chroot

Source: https://www.virtualbox.org/wiki/Setup_Jail_version=1

This command sequence first ensures that the udev initialization script exists and then installs the virtualbox-ose package within the chroot environment using apt-get. This assumes VirtualBox modules have already been built outside the chroot.

```bash
sudo touch /etc/init.d/udev
sudo apt-get install virtualbox-ose
```

--------------------------------

### Windows Host: Install and Run VirtualBox

Source: https://www.virtualbox.org/wiki/VBoxInstallAndRun

Instructions for installing VirtualBox on Windows using an MSI package and for running it directly from the output directory during development. This includes commands for loading/unloading drivers, registering components, and managing VirtualBox services.

```batch
msiexec /i VirtualBox-xxxxx.msi /l* install.log
loadall.cmd
comregister.cmd -u
loadall.cmd -u
pskill VBoxSVC
pskill VBoxSDS
set VBOX_ASSERT=none
set VBOX_LOG=...
set VBOX_LOG_FLAGS=time thread buffered
```

--------------------------------

### Windows Development Environment Setup

Source: https://www.virtualbox.org/wiki/VBoxInstallAndRun_version=1

These commands are used on Windows hosts to load necessary drivers for running VirtualBox directly from the output directory during development. `loadall.cmd` loads all drivers, while `load.cmd` can be used to load only the support driver. Uninstallation is handled by `comregister.cmd -u` and `loadall.cmd -u`.

```batch
loadall.cmd

```

```batch
comregister.cmd -u
loadall.cmd -u
```

--------------------------------

### Create Bridged Networking Scripts

Source: https://www.virtualbox.org/wiki/Setup_Jail_version=1

These commands install necessary utilities for bridged networking (uml-utilities, bridge-utils) and define two bash scripts, vbox-ifup.sh and vbox-ifdown.sh. These scripts manage the attachment and detachment of TAP interfaces to the bridge interface 'br0'.

```bash
sudo apt-get install uml-utilities bridge-utils
cat > vbox-ifup.sh <<EOF
#!/bin/bash
/usr/bin/sudo /sbin/ifconfig $2 up
/usr/bin/sudo /usr/sbin/brctl addif br0 $2
EOF
cat > vbox-ifdown.sh <<EOF
#!/bin/bash
/usr/bin/sudo /usr/sbin/brctl delif br0 $2
/usr/bin/sudo /sbin/ifconfig $2 down
EOF
chmod a+x vbox-ifup.sh vbox-ifdown.sh
```

--------------------------------

### Windows MSI Installation and Logging

Source: https://www.virtualbox.org/wiki/VBoxInstallAndRun_version=1

This snippet shows how to install VirtualBox using an MSI package on Windows hosts and how to enable logging for troubleshooting installation failures. The `msiexec` command with the `/l*` flag is used for logging.

```batch
msiexec /i VirtualBox-xxxxx.msi /l* install.log
```

--------------------------------

### Solaris Host: Install and Load VirtualBox Drivers

Source: https://www.virtualbox.org/wiki/VBoxInstallAndRun

Instructions for manually setting up VirtualBox on Solaris hosts without using an installer. This involves copying VBI interfaces, the vboxdrv driver, and its configuration file, then removing any previous installation and loading the new module.

```bash
cp src/VBox/Runtime/r0drv/solaris/vbi/64/vbi /platform/i86pc/kernel/misc/amd64/vbi
cp src/VBox/Runtime/r0drv/solaris/vbi/32/vbi /platform/i86pc/kernel/misc/vbi
cp out/solaris.amd64/release/bin/vboxdrv /platform/i86pc/kernel/drv/amd64/vboxdrv
cp out/solaris.x86/release/bin/vboxdrv /platform/i86pc/kernel/drv/vboxdrv
cp src/VBox/HostDrivers/Support/solaris/vboxdrv.conf /platform/i86pc/kernel/drv
su
rem_drv vboxdrv
add_drv -m'* 0666 root sys' vboxdrv
ln -s /devices/pseudo/vboxdrv@0:vboxdrv /dev/vboxdrv
```

--------------------------------

### Launch VirtualBox Frontends

Source: https://www.virtualbox.org/wiki/Windows%20build%20instructions_version=76

These are example commands to launch the graphical user interface or headless versions of VirtualBox. They are executed from the output directory where the binaries are compiled.

```batch
VirtualBox.exe
VBoxHeadless.exe
```

--------------------------------

### Building Heirloom-Pkgtools (Shell)

Source: https://www.virtualbox.org/wiki/SolarisCrossCompiler

Builds the heirloom-pkgtools package on the Linux host for creating Solaris packages. This involves setting up the target installation directory and using specific `make` commands with environment variables for installation paths.

```shell
#!/bin/bash
mkdir -p $TARGET/var/spool/pkg
make SHELL=/bin/sh INSTALL=/usr/bin/install ROOT=$TARGET/ VAR=$TARGET/var \
  BINDIR=/bin SBINDIR=/sbin ETCDIR=$TARGET/etc MANDIR=/usr/share/man
make SHELL=/bin/sh INSTALL=/usr/bin/install ROOT=$TARGET/ VAR=$TARGET/var \
  BINDIR=/bin SBINDIR=/sbin ETCDIR=$TARGET/etc MANDIR=/usr/share/man install
```

--------------------------------

### Install Plugin from Source using setup.py

Source: https://www.virtualbox.org/wiki/TracPlugins_action=diff&version=2

Installs a VirtualBox plugin directly from its source code, typically a tarball or a Subversion repository. This requires Python and its setup.py script to be available. This method is useful for development or when pre-compiled packages are not available.

```bash
$ python setup.py install
```

```bash
easy_install http://svn.edgewall.com/repos/trac/plugins/0.12/spam-filter-captcha
```

--------------------------------

### Wiki Processor with Parameters and Nesting

Source: https://www.virtualbox.org/wiki/WikiProcessors_action=diff&version=3

This example illustrates how to pass parameters to Wiki Processors using key-value pairs and demonstrates the ability to nest processor blocks. Parameters like 'style' can include spaces when quoted, and indentation within nested blocks is ignored.

```Wiki
{{{#!td colspan=2 align=center style="border: none"
  '''Example 1''': Inserting raw HTML
}}}
|-----------------------------------------------------------------
{{{#!td style="border: none"
{{{ 
#!html
<h1>This is raw HTML</h1>
}}}
}}}
|-----------------------------------------------------------------
```

```Wiki
{{{#!td colspan=2 align=center style="border: none"
  '''Example 2''': Highlighted Python code in a <div> block with custom style
}}}
|-----------------------------------------------------------------
```

--------------------------------

### Setting Up Installation Directories (Shell)

Source: https://www.virtualbox.org/wiki/SolarisCrossCompiler

Creates the necessary directories for the cross-compilation toolchain and sysroot on the Linux host. These directories will house the compiled tools and Solaris headers/libraries.

```shell
#!/bin/bash
TARGET=$HOME/cross        # Where the tool chain will be installed to
SYSROOT=$TARGET/sysroot   # Where the Solaris headers and libraries will be installed to
mkdir $TARGET
mkdir $SYSROOT
```

--------------------------------

### InterMapTxt Configuration Examples

Source: https://www.virtualbox.org/wiki/InterWiki_action=diff&version=3

Provides examples of how InterWiki prefixes and their corresponding URLs can be defined in the InterMapTxt wiki page. It illustrates both simple URL appending and parametric URL usage.

```wiki
PEP http://www.python.org/peps/pep-$1.html # Python Enhancement Proposal $1
Trac-ML http://thread.gmane.org/gmane.comp.version-control.subversion.trac.general/$1 # Message $1 in Trac Mailing List
```

--------------------------------

### Start Guest Additions Drivers on Linux

Source: https://www.virtualbox.org/wiki/LinuxAdditionsDebug_version=5

Attempts to manually start the VirtualBox Guest Additions drivers on a Linux guest. This command requires root privileges (using `su` or `sudo`). If the drivers fail to start, this command often outputs error messages that can help diagnose the problem.

```bash
/sbin/rcvboxadd start
```

--------------------------------

### Apache Configuration for Trac

Source: https://www.virtualbox.org/wiki/TracModPython_action=diff&version=2

Example Apache configuration for a specific Trac project. This snippet shows how to define a location for a Trac project and suggests including '...' for other necessary directives. It's important to note that this is a partial example and other configurations might be needed depending on the server setup.

```apache
<Location /projects/myproject>
 ...

```

--------------------------------

### Install Plugin using easy_install

Source: https://www.virtualbox.org/wiki/TracPlugins_action=diff&version=2

Installs a VirtualBox plugin by downloading an .egg file. Ensure easy_install is available and the Python Scripts directory is in the PATH. This method is for installing pre-compiled plugin packages.

```bash
easy_install TracSpamFilter
```

```bash
easy_install --always-unzip TracSpamFilter-0.4.1_r10106-py2.6.egg
```

--------------------------------

### Configuring and Building Binutils (Shell)

Source: https://www.virtualbox.org/wiki/SolarisCrossCompiler

Configures and builds the binutils package for Solaris. It specifies the target architecture, installation prefix, and sysroot. The build process requires creating a separate output directory to avoid modifying the source tree.

```shell
#!/bin/bash
mkdir binutils-out
cd binutils-out
../binutils-2.19.1/configure --target=i386-pc-solaris2.11 --prefix=$TARGET \
  --with-sysroot=$SYSROOT -v
make CFLAGS="-Os -w"  # The -w is because the build produces fatal warnings otherwise
make install
```

--------------------------------

### Linux Development Environment Setup

Source: https://www.virtualbox.org/wiki/VBoxInstallAndRun_version=1

This script `loadall.sh` is used on Linux hosts to set up a minimal development environment for VirtualBox. It places kernel modules, configures device nodes with udev, and sets up USB pass-through. It can also be used for updates or uninstallation with the `-u` flag.

```bash
./loadall.sh

```

```bash
./loadall.sh -u
```

--------------------------------

### Check setuptools Installation

Source: https://www.virtualbox.org/wiki/TracPlugins_version=2

A simple Python command to verify if the setuptools package is installed. Running 'python -c "import pkg_resources"' without any output indicates that setuptools is properly installed and configured.

```bash
$ python -c "import pkg_resources"

```

--------------------------------

### Install Trac Package using setup.py

Source: https://www.virtualbox.org/wiki/TracInstall_action=diff&version=1

This command installs the Trac Python package by running the setup.py script from the source directory. It compiles Python source code and installs Trac into the site-packages directory. Root permissions may be required. Advanced options like custom installation paths can be specified using flags.

```shell
python ./setup.py install
```

```shell
python ./setup.py install --help
```

```shell
python ./setup.py install --prefix=/path/to/installdir
```

--------------------------------

### Install New Trac Version with easy_install

Source: https://www.virtualbox.org/wiki/TracUpgrade_action=diff&version=2

This command upgrades an existing Trac installation to a specific version using the `easy_install` tool. It's recommended for Python-based installations.

```bash
easy_install --upgrade Trac==0.12
```

--------------------------------

### Install setuptools using ez_setup.py

Source: https://www.virtualbox.org/wiki/TracPlugins_action=diff&version=1

This snippet demonstrates how to install the setuptools package, a prerequisite for using egg-based Trac plugins. It involves downloading the ez_setup.py script and executing it with Python. Ensure setuptools version 0.6 or higher is installed.

```bash
$ python ez_setup.py

```

--------------------------------

### Install Trac with extras using pip

Source: https://www.virtualbox.org/wiki/TracInstall

Installs Trac along with specified optional dependencies (extras) using pip. For example, '[babel,rest,pygments,textile]' installs these optional packages. 'rest' includes the 'docutils' dependency.

```bash
$ pip install Trac[babel,rest,pygments,textile]

```

--------------------------------

### Start VirtualBox Application

Source: https://www.virtualbox.org/wiki/Linux%20build%20instructions

This command executes the VirtualBox application from the build output directory. It assumes the build was not hardened and that the kernel module has been successfully installed and loaded.

```bash
./VirtualBox
```

--------------------------------

### Solaris Host: Copy and Install vboxdrv

Source: https://www.virtualbox.org/wiki/VBoxInstallAndRun_action=diff&version=1

Commands to copy and install the VirtualBox driver (`vboxdrv`) on Solaris hosts. This includes copying both 64-bit and 32-bit versions of the driver to their respective kernel directories.

```bash
cp out/solaris.amd64/release/bin/vboxdrv /platform/i86pc/kernel/drv/amd64/vboxdrv
cp out/solaris.x86/release/bin/vboxdrv /platform/i86pc/kernel/drv/vboxdrv
```

--------------------------------

### Chroot into the 64-bit Environment

Source: https://www.virtualbox.org/wiki/Setup_Jail

This command changes the root directory to /var/64, effectively entering the newly created 64-bit chroot environment. It then switches the user to the currently logged-in user (LOGNAME) with root privileges within the chroot. This is the primary step to start working inside the isolated 64-bit environment.

```bash
sudo chroot /var/64 su - ${LOGNAME}

```

--------------------------------

### Example InterWiki Prefix Definitions

Source: https://www.virtualbox.org/wiki/InterMapTxt_version=1

Provides examples of how to define InterWiki prefixes. Each entry includes a prefix, the corresponding URL with argument placeholders, and an optional comment explaining the purpose of the link. These are dynamically interpreted by Trac.

```plaintext
PEP     http://www.python.org/peps/pep-$1.html                                       # Python Enhancement Proposal 
Trac-ML  http://thread.gmane.org/gmane.comp.version-control.subversion.trac.general/ # Message $1 in Trac Mailing List
trac-dev http://thread.gmane.org/gmane.comp.version-control.subversion.trac.devel/   # Message $1 in Trac Development Mailing List

Mercurial http://www.selenic.com/mercurial/wiki/index.cgi/ # the wiki for the Mercurial distributed SCM
RFC       http://rfc.net/rfc$1.html # IETF's RFC $1

#
# A arbitrary pick of InterWiki prefixes...
#
Acronym          http://www.acronymfinder.com/af-query.asp?String=exact&Acronym=
C2find           http://c2.com/cgi/wiki?FindPage&value=
Cache            http://www.google.com/search?q=cache:
CPAN             http://search.cpan.org/perldoc?
DebianBug        http://bugs.debian.org/
DebianPackage    http://packages.debian.org/
Dictionary       http://www.dict.org/bin/Dict?Database=*&Form=Dict1&Strategy=*&Query=
Google           http://www.google.com/search?q=
GoogleGroups     http://groups.google.com/group/$1/msg/$2        # Message $2 in $1 Google Group
JargonFile       http://downlode.org/perl/jargon-redirect.cgi?term=
MeatBall         http://www.usemod.com/cgi-bin/mb.pl?
MetaWiki         http://sunir.org/apps/meta.pl?
MetaWikiPedia    http://meta.wikipedia.org/wiki/
MoinMoin         http://moinmoin.wikiwikiweb.de/
WhoIs            http://www.whois.sc/
Why              http://clublet.com/c/c/why?
c2Wiki             http://c2.com/cgi/wiki?
WikiPedia        http://en.wikipedia.org/wiki/

```

--------------------------------

### Create VirtualBox MSI Package (kmk)

Source: https://www.virtualbox.org/wiki/Windows%20build%20instructions_version=76

Creates an `.msi` package for VirtualBox installation using the `kmk packing` command. This may fail for 64-bit targets if Guest Additions are included in the build. In such cases, build the 32-bit Guest Additions separately and then retry `kmk packing`.

```shell
kmk packing

```