Few days ago I landed on this wonderful project because I was developing a custom OS based on Arch Linux. I built my distro with all what I needed and I used ALCI for building an ISO installer (because I see ALCI is comfortable for making it).
I make the installer in a right way (also thank you for the YT videos of Erik), the only issue was that, when I enter by liveuser on the login window, or by my user after the installation of the OS, when I insert the password and I press Enter, the system spawns some strings cause by an unknown misbehavior:
And it remains on this state for about 20 seconds or more. If I use autologin, I enter directly without this issue.
So, I did a test with a alci-iso-pure (https://github.com/arch-linux-calamares ... i-iso-pure) and I built the installer without touching the package list file. After the installation I got the cli-only environment, so I installed gdm, gnome and then I executed systemctl enable gdm and I rebooted for getting the login GUI window. At the login page, when I inserted the password of the user, I got the same misbehavior. Is it a bug on alci-iso-pure when interfacing with gdm?
Furthermore, I'm new on ArcoLinux project, but I have some doubts on how to lead my project. My basic assumptions are:
- OS based on Arch Linux
- Using GNOME 42
- Use GDM as display manager
- Use only the minimal services and applications I need for the purpose of the OS (for this reason I started with Arch Linux and alci-iso-pure).
- Building a customized installer as Calamares style
On ArcoLinux project I see a lot of stuff like ALCI, CARLI, ArcoLinux itself and so on, so my further question is:
am I right I built the installer for my OS by using ALCI (in particular alci-iso-pure) or I needed to follow a different path/instruments?
Is ALCI the most suggested instrument to build a custom calamares-based installer for my OS?
Sorry for my long post.
Thank you in advance!
