SliTaz Repositories

     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/proot/stuff/patches/man.patch	Sat Nov 21 14:32:44 2020 +0100
     1.3 @@ -0,0 +1,547 @@
     1.4 +--- a/doc/proot/man.1
     1.5 ++++ b/doc/proot/man.1
     1.6 +@@ -1,48 +1,19 @@
     1.7 +-.\" Man page generated from reStructuredText.
     1.8 +-.
     1.9 + .TH PROOT 1 "2014-12-12" "5.1.0" ""
    1.10 + .SH NAME
    1.11 +-PRoot \- chroot, mount --bind, and binfmt_misc without privilege/setup
    1.12 +-.
    1.13 +-.nr rst2man-indent-level 0
    1.14 +-.
    1.15 +-.de1 rstReportMargin
    1.16 +-\\$1 \\n[an-margin]
    1.17 +-level \\n[rst2man-indent-level]
    1.18 +-level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
    1.19 +--
    1.20 +-\\n[rst2man-indent0]
    1.21 +-\\n[rst2man-indent1]
    1.22 +-\\n[rst2man-indent2]
    1.23 +-..
    1.24 +-.de1 INDENT
    1.25 +-.\" .rstReportMargin pre:
    1.26 +-. RS \\$1
    1.27 +-. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
    1.28 +-. nr rst2man-indent-level +1
    1.29 +-.\" .rstReportMargin post:
    1.30 +-..
    1.31 +-.de UNINDENT
    1.32 +-. RE
    1.33 +-.\" indent \\n[an-margin]
    1.34 +-.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
    1.35 +-.nr rst2man-indent-level -1
    1.36 +-.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
    1.37 +-.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
    1.38 +-..
    1.39 ++PRoot \- chroot, mount \-\-bind, and binfmt_misc without privilege/setup
    1.40 + .SH SYNOPSIS
    1.41 + .sp
    1.42 + \fBproot\fP [\fIoption\fP] ... [\fIcommand\fP]
    1.43 + .SH DESCRIPTION
    1.44 + .sp
    1.45 + PRoot is a user\-space implementation of \fBchroot\fP, \fBmount \-\-bind\fP,
    1.46 +-and \fBbinfmt_misc\fP\&.  This means that users don\(aqt need any privileges
    1.47 ++and \fBbinfmt_misc\fP\&.  This means that users don't need any privileges
    1.48 + or setup to do things like using an arbitrary directory as the new
    1.49 + root filesystem, making files accessible somewhere else in the
    1.50 + filesystem hierarchy, or executing programs built for another CPU
    1.51 + architecture transparently through QEMU user\-mode.  Also, developers
    1.52 + can use PRoot as a generic Linux process instrumentation engine thanks
    1.53 +-to its extension mechanism, see \fI\%CARE\fP for an example.  Technically
    1.54 ++to its extension mechanism, see \fICARE\fP for an example.  Technically
    1.55 + PRoot relies on \fBptrace\fP, an unprivileged system\-call available in
    1.56 + every Linux kernel.
    1.57 + .sp
    1.58 +@@ -55,9 +26,9 @@
    1.59 + .sp
    1.60 + When the guest Linux distribution is made for a CPU architecture
    1.61 + incompatible with the host one, PRoot uses the CPU emulator QEMU
    1.62 +-user\-mode to execute transparently guest programs.  It\(aqs a convenient
    1.63 ++user\-mode to execute transparently guest programs.  It's a convenient
    1.64 + way to develop, to build, and to validate any guest Linux packages
    1.65 +-seamlessly on users\(aq computer, just as if they were in a \fInative\fP
    1.66 ++seamlessly on users' computer, just as if they were in a \fInative\fP
    1.67 + guest environment.  That way all of the cross\-compilation issues are
    1.68 + avoided.
    1.69 + .sp
    1.70 +@@ -75,12 +46,11 @@
    1.71 + if they were "normal" host programs.
    1.72 + .SH OPTIONS
    1.73 + .sp
    1.74 +-The command\-line interface is composed of two parts: first PRoot\(aqs
    1.75 ++The command\-line interface is composed of two parts: first PRoot's
    1.76 + options (optional), then the command to launch (\fB/bin/sh\fP if not
    1.77 + specified).  This section describes the options supported by PRoot,
    1.78 + that is, the first part of its command\-line interface.
    1.79 + .SS Regular options
    1.80 +-.INDENT 0.0
    1.81 + .TP
    1.82 + .BI \-r \ path\fP,\fB \ \-\-rootfs\fB= path
    1.83 + Use \fIpath\fP as the new guest root file\-system, default is \fB/\fP\&.
    1.84 +@@ -104,7 +74,7 @@
    1.85 + guest location is a symbolic link, it is dereferenced to ensure
    1.86 + the new content is accessible through all the symbolic links that
    1.87 + point to the overlaid content.  In most cases this default
    1.88 +-behavior shouldn\(aqt be a problem, although it is possible to
    1.89 ++behavior shouldn't be a problem, although it is possible to
    1.90 + explicitly not dereference the guest location by appending it the
    1.91 + \fB!\fP character: \fB\-b *host_path*:*guest_location!*\fP\&.
    1.92 + .TP
    1.93 +@@ -137,14 +107,12 @@
    1.94 + .TP
    1.95 + .B \-h\fP,\fB  \-\-help\fP,\fB  \-\-usage
    1.96 + Print the version and the command\-line usage, then exit.
    1.97 +-.UNINDENT
    1.98 + .SS Extension options
    1.99 + .sp
   1.100 + The following options enable built\-in extensions.  Technically
   1.101 + developers can add their own features to PRoot or use it as a Linux
   1.102 + process instrumentation engine thanks to its extension mechanism, see
   1.103 + the sources for further details.
   1.104 +-.INDENT 0.0
   1.105 + .TP
   1.106 + .BI \-k \ string\fP,\fB \ \-\-kernel\-release\fB= string
   1.107 + Make current kernel appear as kernel release \fIstring\fP\&.
   1.108 +@@ -174,11 +142,9 @@
   1.109 + \fIgid\fP\&.  Likewise, files actually owned by the current user and
   1.110 + group appear as if they were owned by \fIuid\fP and \fIgid\fP instead.
   1.111 + Note that the \fB\-0\fP option is the same as \fB\-i 0:0\fP\&.
   1.112 +-.UNINDENT
   1.113 + .SS Alias options
   1.114 + .sp
   1.115 + The following options are aliases for handy sets of options.
   1.116 +-.INDENT 0.0
   1.117 + .TP
   1.118 + .BI \-R \ path
   1.119 + Alias: \fB\-r *path*\fP + a couple of recommended \fB\-b\fP\&.
   1.120 +@@ -187,10 +153,9 @@
   1.121 + access information about the host system, as it is illustrated in
   1.122 + the \fBExamples\fP section of the manual.  These host information
   1.123 + are typically: user/group definition, network setup, run\-time
   1.124 +-information, users\(aq files, ...  On all Linux distributions, they
   1.125 ++information, users' files, ...  On all Linux distributions, they
   1.126 + all lie in a couple of host files and directories that are
   1.127 + automatically bound by this option:
   1.128 +-.INDENT 7.0
   1.129 + .IP \(bu 2
   1.130 + /etc/host.conf
   1.131 + .IP \(bu 2
   1.132 +@@ -229,7 +194,6 @@
   1.133 + $HOME
   1.134 + .IP \(bu 2
   1.135 + \fIpath\fP
   1.136 +-.UNINDENT
   1.137 + .TP
   1.138 + .BI \-S \ path
   1.139 + Alias: \fB\-0 \-r *path*\fP + a couple of recommended \fB\-b\fP\&.
   1.140 +@@ -238,7 +202,6 @@
   1.141 + the guest rootfs.  It is similar to the \fB\-R\fP option expect it
   1.142 + enables the \fB\-0\fP option and binds only the following minimal set
   1.143 + of paths to avoid unexpected changes on host files:
   1.144 +-.INDENT 7.0
   1.145 + .IP \(bu 2
   1.146 + /etc/host.conf
   1.147 + .IP \(bu 2
   1.148 +@@ -261,8 +224,6 @@
   1.149 + $HOME
   1.150 + .IP \(bu 2
   1.151 + \fIpath\fP
   1.152 +-.UNINDENT
   1.153 +-.UNINDENT
   1.154 + .SH EXIT STATUS
   1.155 + .sp
   1.156 + If an internal error occurs, \fBproot\fP returns a non\-zero exit status,
   1.157 +@@ -285,8 +246,6 @@
   1.158 + \fBproot\fP the path to the guest rootfs followed by the desired
   1.159 + command.  The example below executes the program \fBcat\fP to print the
   1.160 + content of a file:
   1.161 +-.INDENT 0.0
   1.162 +-.INDENT 3.5
   1.163 + .sp
   1.164 + .nf
   1.165 + .ft C
   1.166 +@@ -295,14 +254,10 @@
   1.167 + Welcome to Slackware Linux 8.0
   1.168 + .ft P
   1.169 + .fi
   1.170 +-.UNINDENT
   1.171 +-.UNINDENT
   1.172 + .sp
   1.173 + The default command is \fB/bin/sh\fP when none is specified. Thus the
   1.174 + shortest way to confine an interactive shell and all its sub\-programs
   1.175 + is:
   1.176 +-.INDENT 0.0
   1.177 +-.INDENT 3.5
   1.178 + .sp
   1.179 + .nf
   1.180 + .ft C
   1.181 +@@ -312,15 +267,11 @@
   1.182 + Welcome to Slackware Linux 8.0
   1.183 + .ft P
   1.184 + .fi
   1.185 +-.UNINDENT
   1.186 +-.UNINDENT
   1.187 + .SS \fBmount \-\-bind\fP equivalent
   1.188 + .sp
   1.189 + The bind mechanism enables one to relocate files and directories.  This is
   1.190 + typically useful to trick programs that perform access to hard\-coded
   1.191 + locations, like some installation scripts:
   1.192 +-.INDENT 0.0
   1.193 +-.INDENT 3.5
   1.194 + .sp
   1.195 + .nf
   1.196 + .ft C
   1.197 +@@ -333,14 +284,10 @@
   1.198 + [...] # prog is installed in "/tmp/alternate_opt/bin" actually
   1.199 + .ft P
   1.200 + .fi
   1.201 +-.UNINDENT
   1.202 +-.UNINDENT
   1.203 + .sp
   1.204 + As shown in this example, it is possible to bind over files not even
   1.205 + owned by the user.  This can be used to \fIoverlay\fP system configuration
   1.206 + files, for instance the DNS setting:
   1.207 +-.INDENT 0.0
   1.208 +-.INDENT 3.5
   1.209 + .sp
   1.210 + .nf
   1.211 + .ft C
   1.212 +@@ -348,25 +295,19 @@
   1.213 + \-rw\-r\-\-r\-\- 1 root root 675 Mar  4  2011 /etc/hosts
   1.214 + .ft P
   1.215 + .fi
   1.216 +-.UNINDENT
   1.217 +-.UNINDENT
   1.218 +-.INDENT 0.0
   1.219 +-.INDENT 3.5
   1.220 + .sp
   1.221 + .nf
   1.222 + .ft C
   1.223 + proot \-b ~/alternate_hosts:/etc/hosts
   1.224 + 
   1.225 +-$ echo \(aq1.2.3.4 google.com\(aq > /etc/hosts
   1.226 ++$ echo '1.2.3.4 google.com' > /etc/hosts
   1.227 + $ resolveip google.com
   1.228 + IP address of google.com is 1.2.3.4
   1.229 +-$ echo \(aq5.6.7.8 google.com\(aq > /etc/hosts
   1.230 ++$ echo '5.6.7.8 google.com' > /etc/hosts
   1.231 + $ resolveip google.com
   1.232 + IP address of google.com is 5.6.7.8
   1.233 + .ft P
   1.234 + .fi
   1.235 +-.UNINDENT
   1.236 +-.UNINDENT
   1.237 + .sp
   1.238 + Another example: on most Linux distributions \fB/bin/sh\fP is a symbolic
   1.239 + link to \fB/bin/bash\fP, whereas it points to \fB/bin/dash\fP on Debian
   1.240 +@@ -374,21 +315,15 @@
   1.241 + might not work with Dash.  In this case, the binding mechanism of
   1.242 + PRoot can be used to set non\-disruptively \fB/bin/bash\fP as the default
   1.243 + \fB/bin/sh\fP on these two Linux distributions:
   1.244 +-.INDENT 0.0
   1.245 +-.INDENT 3.5
   1.246 + .sp
   1.247 + .nf
   1.248 + .ft C
   1.249 + proot \-b /bin/bash:/bin/sh [...]
   1.250 + .ft P
   1.251 + .fi
   1.252 +-.UNINDENT
   1.253 +-.UNINDENT
   1.254 + .sp
   1.255 + Because \fB/bin/sh\fP is initially a symbolic link to \fB/bin/dash\fP, the
   1.256 + content of \fB/bin/bash\fP is actually bound over this latter:
   1.257 +-.INDENT 0.0
   1.258 +-.INDENT 3.5
   1.259 + .sp
   1.260 + .nf
   1.261 + .ft C
   1.262 +@@ -402,18 +337,14 @@
   1.263 + 089ed56cd74e63f461bef0fdfc2d159a  /bin/dash
   1.264 + .ft P
   1.265 + .fi
   1.266 +-.UNINDENT
   1.267 +-.UNINDENT
   1.268 + .sp
   1.269 +-In most cases this shouldn\(aqt be a problem, but it is still possible to
   1.270 ++In most cases this shouldn't be a problem, but it is still possible to
   1.271 + strictly bind \fB/bin/bash\fP over \fB/bin/sh\fP \-\- without dereferencing
   1.272 + it \-\- by specifying the \fB!\fP character at the end:
   1.273 +-.INDENT 0.0
   1.274 +-.INDENT 3.5
   1.275 + .sp
   1.276 + .nf
   1.277 + .ft C
   1.278 +-proot \-b \(aq/bin/bash:/bin/sh!\(aq
   1.279 ++proot \-b '/bin/bash:/bin/sh!'
   1.280 + 
   1.281 + $ md5sum /bin/sh
   1.282 + 089ed56cd74e63f461bef0fdfc2d159a  /bin/sh
   1.283 +@@ -423,16 +354,12 @@
   1.284 + c229085928dc19e8d9bd29fe88268504  /bin/dash
   1.285 + .ft P
   1.286 + .fi
   1.287 +-.UNINDENT
   1.288 +-.UNINDENT
   1.289 + .SS \fBchroot\fP + \fBmount \-\-bind\fP equivalent
   1.290 + .sp
   1.291 + The two features above can be combined to make any file from the host
   1.292 + rootfs accessible in the confined environment just as if it were
   1.293 + initially part of the guest rootfs.  It is sometimes required to run
   1.294 + programs that rely on some specific files:
   1.295 +-.INDENT 0.0
   1.296 +-.INDENT 3.5
   1.297 + .sp
   1.298 + .nf
   1.299 + .ft C
   1.300 +@@ -442,12 +369,8 @@
   1.301 + Error, do this: mount \-t proc none /proc
   1.302 + .ft P
   1.303 + .fi
   1.304 +-.UNINDENT
   1.305 +-.UNINDENT
   1.306 + .sp
   1.307 + works better with:
   1.308 +-.INDENT 0.0
   1.309 +-.INDENT 3.5
   1.310 + .sp
   1.311 + .nf
   1.312 + .ft C
   1.313 +@@ -461,14 +384,10 @@
   1.314 + ?        ps \-o tty,command
   1.315 + .ft P
   1.316 + .fi
   1.317 +-.UNINDENT
   1.318 +-.UNINDENT
   1.319 + .sp
   1.320 +-Actually there\(aqs a bunch of such specific files, that\(aqs why PRoot
   1.321 ++Actually there's a bunch of such specific files, that's why PRoot
   1.322 + provides the option \fB\-R\fP to bind automatically a pre\-defined list of
   1.323 + recommended paths:
   1.324 +-.INDENT 0.0
   1.325 +-.INDENT 3.5
   1.326 + .sp
   1.327 + .nf
   1.328 + .ft C
   1.329 +@@ -482,16 +401,12 @@
   1.330 + pts/6    ps \-o tty,command
   1.331 + .ft P
   1.332 + .fi
   1.333 +-.UNINDENT
   1.334 +-.UNINDENT
   1.335 + .SS \fBchroot\fP + \fBmount \-\-bind\fP + \fBsu\fP equivalent
   1.336 + .sp
   1.337 + Some programs will not work correctly if they are not run by the
   1.338 + "root" user, this is typically the case with package managers.  PRoot
   1.339 + can fake the root identity and its privileges when the \fB\-0\fP (zero)
   1.340 + option is specified:
   1.341 +-.INDENT 0.0
   1.342 +-.INDENT 3.5
   1.343 + .sp
   1.344 + .nf
   1.345 + .ft C
   1.346 +@@ -502,13 +417,11 @@
   1.347 + 
   1.348 + # mkdir /tmp/foo
   1.349 + # chmod a\-rwx /tmp/foo
   1.350 +-# echo \(aqI bypass file\-system permissions.\(aq > /tmp/foo/bar
   1.351 ++# echo 'I bypass file\-system permissions.' > /tmp/foo/bar
   1.352 + # cat /tmp/foo/bar
   1.353 + I bypass file\-system permissions.
   1.354 + .ft P
   1.355 + .fi
   1.356 +-.UNINDENT
   1.357 +-.UNINDENT
   1.358 + .sp
   1.359 + This option is typically required to create or install packages into
   1.360 + the guest rootfs.  Note it is \fInot\fP recommended to use the \fB\-R\fP
   1.361 +@@ -516,8 +429,6 @@
   1.362 + system files, like \fB/etc/group\fP\&.  Instead, it is recommended to use
   1.363 + the \fB\-S\fP option.  This latter enables the \fB\-0\fP option and binds
   1.364 + only paths that are known to not be updated by packages:
   1.365 +-.INDENT 0.0
   1.366 +-.INDENT 3.5
   1.367 + .sp
   1.368 + .nf
   1.369 + .ft C
   1.370 +@@ -527,18 +438,14 @@
   1.371 + Installing package perl...
   1.372 + .ft P
   1.373 + .fi
   1.374 +-.UNINDENT
   1.375 +-.UNINDENT
   1.376 + .SS \fBchroot\fP + \fBmount \-\-bind\fP + \fBbinfmt_misc\fP equivalent
   1.377 + .sp
   1.378 + PRoot uses QEMU user\-mode to execute programs built for a CPU
   1.379 +-architecture incompatible with the host one.  From users\(aq
   1.380 ++architecture incompatible with the host one.  From users'
   1.381 + point\-of\-view, guest programs handled by QEMU user\-mode are executed
   1.382 + transparently, that is, just like host programs.  To enable this
   1.383 + feature users just have to specify which instance of QEMU user\-mode
   1.384 + they want to use with the option \fB\-q\fP:
   1.385 +-.INDENT 0.0
   1.386 +-.INDENT 3.5
   1.387 + .sp
   1.388 + .nf
   1.389 + .ft C
   1.390 +@@ -548,31 +455,23 @@
   1.391 + Welcome to ARMedSlack Linux 12.2
   1.392 + .ft P
   1.393 + .fi
   1.394 +-.UNINDENT
   1.395 +-.UNINDENT
   1.396 + .sp
   1.397 + The parameter of the \fB\-q\fP option is actually a whole QEMU user\-mode
   1.398 + command, for instance to enable its GDB server on port 1234:
   1.399 +-.INDENT 0.0
   1.400 +-.INDENT 3.5
   1.401 + .sp
   1.402 + .nf
   1.403 + .ft C
   1.404 + proot \-R /mnt/armslack\-12.2/ \-q "qemu\-arm \-g 1234" emacs
   1.405 + .ft P
   1.406 + .fi
   1.407 +-.UNINDENT
   1.408 +-.UNINDENT
   1.409 + .sp
   1.410 + PRoot allows one to mix transparently the emulated execution of guest
   1.411 + programs and the native execution of host programs in the same
   1.412 +-file\-system namespace.  It\(aqs typically useful to extend the list of
   1.413 ++file\-system namespace.  It's typically useful to extend the list of
   1.414 + available programs and to speed up build\-time significantly.  This
   1.415 + mixed\-execution feature is enabled by default when using QEMU
   1.416 + user\-mode, and the content of the host rootfs is made accessible
   1.417 + through \fB/host\-rootfs\fP:
   1.418 +-.INDENT 0.0
   1.419 +-.INDENT 3.5
   1.420 + .sp
   1.421 + .nf
   1.422 + .ft C
   1.423 +@@ -580,24 +479,20 @@
   1.424 + 
   1.425 + $ file /bin/echo
   1.426 + [...] ELF 32\-bit LSB executable, ARM [...]
   1.427 +-$ /bin/echo \(aqHello world!\(aq
   1.428 ++$ /bin/echo 'Hello world!'
   1.429 + Hello world!
   1.430 + 
   1.431 + $ file /host\-rootfs/bin/echo
   1.432 + [...] ELF 64\-bit LSB executable, x86\-64 [...]
   1.433 +-$ /host\-rootfs/bin/echo \(aqHello mixed world!\(aq
   1.434 ++$ /host\-rootfs/bin/echo 'Hello mixed world!'
   1.435 + Hello mixed world!
   1.436 + .ft P
   1.437 + .fi
   1.438 +-.UNINDENT
   1.439 +-.UNINDENT
   1.440 + .sp
   1.441 + Since both host and guest programs use the guest rootfs as \fB/\fP,
   1.442 + users may want to deactivate explicitly cross\-filesystem support found
   1.443 + in most GNU cross\-compilation tools.  For example with GCC configured
   1.444 + to cross\-compile to the ARM target:
   1.445 +-.INDENT 0.0
   1.446 +-.INDENT 3.5
   1.447 + .sp
   1.448 + .nf
   1.449 + .ft C
   1.450 +@@ -608,14 +503,10 @@
   1.451 + $ ./configure; make
   1.452 + .ft P
   1.453 + .fi
   1.454 +-.UNINDENT
   1.455 +-.UNINDENT
   1.456 + .sp
   1.457 + As with regular files, a host instance of a program can be bound over
   1.458 + its guest instance.  Here is an example where the guest binary of
   1.459 + \fBmake\fP is overlaid by the host one:
   1.460 +-.INDENT 0.0
   1.461 +-.INDENT 3.5
   1.462 + .sp
   1.463 + .nf
   1.464 + .ft C
   1.465 +@@ -628,31 +519,24 @@
   1.466 + Built for x86_64\-slackware\-linux\-gnu
   1.467 + .ft P
   1.468 + .fi
   1.469 +-.UNINDENT
   1.470 +-.UNINDENT
   1.471 + .sp
   1.472 +-It\(aqs worth mentioning that even when mixing the native execution of
   1.473 ++It's worth mentioning that even when mixing the native execution of
   1.474 + host programs and the emulated execution of guest programs, they still
   1.475 + believe they are running in a native guest environment.  As a
   1.476 + demonstration, here is a partial output of a typical \fB\&./configure\fP
   1.477 + script:
   1.478 +-.INDENT 0.0
   1.479 +-.INDENT 3.5
   1.480 + .sp
   1.481 + .nf
   1.482 + .ft C
   1.483 + checking whether the C compiler is a cross\-compiler... no
   1.484 + .ft P
   1.485 + .fi
   1.486 +-.UNINDENT
   1.487 +-.UNINDENT
   1.488 + .SH DOWNLOADS
   1.489 + .SS PRoot
   1.490 + .sp
   1.491 + The latest release of PRoot is packaged on \fI\%http://packages.proot.me\fP
   1.492 + and sources are hosted on \fI\%http://github.proot.me\fP\&.  It is also
   1.493 + available as highly compatible static binaries:
   1.494 +-.INDENT 0.0
   1.495 + .IP \(bu 2
   1.496 + for x86_64: \fI\%http://static.proot.me/proot\-x86_64\fP
   1.497 + .IP \(bu 2
   1.498 +@@ -661,14 +545,12 @@
   1.499 + for ARM: \fI\%http://static.proot.me/proot\-arm\fP
   1.500 + .IP \(bu 2
   1.501 + other architectures: on demand.
   1.502 +-.UNINDENT
   1.503 + .SS Rootfs
   1.504 + .sp
   1.505 + Here follows a couple of URLs where some rootfs archives can be freely
   1.506 + downloaded.  Note that \fBmknod\fP errors reported by \fBtar\fP when
   1.507 + extracting these archives can be safely ignored since special files
   1.508 + are typically bound (see \fB\-R\fP option for details).
   1.509 +-.INDENT 0.0
   1.510 + .IP \(bu 2
   1.511 + \fI\%http://download.openvz.org/template/precreated/\fP
   1.512 + .IP \(bu 2
   1.513 +@@ -679,20 +561,15 @@
   1.514 + \fI\%http://cdimage.ubuntu.com/ubuntu\-core/releases/\fP
   1.515 + .IP \(bu 2
   1.516 + \fI\%http://archlinuxarm.org/developers/downloads\fP
   1.517 +-.UNINDENT
   1.518 + .sp
   1.519 + Technically such rootfs archive can be created by running the
   1.520 + following command on the expected Linux distribution:
   1.521 +-.INDENT 0.0
   1.522 +-.INDENT 3.5
   1.523 + .sp
   1.524 + .nf
   1.525 + .ft C
   1.526 + tar \-\-one\-file\-system \-\-create \-\-gzip \-\-file my_rootfs.tar.gz /
   1.527 + .ft P
   1.528 + .fi
   1.529 +-.UNINDENT
   1.530 +-.UNINDENT
   1.531 + .SS QEMU user\-mode
   1.532 + .sp
   1.533 + QEMU user\-mode is required only if the guest rootfs was made for a CPU
   1.534 +@@ -710,8 +587,6 @@
   1.535 + .sp
   1.536 + Visit \fI\%http://proot.me\fP for help, bug reports, suggestions, patches, ...
   1.537 + Copyright (C) 2014 STMicroelectronics, licensed under GPL v2 or later.
   1.538 +-.INDENT 0.0
   1.539 +-.INDENT 3.5
   1.540 + .sp
   1.541 + .nf
   1.542 + .ft C
   1.543 +@@ -721,7 +596,4 @@
   1.544 + |__|  |__|__\e_____/\e_____/\e____|
   1.545 + .ft P
   1.546 + .fi
   1.547 +-.UNINDENT
   1.548 +-.UNINDENT
   1.549 +-.\" Generated by docutils manpage writer.
   1.550 + .