5 ms·
Show HN: The Unite real time operating system
- AndrewKemendo 1y agoCongrats on shipping Jaques! Great to see you resurrect this project and publish it.
- jacquesm 1y agoThank you. One download so far :) Mega success! It's interesting how you can release an OS + source code and hardly anybody will bat an eye. But nonsense attached to an LLM will draw a crowd ;) Anyway, I'm happy that I got it to work and I hope at least someone will find it useful.
- AndrewKemendo 1y agoJust gotta ride the wave as you know. Sorry I misspelled your name originally!
- jacquesm 1y agoNP, that's been happening to me pretty much since I was born.
- balder1991 1y agoMaybe he should have named the OS the “LLM OS”, and then only later people will realize LLM stands for something else entirely.
- jacquesm 1y agoThat's slightly evil, but funny too!
- bcjordan 1y agoReally interesting. Feels like a fun platform to tinker with like "circuit bending" to make surprising behaviors happen across the entire OS I wonder what the ideal demo of this that makes its approach visually legible would be
- jacquesm 1y agoThat's a good question and one that I've been wondering about myself. For me it is the very clean abstraction layers. There is zero side-to-side communication it is all broader foundations to narrower verticals plugged in to those. For instance, the networking stack has a process for every layer. That keeps that whole thing manageable and it means that problems can never escape the scope of the process they are in, unlike a 'large' kernel where a botched device driver can bring down the whole system. You can pretty much tear this down to the task scheduler and the loader and rebuild it up without taking the system down. And I had a good idea on how you could replace the scheduler with another one while the system is running. I'm really curious what - if anything - people will do with it, I think that the fact that an OS like this one powered the BlackBerry (which people loved) should work in its favor, other places where you find this kind of OS is in industrial control and in vehicles. Usually there is some kind of hardware component involved but that's entirely optional, you could use it as a general purpose OS as well.
- landsman 1y agoI would consider putting it on GitHub. Torrent is not the best way to share code today.
- jacquesm 1y agoIt's a running OS snapshot as a drive image, not a source tree, the sources are on the drive image. As for GitHub itself: I am not going to further Microsoft's grip on the world of software development.
- ofrzeta 1y agoWell, then go to codeberg.org
- ThinkBeat 1y agoThank you. For taking a stand against Microsofts "social network", "ai training data", greed and proprietary tooling. I think sharing the source code as you do now is a perfect choice is it is what you are most comfortable with.
- jacquesm 1y agoI may end up working some more on it and releasing updated versions of the torrent. But I'm not going to be a 'maintainer', if I want unpaid work I'll volunteer at the local animal shelter instead.
- alain94040 1y agoInteresting. Is there a picture that explains how the layers talk to each other? Is there a VM system? How does message passing work, what kinds of protections are between tasks? I have had many ideas for such kernels over the years, but not the patience yet to implement any of them. I wonder if Claude could help me with generating a kernel in less than a day.
- kroaton 1y agoPull the source and ask Claude to explain it to you...
- jacquesm 1y agoI should definitely make that picture. Yes, it as VM. Message passing all runs through the kernel. Task isolation is strictly memory based, whether a task acts on or responds to a message is something the tasks will have to negotiate between themselves. You could whitelist, use a token scheme or any other method for authentication that you wish to put in place, but out of the box there is none, if you know a tasks ID you can send it a message. Obviously there are ownership of resource constraints and the kernel will always ensure that the receiving task knows who the sending task is to ensure that parties are not stealing each others descriptors and such.
- Animats 1y agoAw. I've always liked QNX. But a modern implementation, not a revival of a 30 year old abandoned project, would be more useful. We really need something for small IoT boxes that has less attack surface than Linux. The problem people run into trying to build something like QNX is that, while the kernel is tiny, it won't even do Hello World until you have the necessary user-space drivers running. Initial debugging is hard.
- bregma 1y agoIf you're looking for something like QNX you could use... QNX. It's still around and free for hobbyists [0]. You can use it knowing you're using the same OS as your car, or train, or medical device, or spacecraft. [0] https://www.qnx.com/products/everywhere/ https://www.qnx.com/products/everywhere/
- Chris2048 1y agoYou still have to register with them, I'm not sure that is common among NC licenses. I assume this also means its not really open-source (or compatible with open collaboration) if they are gatekeeping (via licences) the free dev licence. Also consider this - If you got a licence would this "taint" you if you ever wanted to work on a project like OPs? As in, the registration is proof you could access the proprietary QNX code, forming the basis of a lawsuit.
- jacquesm 1y agoQuantum has muddied the waters considerably here by at some point releasing the code under a fully open license. They tried hard to reverse that decision but I'm sure there are still copies of that version floating around.
- cxr 1y agoIn contrast to Minix 3.0+, no version of QNX has ever been fully open. At its most permissive, it was made available (behind a form submission) under a look-but-don't-touch All Rights Reserved sourceware license.
- Rochus 1y agoThat's interesting. Did you have access to the QNX sources at the time and were able to study the QNX kernel and why it had a much better performance than Minix? Given your reference to DJGPP, am I right to assume that you have written your OS in C? (I wasn't able to download the source code and would appreciate to be able to download a compressed file from a "normal" web server). Since you made comparisons with the Minix version of that time, what conclusions did you draw from this, and what especially made your kernel "lightyears ahead" of Minix?
- jacquesm 1y agoNo, but I had used it extensively and written a fairly large amount of code for it so it was mostly re-implementing how I thought things must work under the hood. The hardest part was to bridge some of the posix like functionality to this rather strange set of primitives, especially 'fork' and the '/dev/' parts required some pretty hacky solutions. But they work and they ended up being quite reliable. As for it being lightyears ahead of Minix: Minix was built from the ground up as a platform to demonstrate how Unix works without being Unix. QnX and by extension my version on that theme was built from day one to be low latency and to have the smallest possible kernel footprint that you could have. The lack of a root file system and the Plan-9 like network transparency are all as a result of that and allow extremely fine grained control over what goes into the final package. It is far more suitable for low level control while at the same time having high level tooling than Minix. What I loved about Minix is the way the source code is organized and how - and this is obviously no accident - it reads as a textbook, I learned a lot from looking at the code and ended up adopting the file system as a stand-alone piece of code (which allowed me to pass files in and out of the OS early on by writing them under one OS and then rebooting so I had access on the other side).
- Rochus 1y agoAmazing, thanks. Is it possible to just have a look at the source code somewhere, e.g. codeberg or gitlab? I'm especially interested in the microkernel IPC.
- 1y ago
- whitehexagon 1y ago>dive under the table every three minutes to hit the reset button Hah, I feel that pain. Currently hacking some bare-metal Zig on PinePhone, and on top of the USB reconnect power cycle, I am transferring an SD card back n forth. I wonder if I'll be making a similar post in 30 years time. Anyway, well done, and I look forward to browsing the code for some inspiration. Thanks for making it PD.
- jacquesm 1y agoOh good luck, I really feel your pain :) Consider using an emulator until you're really ready to go to hardware that might save you a lot of time and headache, it also makes observability a lot better. Nothing beats having access to memory from a debugger.
- whitehexagon 1y agoThank-you for the advice. So far it has been mostly SoC stuff, and I recently got side-tracked learning some armv8 assembly, which reminds me somewhat of my 68000 days and has been good fun. I did try QEMU for the first time last week, but started thinking I'd need some way to mock out all the hardware, and I only got as far as UART. But now that you mention it I'll take another look. There is a lot of multi-core mbox? IRQ stuff I'm about to tackle next, and I dont see why I cant develop all of that independent of the hardware. I seem to be learning the hard way. I spent the first 12 months debugging via the only thing I could get working, an onboard RGB LED.
- jacquesm 1y agoMulti-core is a level of complexity that I have no experience with, there were some i386 / i486 multi-cpu boards but I don't remember every having one of those. We did have a very early dual CPU pentium, but by that time the OS was already mothballed and we had standardized on Linux.
- jacquesm 1y agoIf you want to run this under windows then VirtualBox seems to work better than QEMU.