CHANGES - [androot.sh] Improve code quality - [androot.sh] Modify DOWNLOADSERVER* variables - [patch.sh] Implement rootfs patching - [prepare.sh] Squashed bugs - [rootfsbuilder/archlinux-x86_64.sh] Remove "copy pacman config" flag causing some issues - [systeminstall.sh] Implement rootfs configuration and update script BUGS - [systeminstall.sh|patch.sh] Scripts only work on the same architecture as the host
2.5 KiB
androot
Chroot and systemd-nspawn rootfs installer
Experimental
androot is experimental software and can lead to breakage!
Only run these scripts with extensive knowledge of Linux (and Android if using Termux)!
How to use
Termux
WARNING
If you want to use androot under Android you need a working Magisk or KernelSU installation.
If you wish to install a (more limited) Linux distribution without root access use Andronix instead.
Dependencies
- Magisk/Magisk Delta/KernelSU
- curl
- bash
- chroot
- bsdtar
- tsu
Use
curl -sSL "https://git.staropensource.de/StarOpenSource/androot/raw/branch/master/androot.sh"|sudo bash - --download
Linux
Dependencies
- curl
- bash
- chroot/systemd-nspawn
- bsdtar
Use
curl -sSL "https://git.staropensource.de/StarOpenSource/androot/raw/branch/master/androot.sh"|sudo bash - --download
Architectures
Supported (target architectures)
- x86_64 (amd64)
- arm64 (aarch64)
Supported (execution architectures)
- x86_64 (amd64)
- arm64 (aarch64)
- powerpc64 (ppc64,ppc64le)
- mips64
Unsupported
- x86 (i386,i686)
- arm
- powerpc (ppc,ppcle)
- mips
Distributions
- Arch Linux
How does this work?
tldr
We download & decompress a rootfs, apply some magic and make it "bootable" with the help of chroot
or systemd-nspawn
.
The short answer
- check architecture
- ask for target architecture, execution architecture(s) and distribution
- download rootfs
- decompress rootfs
- mount rootfs
- install updates and bootscript dependencies
- apply patches (if using chroot)
- download bootscripts
- unmount rootfs
- finish and print information about how to "boot" the rootfs
The long answer
Just read the source code.
How to test
make test
to run it, make log
to view the log file.
Recommendation
We recommend using /dev/shm as a install location during development. Although using temporary directories
is disallowed for normal installations we highly recommend using /dev/shm during development as you will
be wearing out your disk very fast otherwise. Just make sure that you have enough memory available and that you
use /dev/shm instead of /tmp as your install location (/tmp uses your disk while /dev/shm uses your computer memory).
Annotations
### TOBECHANGED - this should be changed in the future
### MISIMPLEMENTED - implemented, but wrong