No description
Mathieu Benoit
d1ac7a94f9
Four packages failed in prepare() on Failed to clone 'gl-mod/bootstrap' a second time, aborting The first diagnosis was DNS, and it was right: the chroot had no resolv.conf. Copying it made resolution work -- `getent hosts github.com` answers -- and the clones still failed, now on error adding trust anchors from file: /etc/ssl/certs/ca-certificates.crt Everything needed was already installed: the symlink, the Mozilla trust source, update-ca-trust, p11-kit's trust. What was missing is that the bundle they produce is made by an ALPM HOOK, and `pacman --root` does not run hooks. So the target of that symlink never existed, and a package list cannot tell a dangling symlink from a working installation. Generated from our own trust source, not copied from the host, and counted rather than trusted: update-ca-trust exits 0 on an empty source, and what that hides is an https failure hours later. 121 certificates; the clone works. --- FR --- Quatre paquets ont échoué dans prepare() sur Failed to clone 'gl-mod/bootstrap' a second time, aborting Le premier diagnostic était le DNS, et il était juste : le chroot n'avait pas de resolv.conf. Le copier a rétabli la résolution — `getent hosts github.com` répond — et les clones échouaient toujours, désormais sur error adding trust anchors from file: /etc/ssl/certs/ca-certificates.crt Tout le nécessaire était installé : le lien, la source de confiance Mozilla, update-ca-trust, le trust de p11-kit. Ce qui manquait, c'est que le faisceau qu'ils produisent est fabriqué par un hook ALPM, et `pacman --root` n'exécute pas les hooks. La cible du lien n'a donc jamais existé, et une liste de paquets ne distingue pas un lien mort d'une installation valide. Généré depuis notre propre source de confiance, non copié de l'hôte, et compté plutôt que cru : update-ca-trust sort en 0 sur une source vide, et ce que cela masque est un échec https des heures plus tard. 121 certificats ; le clone passe. Assisted-by: Claude Opus 5 |
||
|---|---|---|
| .github/workflows | ||
| arch-kernel | ||
| boot | ||
| patches | ||
| scripts | ||
| .env.example | ||
| .gitignore | ||
| CODEOWNERS | ||
| Containerfile | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| TODO.md | ||
Arch Linux s390x
A port of Arch Linux to IBM s390x mainframe architecture with systemd support.
Boots a full Arch Linux system on IBM mainframes (or QEMU s390x emulation) using a hybrid build: cross-compilation for the kernel, native s390x compilation on z/VM for userspace.
Quick Start
make container # build dev container (first time)
cp .env.example .env # configure z/VM access
make all # build kernel + initramfs + systemd
make test-systemd # boot it
What Works
- Arch Linux kernel 6.18.6-arch1 with Arch patches, cross-compiled
- Initramfs via modified mkinitcpio
- Static busybox built natively on z/VM, 2.3MB
- Root filesystem with ext4, switch_root to real rootfs
- Systemd as PID 1
Pacman, bash, and GNU coreutils are not yet ported.
Build System
The build uses two tiers:
Cross-compilation (x86_64 host): Kernel is built in a Fedora 43 container with s390x-linux-gnu-gcc. Initramfs is generated with a patched mkinitcpio that handles cross-architecture binary injection.
Native compilation (s390x z/VM): Busybox and systemd must be built on real s390x hardware. The z/VM system runs RHEL 9.6 with GCC 11.5.0. Scripts handle SSH deployment and retrieval automatically via .env configuration.