1.1 --- a/README.txt Mon Mar 29 00:10:33 2010 +0200
1.2 +++ b/README.txt Thu Apr 15 00:44:21 2010 +0200
1.3 @@ -20,8 +20,8 @@
1.4 docs/COPYING.txt and docs/gpl-3.0.txt for more information.
1.5
1.6 Thanks to Piotr Roszatycki, the maintainer of fakechroot, for helpfully fixing
1.7 -system call coverage in that utility in order to support cross-distribution
1.8 -bootstrapping.
1.9 +system call coverage in that utility in order to attempt to support
1.10 +cross-distribution bootstrapping.
1.11
1.12 Dependencies
1.13 ------------
1.14 @@ -38,9 +38,13 @@
1.15 * Adopted lsb-release environment variables instead of new ones like
1.16 DISTNAME, exposing derivatives of these variables by default.
1.17 * Added explicit keyring package installation.
1.18 - * Added scripts for configuring and entering the chroot.
1.19 + * Added -do scripts for configuring and entering the chroot.
1.20 * Added support for UML instance construction from distribution
1.21 installations.
1.22 + * Removed specific apt- and dpkg-related scripts, replacing them with the
1.23 + general -do scripts.
1.24 + * Added --root options to certain scripts in order to support normal chroot
1.25 + installations.
1.26
1.27 Configuration
1.28 -------------
1.29 @@ -87,10 +91,6 @@
1.30
1.31 user-setup
1.32
1.33 -Or with defaults in the current directory:
1.34 -
1.35 -./user-setup
1.36 -
1.37 It is possible to override the "template" for the system by specifying a
1.38 "mirror" location. This is useful if you have the CD or DVD image for the
1.39 distribution already mounted in the filesystem. For example:
1.40 @@ -124,35 +124,23 @@
1.41
1.42 user-path /etc/apt/sources.list
1.43
1.44 -Or with defaults in the current directory:
1.45 -
1.46 -./user-path /etc/apt/sources.list
1.47 -
1.48 And you can edit the file directly with a text editor (such as vi) as follows:
1.49
1.50 vi `user-path /etc/apt/sources.list`
1.51
1.52 -Or with defaults in the current directory:
1.53 -
1.54 -vi `./user-path /etc/apt/sources.list`
1.55 -
1.56 Installing Packages
1.57 -------------------
1.58
1.59 -To install packages from other repositories, invoke the user-apt-get script
1.60 -with the options expected by the regular apt-get program. For example:
1.61 -
1.62 -user-apt-get --help
1.63 -user-apt-get update
1.64 +To install packages from other repositories, invoke the user-do script and
1.65 +specify the apt-get program together with options expected by that program.
1.66 +For example:
1.67
1.68 -It may be necessary to install the gnupg package to enable package signature
1.69 -verification:
1.70 +user-do apt-get --help
1.71 +user-do apt-get update
1.72
1.73 -user-apt-get install gnupg
1.74 +Packages can then be installed. For example:
1.75
1.76 -Then, other packages can be installed. For example:
1.77 -
1.78 -user-apt-get install python-cmdsyntax
1.79 +user-do apt-get install python-cmdsyntax
1.80
1.81 Provided that the specified packages are known and their dependencies can be
1.82 met, they will be installed into the system.
1.83 @@ -160,13 +148,14 @@
1.84 Installing Single Packages
1.85 --------------------------
1.86
1.87 -To install individual package files, invoke the user-dpkg-i script with the
1.88 -name of the package file. For example:
1.89 +To install individual package files, first copy them into the package manager
1.90 +directory hierarchy. For example:
1.91
1.92 -user-dpkg-i /home/me/downloads/python-cmdsyntax_0.91-0ubuntu2_all.deb
1.93 +cp python-cmdsyntax_0.91-0ubuntu2_all.deb `user-path /tmp`
1.94
1.95 -This script will copy the file into the personal package management
1.96 -environment and run dpkg with the -i (install) option.
1.97 +The invoke the dpkg program through the user-do script as follows:
1.98 +
1.99 +user-do dpkg -i /tmp/python-cmdsyntax_0.91-0ubuntu2_all.deb
1.100
1.101 Using Packages
1.102 --------------
1.103 @@ -197,9 +186,9 @@
1.104 More complicated extension modules may require further adjustments to the
1.105 LD_LIBRARY_PATH and PYTHONPATH variables:
1.106
1.107 -export LD_LIBRARY_PATH=`./user-path /usr/lib`
1.108 -export PYTHONPATH=`./user-path /usr/lib/python2.5/site-packages/`
1.109 -export PYTHONPATH=${PYTHONPATH}:`./user-path /var/lib/python-support/python2.5`
1.110 +export LD_LIBRARY_PATH=`user-path /usr/lib`
1.111 +export PYTHONPATH=`user-path /usr/lib/python2.5/site-packages/`
1.112 +export PYTHONPATH=${PYTHONPATH}:`user-path /var/lib/python-support/python2.5`
1.113
1.114 Entering the Package Manager
1.115 ----------------------------
1.116 @@ -207,7 +196,7 @@
1.117 It is also possible to administer the package manager from within the
1.118 installation:
1.119
1.120 -user-enter
1.121 +user-do
1.122
1.123 This should provide a "root" prompt which can then be used to issue commands
1.124 within the package manager environment. For example:
1.125 @@ -222,12 +211,12 @@
1.126 the User Mode Linux (UML) software.
1.127
1.128 To convert a package manager installation into a UML instance, start with the
1.129 -uml-postsetup script which changes the installation's configuration in a
1.130 -number of areas:
1.131 +user-to-uml script which changes the installation's configuration in a number
1.132 +of areas:
1.133
1.134 -uml-postsetup
1.135 +user-to-uml
1.136
1.137 -Then, as a privileged user, run the user-setupdev script to initialise some
1.138 +Then, as a privileged user, run the uml-setupdev script to initialise some
1.139 UML-specific device files:
1.140
1.141 sudo uml-setupdev
1.142 @@ -249,6 +238,6 @@
1.143 Entering or Starting UML Instances
1.144 ----------------------------------
1.145
1.146 -To enter a UML instance, use the uml-enter script:
1.147 +To enter a UML instance, use the uml-do script:
1.148
1.149 -uml-enter
1.150 +uml-do