@santi @muito_pelo @goosey propably because they want to renew interest amd potentially gain new licensees.

• Not shure why anyone would choose #RiscOS in 2026 and it's "Cooperative Multitasking" but maybe a 'mature codebase' makes it more interesting. Similar to #OpenVMS ¹, #QNX ², #VxWorks ³ and #WindRiverLinux ⁴ trying to increase adoption by those that demand a more hardened and deterministic performing OS…

@w84death @whitequark @landley the idea behind @OS1337 is not dissimilar from #VxWorks and #WindRiverLinux in that one can build their own #custom minimalist #Linux...

• It's still in early concept but longterm I do intent to flesh it out into something more useful, maximizing the abilities one has with #Frugalcomputing, because an 80x25 #Terminal should be all that's needed still...

https://os1337.com

AMD Embedded+ mini-ITX Board features Ryzen AI Embedded P132 CPU, Versal AI Edge Gen2 VE3558 SoC FPGA

https://web.brid.gy/r/https://www.cnx-software.com/2026/01/11/amd-embedded-mini-itx-board-features-ryzen-ai-embedded-p132-cpu-versal-ai-edge-gen2-ve3558-soc-fpga/

@ghul @jti42 @pkal @landley precisely!

Besides: All those big corpos contributing don't do so out of kindness either, but because none of them want to cough up way more money for a #CCSS alternative like Wind River #VxWorks, #Oracle #Solaris or god forbid #IBM #zArchitecture #Mainframes!

• #Android will need to have a #Community #Fork unless #Google instantly and retroactively revers their "#Developer #Verification" bs even for non-#GooglePlay #Apps!

@landley granted I do share that goal for @OS1337 abeit with way less priority (as I'm content with a #VxWorks-like approach for now!)

• But also because I am kinda lazy and don't want to "reinvent the wheel" and instead 'just wait & pull from upstream' [#toybox] because I suck at coding [outside of bash and some other small stuff]…

All I want to do re: _OS/1337 is merely do the bare minimum necessary to quickly build custom, verifyable & reproduceable system images to boot as well as include whatever tools that one wants in it.

• And ideally I want to just pull vanilla codebases and just have configurations for *each supported architecture [currently i486 only but others are planned too] to target:
  • Basically just having to specify the target and roll that way.

Since the build scripts are all #bash, 'self-hosting' (building itself under itself) should be totally in the cards and as soon as #mkroot can do it, I intent to follow suit in this functionality...

#OS1337

@eickot @nixCraft it should ideally be a self-hosting development envoirment but even if it's just a better #VxWorks that'll already be nice!

@nixCraft this makes total sense for #CriticalInfrastructure control systems as well as #aerospace applications.

• Which is good because there needs to be more competition to the likes of #VxWorks!

#RTOS #Realtime #OS #OperatingSystem #FLOSS #Irobclad #IroncladOS

@estherschindler I worked on the MIPS, PowerPC, and ARM architecture layers and BSPs for #VxWorks at #WindRiverSystems back from 1999‐2004, and then moved on to their embedded Linux kernel and BSPs, so if it is a general question, I might be able to help a little.... haven't kept up with it since then though.

Are there any active #VxWorks online communities? Where do those developers hang out? I have questions for them.

Are there any active #VxWorks online communities? Where do those developers hang out? I have questions for them.

@personifieddevil @BrodieOnLinux yes and no.

• You know.how much old stuff is still being deployed?

The #SpaceShuttle program got aborted because they couldn't get new old stock of radiation hardened chips, and to this day you have stuff like #ISA cards and #i486 systems in many #CriticalInfrastructure because noone can or wants to reimplement systems.

• GE literally used #PDP11's to automatically control their nuclear reactor designs because as old as they are the design has been known to work and re-certifying something new is basically almost impossible and not financially feasible.

And believe it or not, #git may be part of the toolchain for something that runs #VxWorks and goes into space:

• Stuff like the #MarsHelicopter being cobbled together from modern #Smartphone parts is more of an accident than actual planning, because it was a severly constrained effort.

As for #Rust, I rarely see benefits outweight the costs…

Anyone here knowledgeable about #VxWorks and #VxWin?

Please boost.

Understanding RTOS in Automotive Embedded Systems

Join yours Educational open Source community
👉 Download Now from Google Play
🔗 https://play.google.com/store/apps/details?id=com.piembsystech&pcampaignid=web_share
👉 Visit for more :
🌍 https://piembsystech.com/rtos-concept/

#RTOS #RealTimeOperatingSystem #EmbeddedSystems #AutomotiveEmbedded #EmbeddedEngineer #AUTOSAR #ECUDevelopment #ADAS #FunctionalSafety #ISO26262 #AutomotiveSoftware #AutomotiveTechnology #Microcontroller #FreeRTOS #QNX #VxWorks #FirmwareDevelopment #EmbeddedC #AutomotiveInnovation

@mrmasterkeyboard @landley glad I could get you guys connected then...

I'm convinced #toybox is a good #userland to get a basic OS up and running and on it's feet. If it's good enough for #Android then it's certainly gonna be good enough for #embedded stuff as well...

• After all that seems to be the main goal of it: Allowing "self-hosting" as in building itself under itself if not deliver under the same OS...

I don't leverage that capability with #OS1337 (at least for now) but that's because I treat it more akin to how #VxWorks and #WindRiverLinux is being developed and deployed...

#VxWorks, a real-time operating system (RTOS) by Wind River, has been in development since 1980s. It is used in deterministic, real-time and safety-critical applications. Many well-known modern aircraft are running VxWorks on board. VxWorks has been heavily influenced by #Unix
Via @unix_byte

@soc @dysfun @musl well, every single piece of software is!

• Show me a poeve of software, #FLOSS or #CCSS doesn't matter, that doesn't have this clause?

And no, "#CallForPricing" and #NDA'd #MILINTEL / #Aerospace stuff like #VxWorks doesn't count!

#BSI WID-SEC-2025-0192: [NEU] [UNGEPATCHT] [mittel] #Wind #River #VxWorks: Schwachstelle ermöglicht Offenlegung von Informationen

Ein Angreifer kann eine Schwachstelle in Wind River VxWorks ausnutzen, um Informationen offenzulegen.

https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2025-0192

@jamie @icedquinn unlikely...

Last time I checked only #VxWorks was certified by #NASA, #esa & #JAXA for crtitical systems...

@leonerd Spirit and Opportunity ran #VxWorks, and I don't think there's a perl port. I'd not be surprised if the follow-ups also run VxWorks. There's almost certainly perl code running on the control room side of things, of course, just because so many system maintenance tools are written in it.

@landley @DavittoKun *nodds in agreement*

I don't expect anyone maintaining, designing or building #CriticalInfrastructure to ever reach out to me or even use OS/1337, but if those developing i.e. medical IT take a look at this and decide to use a clean and minimalist #Linux, #FreeBSD, #OpenBSD or even #illumos - based distro with #toybox or another compact #Userland instead of some botched "embedded" Version of Windows, then already that's the kind of change I want to see...

I mean it would be cool if they used and contributed to #OS1337 but if I wanted to force them then I should've made some commercial distro akin to #WindRiverLinux or #VxWorks instead, and I don't...