The custom settings for Calamares is in here GitHub - dmknght/calamares-settings-netinst: Netinstall configurations
I’ll merge the settings into calamares-settings-parrot
as soon as it’s ready.
Differences between this and Architecture
Calamares | Architecture | |
---|---|---|
Installer | Calamares | Debian’s Netinstaller |
— | — | — |
Live mode | Yes | No |
— | — | — |
Encrypt /boot when use LUKS |
Yes | No (likely) |
— | — | — |
Fully customizable | Almost | Not really |
The NetInstaller of Calamares will provide as many packages as selectable options so users can select whatever they want for Parrot OS, even no Desktop Environment target. No systemd
? It’s fine. I’m having a list (and doing the test) of systemd alternative
. Meanwhile Architecture provides limited selectable options to choose Desktop Environment and some meta packages.
Calamares’s NetInstaller Limitation:
- Stable network connection is highly required
- It’s slow. It uses
debootstrap
to create system. There’s no multithreading installing packages. For example: this error can happen easily
- It uses
debootstrap
, therefore the are many configurations are missing during installation. For example: missing group when install a package
- Users must know what to install or the target system will be a broken system. It’s not easy to balance between “not having too many unused packages” and “install required packages that system needs”.
- Packages failed to install because of
stdin
requirement. For example: replace settings in/etc/
requires user to typeY
to confirm but the installer has no interactive method (trying to fix this).