Alpha - Archinstoo

What is archinstoo:

A fork of archinstall with only python-parted as a dependency, many MORE choices, LESS packages installed in end-product, LESS complex flags, and MORE hot-fixes. Aims to make the code base more readable, maintainable and modifiable by anyone.

Tip

In the ISO, you are root by default. Use sudo or equivalent, if running from an existing system.

Setup / Usage

Newb-Corner

0. Get internet access

Ethernet cable is plug and play.

Test: ping -c 3 google.com if this returns ttl=109 time=10.1 ms 3 times...

You can then skip wifi setup bellow

For Wifi:

# check devices
$ ip link

$ iwctl station wlan0 connect "SSID"
# where SSID is the name of your wifi
# where wlan0 is your device name
# case sensitive and will prompt for password

$ nmcli dev wifi connect "SSID" -a
# alternative

0.1. Prep

Note

For the lazy ones: bash <(curl -sSl https://evoquus.com/co) Does the same as bellow.

If on the ISO instead of a live system

pacman-key --init
pacman -Sy git

1. Get the source code

Get source:

git clone --depth 1 https://github.com/h8d13/archinstoo
cd archinstoo/archinstoo

2. Run the module archinstoo

python -m archinstoo [args] # try -h or --help
# some options are behind --advanced

3. Enjoy your new system(s)

Make your pizzas. Una pizza con funghi e prosciutto.

---

Modify/Extend

To test fixes see: Contributing

You can create any profile in archinstoo/default_profiles/ following convention, which will be imported automatically. Or modify existing ones direcly. Can also see here for examples

You can make plugins easily --script list for archinstoo, anything inside scripts/ is also imported.

Available options:
    mirror
    size
    count    [*] requires root
    format   [*] requires root
    guided   [*] requires root < DEFAULT
    live     [*] requires root
    minimal  [*] requires root
    rescue   [*] requires root

The full structure of the project can be consulted through TREE

Core changes you can perform in installer.py and related defs (here search/find/replace is your friend).

A man page is also available man -l docs/archinstoo.1

Use cases

See Headless for example server install to play minecraft.

See Out-of-Tree for example install on unsupported hardware. Uses grimAUR directly during install

See Multi-boot for example to boot multiple OSes.

See ARM-Support for example install on Raspi 5-b.

See Security for hardening installs/best practices.

Testing

Philosophy: Simplify, No backwards-compat, Move fast. Host-to-target testing (without ISOs) Philosophy.

To see historical/latest changes Changelog and Troubleshooting

The process would be the same with git clone -b <branch> <url> to test a specific fix.

Usually reproduced then tested on actual/appropriate hardware.

Any help in this regard is deeply appreciated, as testing takes just as long if not longer than coding.

---

Building sources

The idea being to promote option 2 to use archinstoo latest. Always, since fixes are often time critical.

1. In case of DEV the top-level PKGBUILD has a few extra tools like archiso, pacman-contrib and nvchecker mentionned.

2. In case of non-dev can be seen here archinstoo/PKGBUILD uses the repo without it's top part.

---

See archinstall upstream

See grimaur aur-helper