Chroot inside *path*. This is especially usefull to update system images. This mounts filesystems (/proc, /sys, /dev, /dev/pts, /dev/shm), modify a few config files (resolv.conf, mtab) and finally executes a shell in your chroot (default: /bin/bash)
Chroot inside *path*. This is especially useful to update system images. This mounts filesystems (/proc, /sys, /dev, /dev/pts, /dev/shm), modify a few config files (resolv.conf, mtab) and finally executes a shell in your chroot (default: /bin/bash)
@@ -337,7 +337,7 @@ InstallSystems use two kind of images:
**source image**
Each image available in repositories has to be build. The image before building is called a source image. In a source image, there are five directories and two files. Each images make the distinction between scripts and payloads.
Each image available in repositories has to be built. The image before building is called a source image. In a source image, there are typically five directories and three files.
build/
Scripts to customize the build process for the image.
@@ -349,7 +349,7 @@ InstallSystems use two kind of images:
The scripts with logical steps of the install are in this directory.
lib/
Python modules which are embeded in image.
Python modules needed to build and/or to install the image
payload/
This directory embeds one or more payloads (typically rootfs) for the image.
@@ -376,5 +376,5 @@ REPOSITORIES
InstallSystems manages images with repositories.
An InstallSystems repository use a SQLite3 database (db), a last file (timestamp of last db modification) and MD5s of images. The repos are reachable by HTTP(S), FTP and SSH. This allows you to easily access images.
An InstallSystems repository use a SQLite3 database (db), a last file (timestamp of last db modification) and MD5s of images. Repositories are reachable by HTTP(S), FTP and SSH. This allows you to easily access images.
Also, please note that you can only modify local repositories.