home.social

#s390x — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #s390x, aggregated by home.social.

  1. offlineimap3 cannot enter #debian testing because it fails to compile on s390x, which seems to be an IBM mainframe architecture from the 90’s.

    I’m really curious how much #s390x computers still exist that are running the latest Debian…

    (yes, #offlineimap is a critical part of my setup for offline emailing)

    qa.debian.org/excuses.php?pack

    (wasn’t @jgoerzen involved in offlineimap?)

    UPDATE: I was wrong, s390x is not legacy but still widely used!

  2. offlineimap3 cannot enter #debian testing because it fails to compile on s390x, which seems to be an IBM mainframe architecture from the 90’s.

    I’m really curious how much #s390x computers still exist that are running the latest Debian…

    (yes, #offlineimap is a critical part of my setup for offline emailing)

    qa.debian.org/excuses.php?pack

    (wasn’t @jgoerzen involved in offlineimap?)

    UPDATE: I was wrong, s390x is not legacy but still widely used!

  3. offlineimap3 cannot enter #debian testing because it fails to compile on s390x, which seems to be an IBM mainframe architecture from the 90’s.

    I’m really curious how much #s390x computers still exist that are running the latest Debian…

    (yes, #offlineimap is a critical part of my setup for offline emailing)

    qa.debian.org/excuses.php?pack

    (wasn’t @jgoerzen involved in offlineimap?)

    UPDATE: I was wrong, s390x is not legacy but still widely used!

  4. offlineimap3 cannot enter #debian testing because it fails to compile on s390x, which seems to be an IBM mainframe architecture from the 90’s.

    I’m really curious how much #s390x computers still exist that are running the latest Debian…

    (yes, #offlineimap is a critical part of my setup for offline emailing)

    qa.debian.org/excuses.php?pack

    (wasn’t @jgoerzen involved in offlineimap?)

    UPDATE: I was wrong, s390x is not legacy but still widely used!

  5. offlineimap3 cannot enter #debian testing because it fails to compile on s390x, which seems to be an IBM mainframe architecture from the 90’s.

    I’m really curious how much #s390x computers still exist that are running the latest Debian…

    (yes, #offlineimap is a critical part of my setup for offline emailing)

    qa.debian.org/excuses.php?pack

    (wasn’t @jgoerzen involved in offlineimap?)

    UPDATE: I was wrong, s390x is not legacy but still widely used!

  6. Running #Forgejo is cool. 😎
    Forgejo on an IBM #S390X CPU running #Linux is even cooler. 🪭
    snapcraft.io/forgejo

  7. Running #Forgejo is cool. 😎
    Forgejo on an IBM #S390X CPU running #Linux is even cooler. 🪭
    snapcraft.io/forgejo

  8. Running #Forgejo is cool. 😎
    Forgejo on an IBM #S390X CPU running #Linux is even cooler. 🪭
    snapcraft.io/forgejo

  9. Running #Forgejo is cool. 😎
    Forgejo on an IBM #S390X CPU running #Linux is even cooler. 🪭
    snapcraft.io/forgejo

  10. Running #Forgejo is cool. 😎
    Forgejo on an IBM #S390X CPU running #Linux is even cooler. 🪭
    snapcraft.io/forgejo

  11. The #s390x open source software team at IBM confirms the latest versions of various software packages run well on #Linux on #IBMZ & #LinuxONE 🐧

    In October 2025 validation was maintained for two dozen projects, including #ApacheActiveMQ #InfluxDB & #Rails 🎉

    We also on-boarded libdfp & qsv to our new hosted GitHub Actions runners, and saw Rarr add CI and VictoriaTraces begin releasing binaries 🎁

    Details in my monthly report: community.ibm.com/community/us

  12. The #s390x open source software team at IBM confirms the latest versions of various software packages run well on #Linux on #IBMZ & #LinuxONE 🐧

    In October 2025 validation was maintained for two dozen projects, including #ApacheActiveMQ #InfluxDB & #Rails 🎉

    We also on-boarded libdfp & qsv to our new hosted GitHub Actions runners, and saw Rarr add CI and VictoriaTraces begin releasing binaries 🎁

    Details in my monthly report: community.ibm.com/community/us

  13. The #s390x open source software team at IBM confirms the latest versions of various software packages run well on #Linux on #IBMZ & #LinuxONE 🐧

    In October 2025 validation was maintained for two dozen projects, including #ApacheActiveMQ #InfluxDB & #Rails 🎉

    We also on-boarded libdfp & qsv to our new hosted GitHub Actions runners, and saw Rarr add CI and VictoriaTraces begin releasing binaries 🎁

    Details in my monthly report: community.ibm.com/community/us

  14. The #s390x open source software team at IBM confirms the latest versions of various software packages run well on #Linux on #IBMZ & #LinuxONE 🐧

    In October 2025 validation was maintained for two dozen projects, including #ApacheActiveMQ #InfluxDB & #Rails 🎉

    We also on-boarded libdfp & qsv to our new hosted GitHub Actions runners, and saw Rarr add CI and VictoriaTraces begin releasing binaries 🎁

    Details in my monthly report: community.ibm.com/community/us

  15. The #s390x open source software team at IBM confirms the latest versions of various software packages run well on #Linux on #IBMZ & #LinuxONE 🐧

    In October 2025 validation was maintained for two dozen projects, including #ApacheActiveMQ #InfluxDB & #Rails 🎉

    We also on-boarded libdfp & qsv to our new hosted GitHub Actions runners, and saw Rarr add CI and VictoriaTraces begin releasing binaries 🎁

    Details in my monthly report: community.ibm.com/community/us

  16. Either someone found the vanilla #linux-next builds fpr #s390x useful, which I enabled a few days ago in my #Fedora Linux #copr[1] – or it was just some AI crawler that made the number in the download stats go up from 0 to 32. 🤷

    These days you never know. #moderntimes #kernel #LinuxKernel

    [1] copr.fedorainfracloud.org/copr

  17. Either someone found the vanilla #linux-next builds fpr #s390x useful, which I enabled a few days ago in my #Fedora Linux #copr[1] – or it was just some AI crawler that made the number in the download stats go up from 0 to 32. 🤷

    These days you never know. #moderntimes #kernel #LinuxKernel

    [1] copr.fedorainfracloud.org/copr

  18. Either someone found the vanilla #linux-next builds fpr #s390x useful, which I enabled a few days ago in my #Fedora Linux #copr[1] – or it was just some AI crawler that made the number in the download stats go up from 0 to 32. 🤷

    These days you never know. #moderntimes #kernel #LinuxKernel

    [1] copr.fedorainfracloud.org/copr

  19. Either someone found the vanilla #linux-next builds fpr #s390x useful, which I enabled a few days ago in my #Fedora Linux #copr[1] – or it was just some AI crawler that made the number in the download stats go up from 0 to 32. 🤷

    These days you never know. #moderntimes #kernel #LinuxKernel

    [1] copr.fedorainfracloud.org/copr

  20. Either someone found the vanilla #linux-next builds fpr #s390x useful, which I enabled a few days ago in my #Fedora Linux #copr[1] – or it was just some AI crawler that made the number in the download stats go up from 0 to 32. 🤷

    These days you never know. #moderntimes #kernel #LinuxKernel

    [1] copr.fedorainfracloud.org/copr

  21. The #s390x open source software team at IBM confirms the latest versions of various software packages run well on #Linux on #IBMZ & #LinuxONE 🐧

    The report from July is extra special because it includes details of the first projects we on-boarded to our hosted #GitHub Actions service! You can also get an update into the latest from the ngrok community and FlatCC.

    Details here: community.ibm.com/community/us

  22. The #s390x open source software team at IBM confirms the latest versions of various software packages run well on #Linux on #IBMZ & #LinuxONE 🐧

    The report from July is extra special because it includes details of the first projects we on-boarded to our hosted #GitHub Actions service! You can also get an update into the latest from the ngrok community and FlatCC.

    Details here: community.ibm.com/community/us

  23. The #s390x open source software team at IBM confirms the latest versions of various software packages run well on #Linux on #IBMZ & #LinuxONE 🐧

    The report from July is extra special because it includes details of the first projects we on-boarded to our hosted #GitHub Actions service! You can also get an update into the latest from the ngrok community and FlatCC.

    Details here: community.ibm.com/community/us

  24. The #s390x open source software team at IBM confirms the latest versions of various software packages run well on #Linux on #IBMZ & #LinuxONE 🐧

    The report from July is extra special because it includes details of the first projects we on-boarded to our hosted #GitHub Actions service! You can also get an update into the latest from the ngrok community and FlatCC.

    Details here: community.ibm.com/community/us

  25. The #s390x open source software team at IBM confirms the latest versions of various software packages run well on #Linux on #IBMZ & #LinuxONE 🐧

    The report from July is extra special because it includes details of the first projects we on-boarded to our hosted #GitHub Actions service! You can also get an update into the latest from the ngrok community and FlatCC.

    Details here: community.ibm.com/community/us

  26. The #s390x open source software team at IBM confirms the latest versions of various software packages run well on #Linux on #IBMZ & #LinuxONE 🐧

    In June 2025 validation was maintained for over two dozen, including #Apache #Storm, #Envoy and #Falco 🎉

    Plus various release additions from the broader open source community, including: NATS-box (containers), cnquery (ci, binaries) & Encrust (ci)

    Full report + how your project can apply for a s390x VM: community.ibm.com/community/us

  27. The #s390x open source software team at IBM confirms the latest versions of various software packages run well on #Linux on #IBMZ & #LinuxONE 🐧

    In June 2025 validation was maintained for over two dozen, including #Apache #Storm, #Envoy and #Falco 🎉

    Plus various release additions from the broader open source community, including: NATS-box (containers), cnquery (ci, binaries) & Encrust (ci)

    Full report + how your project can apply for a s390x VM: community.ibm.com/community/us

  28. The #s390x open source software team at IBM confirms the latest versions of various software packages run well on #Linux on #IBMZ & #LinuxONE 🐧

    In June 2025 validation was maintained for over two dozen, including #Apache #Storm, #Envoy and #Falco 🎉

    Plus various release additions from the broader open source community, including: NATS-box (containers), cnquery (ci, binaries) & Encrust (ci)

    Full report + how your project can apply for a s390x VM: community.ibm.com/community/us

  29. The #s390x open source software team at IBM confirms the latest versions of various software packages run well on #Linux on #IBMZ & #LinuxONE 🐧

    In June 2025 validation was maintained for over two dozen, including #Apache #Storm, #Envoy and #Falco 🎉

    Plus various release additions from the broader open source community, including: NATS-box (containers), cnquery (ci, binaries) & Encrust (ci)

    Full report + how your project can apply for a s390x VM: community.ibm.com/community/us

  30. The #s390x open source software team at IBM confirms the latest versions of various software packages run well on #Linux on #IBMZ & #LinuxONE 🐧

    In June 2025 validation was maintained for over two dozen, including #Apache #Storm, #Envoy and #Falco 🎉

    Plus various release additions from the broader open source community, including: NATS-box (containers), cnquery (ci, binaries) & Encrust (ci)

    Full report + how your project can apply for a s390x VM: community.ibm.com/community/us

  31. I'm trying to boot #ubuntu 16.04 for #s390x in #qemu but all I get for that one particular image is, including the dots:

    LOADPARM=[ ]

    Using virtio-blk.
    Using SCSI scheme.
    ....

    Subsequent images (18.04+) boot fine. I found description of s390x bios and bootindex parameter but I am explicitly passing it.

  32. I'm trying to boot 16.04 for in but all I get for that one particular image is, including the dots:

    LOADPARM=[ ]

    Using virtio-blk.
    Using SCSI scheme.
    ....

    Subsequent images (18.04+) boot fine. I found description of s390x bios and bootindex parameter but I am explicitly passing it.

  33. I'm trying to boot #ubuntu 16.04 for #s390x in #qemu but all I get for that one particular image is, including the dots:

    LOADPARM=[ ]

    Using virtio-blk.
    Using SCSI scheme.
    ....

    Subsequent images (18.04+) boot fine. I found description of s390x bios and bootindex parameter but I am explicitly passing it.

  34. I'm trying to boot #ubuntu 16.04 for #s390x in #qemu but all I get for that one particular image is, including the dots:

    LOADPARM=[ ]

    Using virtio-blk.
    Using SCSI scheme.
    ....

    Subsequent images (18.04+) boot fine. I found description of s390x bios and bootindex parameter but I am explicitly passing it.

  35. The #s390x open source software team at IBM confirms the latest versions of various software packages run well on #Linux on #IBMZ & #LinuxONE 🐧

    In May 2025 validation was maintained for over two dozen, including #CockroachDB #Grafana & #Ruby 🎉

    Plus various release additions from the broader open source community, including: libebml & libmatroska (ci), Zig lang (binaries, containers), and setup-uv (ci, binaries)

    Full report + how your project can apply for a s390x VM: community.ibm.com/community/us