| Age | Commit message (Collapse) | Author |
|---|
|
We need to have two partitions in BIOS one for boot (grub)
and the other for root (/). The format of the boot partition
is ext2 (so it is added).
If disk is chosen to be encrypted, `then /etc/default/grub` is edited
as the followings: https://wiki.archlinux.org/title/Dm-crypt/Encrypting_an_entire_system#Configuring_GRUB_2
Issue: https://github.com/archlinux/archinstall/issues/586
This work is done while working on CachyOS which is Arch based and
it is using customized archinstaller.
To test these changes you can try CachyOS installer which supports
encrypted disk with grub (https://wiki.cachyos.org/).
Hamad
|
|
|
|
|
|
|
|
both initramfs and vmlinuz will have the trailing definitions, but made both {kernel}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Moving to `localectl` rather than local file manipulation *(both for listing locales and setting them)*.
* Swapped `loadkeys` for localectl.
* Renamed `main` to `maim` in awesome profile.
* Created `archinstall.Boot(<installation>)` which spawns a `systemd-nspawn` container against the installation target.
* Exposing systemd.py's internals to archinstall global scope.
* Re-worked `SysCommand` completely, it's now a wrapper for `SysCommandWorker` which supports interacting with the process in a different way. `SysCommand` should behave just like the old one, for backwards compatibility reasons. This fixes #68 and #69.
* `SysCommand()` now has a `.decode()` function that defaults to `UTF-8`.
* Adding back peak_output=True to pacstrap.
Co-authored-by: Anton Hvornum <anton.feeds@gmail.com>
Co-authored-by: Dylan Taylor <dylan@dylanmtaylor.com>
|
|
|
|
cpu_vendor() output.
|
|
|
|
|
|
|
|
https://docs.python-guide.org/writing/gotchas/#mutable-default-arguments
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Update installer.py
|
|
|
|
was specified. Also fixes a regression bug with line endings in the loader configuration.
|
|
|
|
torxed-kernel-params
|
|
|
|
complaints while still retaining the same functionality, kinda. It's less automatic but it's also less of dark magic, which makes sense for anyone but me.
|
|
|
|
|
|
|
|
They now live as a installation-session variable. Not just minimal installation.
|
|
Make changes suggested by Torxed
|
|
|
|
plugins can hook in to in order to be called during specific on_<event> calls.
|
|
* Added a postgres application profile. Also introducing runas to the arch_chroot of the installation, to run commands as emulated users. This is highly WIP at the moment.
* Fixing top-level-listing of profiles. As well as testing some postgres installation steps.
* Removed dupe functions.
* Added safety check in case a comment mentions the top level profile thing.
* Patching namespace corruption.
* Avoiding runtime collision due to installation not being initiated yet.
* Allow for parameterization of filesystem in guided.
Co-authored-by: Anton Hvornum <anton.feeds@gmail.com>
|
|
* Cleaning up packages. installer now relies on __packages__ definition. Which will work with external libs to more easily gather packages used by installer and profiles.
* Added back the logic for the log message, where we inform if we're adding the boot loader to root or boot.
* Added __package__ definition to profiles and the installer. These packages can be used as an indication from outside libraries of what could *possibly* be installed. For instance an offline-tool could source these, it would source more than it needed to, but it would give a quick rundown of what might be needed.
* Removed import of __base__packages__ as it's now just __packages__ after a lot of stream-lining.
* Explosion misspelling.
Co-authored-by: Anton Hvornum <anton.feeds@gmail.com>
|
|
with dualboot variables. This **NEEDS** to be tested together with a Windows installation dual-boot setup, because this is where variable writing caused issues before.
|
|
|
|
|
|
|
|
|
|
|
|
|