No description
Mathieu Benoit
ed541dacc4
Removing a name from stage2.state means its stage-2 artefact is not trusted -- that is the whole meaning of removing it. The restore ignored that and put the package back anyway, undoing the fix that motivated the removal before the rebuild could run. It happened twice. binutils had to be moved out of repo2 by hand. filesystem was worse because it was invisible: its pass-one build predates the hook adding s390x's lib64 symlinks, so restoring it REMOVED the symlink stage 1 had just installed. /usr/lib64 was absent again and the fix looked like it had failed. pkgbase, not pkgname: stage2.state records what was built, and libxml2-docs is not in it under that name. The diagnosis also took a wrong turn worth recording. `test -L` failing was reported as "a real directory", but it fails just as readily on a path that does not exist -- which was the actual state. The check now says what the path IS. --- FR --- Retirer un nom de stage2.state signifie que son artefact d'étage 2 n'est plus de confiance — c'est tout le sens du retrait. La restauration l'ignorait et le réinstallait quand même, défaisant le correctif qui avait motivé le retrait avant que la reconstruction puisse tourner. Deux fois. binutils a dû être écarté de repo2 à la main. filesystem était pire car invisible : sa construction de la passe 1 précède le hook ajoutant les liens lib64 de s390x, donc le restaurer SUPPRIMAIT le lien que l'étage 1 venait de poser. /usr/lib64 disparaissait et le correctif semblait inopérant. pkgbase, pas pkgname : stage2.state enregistre ce qui a été bâti, et libxml2-docs n'y figure pas sous ce nom. Le diagnostic a aussi pris un mauvais chemin qui mérite d'être noté. L'échec de `test -L` était rapporté comme « vrai répertoire », alors qu'il échoue tout autant sur un chemin absent — l'état réel. Le test dit maintenant ce que le chemin EST. 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.