- This topic has 3 replies, 3 voices, and was last updated Sep 21-11:08 am by Anonymous.
-
Posts
-
doa379
Debian vet for eight years. Looking to try AntiX.
I was wondering if it’s possible to deploy AntiX using debootstrap or similar utility?
If not then what’s the difference between these two images antiX-core, antiX-net? Is wifi support provided in these images?
Xecure
I know that for building the antiX system and generating the .iso files, chroot and debootstrap are used, so it should be possible (cannot confirm).
About differences between antiX net and core, as stated here: http://download.tuxfamily.org/antix/docs-antiX-19/FAQ/index.html
antiX-core includes non-free firmware, which means that most wireless is supported.
Core is if you are building for a computer using a wireless card.
Net is for building using an ethernet connection (no wireless firmware, no wireless support until you install the respective firmware).antiX Live system enthusiast.
General Live Boot Parameters for antiX.Thank you.
Anonymous
antiX ISOs are built using this tool: https://github.com/BitJam/Build-iso
Nested under the /Template subdirectory, for each of the flavors (editions: COMMON, base-AND-full, base, core, full, net) a customizable manifest of packagenames specifies which packages to add/remove (“packages.list” and “remove.list”)
Similarly, for each flavor, under the project subdirectory /Themes holds any additional unpackaged files to be injected.
During the build, a list of pre-installed packages is bundled into the ISO, for the benefit of later reference on an installed system
/usr/share/antiX/installed-packages.txt
https://github.com/BitJam/Build-iso/______/build-iso#L1142https://github.com/BitJam/Build-iso________README.md
build-isoGeneral Operation
The work of build-iso is split up into 8 different stages. When each stages is successfully completed, a stage-N.out file is created in the Output/ directory. Each time build-iso is run, it will start working on the first stage that lacks an output file. These files also let the program pass information for one stage to the next across restarts. Therefore there is almost no penalty for stopping the program after each stage. If there is an error condition then the penalty for stopping the program, fixing the error, and then restarting the program is minimized.The 10 stages of processing are: 0. Gather inputs and set defaults
Make directories and symlinks
Run debootstrap
Prepare chroot
Inside of chroot
Finalize and clean the chroot
Prepare iso directory
Create squashfs file
Create iso file
Clean up and prepare to start overThe most complicated stage is “4: Inside the chroot”. This is also the most time consuming stage because this is when *.deb packages get installed. So Stage 4 is broken up into parts:
Read PARTIAL file to skip parts done
Update repos and do apt-get update
Search for complete kernel name
Define locales
Install basic packages
Install kernel & headers
Update locales
Install pesky packages
Install antiX packages
Run first apt-get -f install
Install latest antiX debs
Remove some packages
Add some packages
Reinstall some packages
Update runlevels based on flavour
Get Latest Flash
Manual configuration
Update Timezone, hostname, and user accounts
Run second apt-get -f install
Update SLiM defaults
Apply Theme
Check kernel’s GCC versionThese parts are not automatically skipped if they have already been performed but the most time consuming parts (installing packages) go by very quickly if the packages have already been installed. You can use environment variables to manually skip parts. See “Debugging Options” for details.
Environment VariablesThe architecture (386 or x64) and the flavour (core-libre, base, or file) can be set via the ARCH and ISO_FLAV environment variables. If they are not set via these environment variables then the user is prompt form them in Stage 0. These two variables let the build-iso-all script build isos for all architectures and flavours without minimal user intervention or no user intervention at all.
Directories
Unlike most programs that live in a directory that is on the PATH, the directory this program is in has special significance. It is called the script directory and that is where it expects to find the Template/ directory and where it creates creates other directories, symlinks and files.Variables in the DEFAULTS file
If needed information is missing from the DEFAULTS file then the user will be prompted for it in Stage 0.ADD_BORDER_OPTS Use these options when adding border to live image
APT_GET_OPTS Options sent to apt-get. Don’t change.
CACHE Enable caches by name. Only “debootstrap” available ATM.
CACHE_EXPIRE Expire cache entries after this many days
CODE_NAME The name of this version of the distro
DEBIAN_RELEASE stable|testing|unstable
DISTRO_NAME “antiX” or your choice
DISTRO_VERSION A version number with numerals and dots
ENABLE_LOCALES All|Default|Single
HOSTNAME “antiX1” or your choice
ISO_SYMLINK If this is a symlink, update it to point to iso file
K_REVISION “*” or your choice of a number
K_TEMPLATE Template for creating kernel names. Change with care.
K_VERSION Version number of the kernel to use or “*” for latest
LIVE_USER Default username on the iso
LOCALE Default locale iso the iso
LOCAL_MIRROR Mirror closest to you
MIRROR Mirror on the iso
RELEASE_DATE Leave blank for today or your choice
RESPIN_FLAV See Custom Flavours below
TIME_ZONE Timezone for the iso
X_TERM_EMULATOR Default X teminal emulator.Custom Flavours
You are allowed to create your own flavour names just by making a subdirectory of Template/ and copying files into it. Your new flavour MUST be based on one of the existing flavours:
core, or base, or full
The reason for this is these existing names are connected with repos names and the names of certain antiX Debian packages.
- You must be logged in to reply to this topic.
