The ALIS project will evolve over time – in these few days Budgie and Bspwm have been added for example.
We will maintain this project only periodically. Our main attention goes to ArcoLinux.

So from time to time you do a git pull in the folder of the ALIS project.

https://github.com/picodotdev/alis/

We show you the workflow in the video.

It is by comparing that we learn the code.

Having a second -dev folder forces you to check again and catch the human errors.

  • Introduced a new configuration for installing Arch Linux using ALIS scripts and emphasized the importance of making personal choices in the setup.
  • Highlighted the ability to build an Arch Linux ISO with a folder containing all scripts and personalized settings without needing to download an existing ISO.
  • Mentioned the relevance of keeping ALIS scripts up to date by comparing personal code to the new code from the ALIS project periodically.
  • Discussed removing certain features like the Control+Backspace function to avoid conflicts with existing Arch Linux configurations.
  • Added a script to automatically clone the ArcoLinux Nemesis GitHub repository for later execution.
  • Emphasized the minimal impact of scripts on ISO size, noting that Arch Linux is inherently minimal and grows slowly in size.
  • Advised on the importance of refreshing and double-checking changes before pushing them online to ensure accuracy and efficiency.
  • Showed the process of building an Arch Linux ISO with ALIS, including deleting old configurations and cloning new ones to ensure the latest setup.
  • Demonstrated the convenience of an automated, unattended installation that pulls in new code and applies selected parameters for a personalized Arch Linux system.
  • Concluded with showcasing the customization and theming capabilities post-installation, leveraging scripts for a tailored Arch Linux experience with XFCE.
  • Video discusses maintenance of the AA now ARISER¬†project, highlighting the challenge of balancing many tasks with limited time.
  • Received an update from Pico, indicating changes to the ALIS scripts, emphasizing the need for regular updates and maintenance checks.
  • Demonstrates how to use tools like GitKraken to review changes made by Pico, including improvements like timing for desktop environment installations and the addition of the Gnome terminal in Cinnamon.
  • Discusses the process of comparing personal code with Pico’s updates, learning from new code, and deciding what changes to incorporate.
  • Specific updates mentioned include adding PackageKit Qt5 for Discover support in Plasma and ensuring Gnome terminal is included in Cinnamon setups.
  • Stresses the importance of local control over updates to tailor the ALIS installation process according to personal preferences.
  • Suggests using comparison tools to spot and learn from code differences, making maintenance a learning opportunity.
  • Highlights the addition of Budgie desktop environment support, along with essential packages for a functional Budgie setup.
  • Encourages viewers to regularly compare their code with the official ALIS project to incorporate desirable updates and maintain an up-to-date system.
  • Concludes with the process of pushing confirmed changes to the internet for community access and preparing for further testing, particularly of the newly added Budgie environment.

Booting and virtual machines

VirtualBox and VMware designate drives as /dev/sda, while Qemu identifies them as /dev/vda.

Alternatively, opting for 'auto' allows the script to automatically select the appropriate option.

Grub is compatible with both BIOS and UEFI systems.

Refind and systemd are exclusively compatible with UEFI environments. (Configure your virtual machine to match these requirements)

We manage our githubs with two scripts. Use them as a template but change them. Download here.