No description
Three gaps in the driver, all found by packages advancing to their next obstacle. no checkout for python-jinja Stage 2 could only rebuild what stage 1 had cloned -- wrong for every package stage 2 builds and stage 1 cannot. libxslt was the first (Ubuntu's libxml2 is too old to configure it), the Python set followed. They are named in CHROOT_STAGE2_PKGS because only this stage can produce them, and this stage would not fetch them. It clones now, pinned to upstream.lock. error: problem setting DownloadUser 'alpm' (user does not exist) The rebuilt pacman drops privileges for downloads to a user created by sysusers.d, which `pacman --root` does not run -- the same reason the CA bundle was never generated. Nothing in the chroot downloads anything. :: zlib-ng-compat and zlib are in conflict zlib-ng produces zlib-ng-compat, correct and belonging in repo2, uninstallable beside the zlib this chroot uses. CHROOT_EXCLUDE already said so for populate; the same list now applies to the per-package install. --- FR --- Trois lacunes du pilote, toutes révélées par des paquets parvenus à leur obstacle suivant. no checkout for python-jinja L'étage 2 ne savait reconstruire que ce que l'étage 1 avait cloné — faux pour tout paquet que l'étage 2 bâtit et que l'étage 1 ne peut pas. libxslt fut le premier (le libxml2 d'Ubuntu est trop ancien), l'ensemble Python a suivi. Ils figurent dans CHROOT_STAGE2_PKGS parce que seul cet étage les produit, et cet étage refusait de les chercher. Il clone désormais, épinglé sur upstream.lock. error: problem setting DownloadUser 'alpm' (user does not exist) Le pacman reconstruit abaisse ses privilèges vers un utilisateur créé par sysusers.d, que `pacman --root` n'exécute pas — la raison même pour laquelle le faisceau de certificats n'était jamais généré. Rien ne télécharge dans ce chroot. :: zlib-ng-compat et zlib sont en conflit zlib-ng produit zlib-ng-compat, juste et à sa place dans repo2, ininstallable à côté du zlib de ce chroot. CHROOT_EXCLUDE le disait déjà pour le peuplement ; la même liste vaut maintenant pour l'installation par paquet. Assisted-by: Claude Opus 5 |
||
|---|---|---|
| .github/workflows | ||
| arch-kernel | ||
| boot | ||
| patches | ||
| scripts | ||
| .env.example | ||
| .gitignore | ||
| CODEOWNERS | ||
| Containerfile | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| RELAIS.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.