| 28 Jun 2024 |
 aleksana (force me to bed after 18:00 UTC) | You may be the first individual I have ever seen who owns a s390x server | 18:12:25 |
 bl0v3 | so there are no easy guides | 18:12:28 |
| bl0v3 | or any | 18:12:32 |
| bl0v3 | In reply to @aleksana:mozilla.org
You may be the first individual I have ever seen who owns a s390x server i mean its old these days | 18:12:55 |
| bl0v3 | 2008 | 18:12:58 |
| aleksana (force me to bed after 18:00 UTC) | Although I've thought about that like "If I become very rich in the future, I will definitely buy a server like a double-door refrigerator and put it at home" | 18:13:23 |
| aleksana (force me to bed after 18:00 UTC) | So I can only say good luck | 18:13:35 |
| bl0v3 | but yeah why would one own this shit realistically, its weights over a ton and eats power | 18:13:43 |
| bl0v3 | so i want to make it slightly less useless by putting nix on it for the lulz | 18:14:10 |
| bl0v3 | Pr wise its also interesting. Cause traditionally netbsd folk used to brag about it running everywhere | 18:15:28 |
| bl0v3 | so running nixos would be funny i figure | 18:15:40 |
| bl0v3 | im sorta just looking for the simplest way i can generate a boot spec so i can refactor the extlinux bootloader targets like i did for some ebedded things | 18:16:27 |
| bl0v3 | pxe boot seems possible too but like i do want a persistant install | 18:16:58 |
 7c6f434c | Wait these are mainframes so the bottom hypervisor is always from IBM and you run stuff in VMs, right? | 18:17:54 |
| bl0v3 | In reply to @7c6f434c:nitro.chat
Wait these are mainframes so the bottom hypervisor is always from IBM and you run stuff in VMs, right? i have no clue | 18:18:10 |
| 7c6f434c | The bright side is that there is something https://wiki.ubuntu.com/S390X | 18:18:28 |
| bl0v3 | its sorta what im trying to figure out | 18:18:28 |
| 7c6f434c | https://en.wikipedia.org/wiki/Linux_on_IBM_Z says that mainframes mean everything has to be somewhat virtualised | 18:18:51 |
| bl0v3 | In reply to @7c6f434c:nitro.chat
The bright side is that there is something https://wiki.ubuntu.com/S390X gives me a 503 | 18:19:27 |
| 7c6f434c |
The boot loader for the s390x architecture is "zipl" (z initial program loader).
| 18:20:39 |
| bl0v3 | well i gotta go work on something else now but i can as it seems build a minimal system configuration already , though it would be useful to build some thing i can test in qemu before putting it on there | 18:20:55 |
| 7c6f434c | Loads for me but very slowly | 18:21:02 |
| 7c6f434c | * wiki page loads for me but very slowly | 18:21:10 |
| bl0v3 | https://www.ibm.com/docs/en/linux-on-systems?topic=u-boot-device | 18:22:48 |
| bl0v3 | actually this looks promising | 18:22:54 |
| bl0v3 | will look into this later | 18:22:58 |
| 7c6f434c | https://www.qemu.org/docs/master/system/s390x/bootdevices.html QEMU might support emulating the boot for the mainframes (but not most of the hardware) | 18:23:20 |
| bl0v3 | In reply to @7c6f434c:nitro.chat
https://www.qemu.org/docs/master/system/s390x/bootdevices.html QEMU might support emulating the boot for the mainframes (but not most of the hardware) as i recall afaik that only runs via netboot, gotta check sorta busy rn | 18:24:02 |
| bl0v3 | will deffo continue this though | 18:24:11 |
| bl0v3 | just no time rn | 18:24:15 |
