News: 0001611336

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

NetBSD's Kernel Supports Lua Scripting But Don't Look For Rust In There Anytime Soon

([BSD] 12 Minutes Ago No Rust In NetBSD Kernel)


For those not fond of the increasing use of the Rust programming language within the Linux kernel or [1]FreeBSD's considerations for Rust in its kernel , you can perhaps find refuge within NetBSD. One of the NetBSD developers has explained why you likely won't be finding Rust code within the NetBSD kernel anytime soon.

NetBSD developer Benny Siegert who also works for Google wrote a blog post this week explaining why there likely won't be Rust code within its kernel anytime soon. That's even with [2]NetBSD's kernel supporting Lua scripts as a unique trait.

Diminishing the prospects of Rust code within the NetBSD kernel is that there are many CPU architectures supported where Rust isn't even available. That would be the lead and immediate blocker to Rust programming language use by NetBSD that supports a diverse array of architectures in a meaningful manner.

Maintaining Rust support has also been challenging with their package management. Also sharply pushing out any idea of using Rust in the NetBSD kernel is that NetBSD's release cycles not aligning with Rust. NetBSD supports the last two major releases and that means NetBSD 9.0 from 2020 and Rust 1.41 of that the isn't too practical: " If Rust 1.41 had been part of NetBSD 9, it would be useless for anything except compiling NetBSD itself – Rust 1.41 is so old that basically no modern code would compile with it. Not great. "

All the details on why you likely won't find Rust in the NetBSD kernel soon can be found on Benny Siegert's [3]blog .



[1] https://www.phoronix.com/news/FreeBSD-Considers-Rust-Base

[2] https://www.phoronix.com/news/MTMwMTU

[3] https://bentsukun.ch/posts/netbsd-rust-kernel/



=== ALL USERS PLEASE NOTE ========================

JCL support as alternative to system menu.

In our continuing effort to support languages other than LISP on the CADDR,
we have developed an OS/360-compatible JCL. This can be used as an
alternative to the standard system menu. Type System J to get to a JCL
interactive read-execute-diagnose loop window. [Note that for 360
compatibility, all input lines are truncated to 80 characters.] This
window also maintains a mouse-sensitive display of critical job parameters
such as dataset allocation, core allocation, channels, etc. When a JCL
syntax error is detected or your job ABENDs, the window-oriented JCL
debugger is entered. The JCL debugger displays appropriate OS/360 error
messages (such as IEC703, "disk error") and allows you to dequeue your job.