Minoca OS goes open source
Minoca OS is a general purpose operating system written completely from the ground up. It’s intended for devices looking to conserve power, memory, and storage. It aims to be lean, maintainable, modular, and compatible with existing software."
Posted Nov 1, 2016 19:11 UTC (Tue)
by spender (guest, #23067)
[Link] (1 responses)
"Proprietary and non-GPL source licenses are available, keeping options open for your customers and end users."
Contributors need to sign CLAs that permit upstream to relicense contributions under proprietary licenses.
-Brad
Posted Nov 1, 2016 19:35 UTC (Tue)
by SEJeff (guest, #51588)
[Link]
Posted Nov 1, 2016 19:18 UTC (Tue)
by Cyberax (✭ supporter ✭, #52523)
[Link] (18 responses)
Their kernel uses all the same design patterns as WinNT from what I can see from the source code. They also have layered driver structure with generalized IRP packets traversing the chain. They have even copied the idea of IRQLs ( https://www.minocacorp.com/doc/1375/api/KERNEL_API/elemen... ). LOL.
I personally don't see the reason for it to exist - it's not like there are no minimalist kernels out there. And it's also pure C, so it's guaranteed to be full of buffer overflows and other classic C-based vulnerabilities.
Posted Nov 1, 2016 19:28 UTC (Tue)
by spender (guest, #23067)
[Link] (1 responses)
KPROCESS
memory descriptor lists, *AllocatePool with a tag argument, etc
-Brad
Posted Nov 1, 2016 19:29 UTC (Tue)
by spender (guest, #23067)
[Link]
-Brad
Posted Nov 1, 2016 19:29 UTC (Tue)
by atai (subscriber, #10977)
[Link] (3 responses)
Posted Nov 1, 2016 19:53 UTC (Tue)
by fratti (guest, #105722)
[Link] (1 responses)
Posted Nov 2, 2016 6:25 UTC (Wed)
by felixfix (subscriber, #242)
[Link]
Posted Nov 3, 2016 11:05 UTC (Thu)
by smurf (subscriber, #17840)
[Link]
Posted Nov 2, 2016 4:21 UTC (Wed)
by pabs (subscriber, #43278)
[Link]
https://news.ycombinator.com/item?id=12841691
Posted Nov 2, 2016 5:27 UTC (Wed)
by eru (subscriber, #2753)
[Link] (10 responses)
What language would you write an OS kernel in, if starting from scratch now? It seems to me the choices are C or something equally low-level, and therefore sharing the same safety problems.
Posted Nov 2, 2016 8:02 UTC (Wed)
by tlamp (subscriber, #108540)
[Link] (3 responses)
There is redox-os which is a micro kernel approach written mostly in rust.
Posted Nov 2, 2016 8:16 UTC (Wed)
by t-v (subscriber, #112111)
[Link]
Posted Nov 5, 2016 6:33 UTC (Sat)
by brouhaha (subscriber, #1698)
[Link]
I worked with an OS written in Ada back in the 1980s, and it had very few places that needed escapes to unsafe constructs.
It's possible that Rust may be a better choice than either of those, though I haven't actually studied Rust so I'm not certain.
Posted Nov 7, 2016 7:09 UTC (Mon)
by mjthayer (guest, #39183)
[Link]
I would expect 16% of a micro-kernel to be a reasonably small code base. It is probably still a lot of code, but perhaps at least somewhat easier to secure.
Posted Nov 2, 2016 8:52 UTC (Wed)
by Cyberax (✭ supporter ✭, #52523)
[Link] (5 responses)
That would have been at least interesting. But another C-based non-realtime OS with a classic monolithic kernel? Meh.
Posted Nov 2, 2016 9:57 UTC (Wed)
by eru (subscriber, #2753)
[Link] (2 responses)
New? That appears to be a reinvention of the idea of running a simple single-tasking OS on top of a hypervisor. Pioneered in IBM CP/CMS from the sixties...
Posted Nov 2, 2016 15:25 UTC (Wed)
by miquels (guest, #59247)
[Link]
Posted Nov 2, 2016 18:22 UTC (Wed)
by Cyberax (✭ supporter ✭, #52523)
[Link]
However, it's the first modern OS built on that idea with attention to performance inside containers.
Posted Nov 2, 2016 13:45 UTC (Wed)
by aggelos (subscriber, #41752)
[Link] (1 responses)
Ah, do you happen to have any links? I was wondering why I haven't come across any such projects yet.
Posted Nov 2, 2016 18:33 UTC (Wed)
by Cyberax (✭ supporter ✭, #52523)
[Link]
Posted Nov 2, 2016 11:20 UTC (Wed)
by ballombe (subscriber, #9523)
[Link]
Posted Nov 2, 2016 15:44 UTC (Wed)
by karim (subscriber, #114)
[Link] (1 responses)
Posted Nov 9, 2016 8:33 UTC (Wed)
by jospoortvliet (guest, #33164)
[Link]
Posted Nov 2, 2016 16:43 UTC (Wed)
by mfuzzey (subscriber, #57966)
[Link] (2 responses)
It seems to have similar resource requirements to Linux whilst having support for far fewer devices (https://www.minocacorp.com/documentation/developers/knowl...) and filesystems (FAT only for the moment, EXT2 coming next)
"Minoca OS runs on x86, ARMv6, or ARMv7 systems that contain virtual memory support and at least a few megabytes of RAM. The OS is highly scalable, so it can also run on larger machines with multiple cores and many gigabytes of RAM."
There's certainly a place for a much smaller OS for places Linux will never fit (and already plenty of contenders for that space) but it doesn't seem built for that.
Licensing wise it's GPL3 so unlikely to appeal to those that don't want to or can't use the GPL.
Posted Nov 3, 2016 0:20 UTC (Thu)
by atai (subscriber, #10977)
[Link] (1 responses)
Posted Nov 3, 2016 11:14 UTC (Thu)
by smurf (subscriber, #17840)
[Link]
No IPv6 support (yet) also means at best marginal utility for IoT, despite their (unspecific) claims about power saving.
Minoca OS goes open source
Minoca OS goes open source
Minoca OS goes open source
Minoca OS goes open source
KeGetCurrentThread()
IMAGE_SECTION
MmHandleFault()
TRAP_FRAME
Minoca OS goes open source
Minoca OS goes open source
Minoca OS goes open source
Minoca OS goes open source
Minoca OS goes open source
Minoca OS goes open source
https://news.ycombinator.com/item?id=12838904
And it's also pure C, so it's guaranteed to be full of buffer overflows and other classic C-based vulnerabilities.
Minoca OS goes open source
Minoca OS goes open source
But on OS level safe rust is not enough, at the moment at least, so they have to use rusts 'unsafe' keyword on a few places, planning to reduce the usage to an absolute minimum.
IIRC, ~ 16% of the kernel code is (possible) 'unsafe' and thus may have the same problems as C regarding memory, the rest should be safe by design (regarding memory, other bugs may naturally happen).
You could combine two recent LWN news items and use corrode (LWN bit) to translate Minoca OS to Rust.
Minoca OS goes open source
Minoca OS goes open source
Minoca OS goes open source
> But on OS level safe rust is not enough, at the moment at least, so they have to use rusts 'unsafe' keyword on a few places, planning to reduce the usage to an absolute minimum.
> IIRC, ~ 16% of the kernel code is (possible) 'unsafe' and thus may have the same problems as C regarding memory, the rest should be safe by design (regarding memory, other bugs may naturally happen).
Minoca OS goes open source
There are other very interesting new approaches to OS development, like http://osv.io/
Minoca OS goes open source
Minoca OS goes open source
Minoca OS goes open source
Minoca OS goes open source
And there are several projects that develop ways to prove safety of unsafe{} blocks in Rust.
Minoca OS goes open source
Minoca OS goes open source
Linux can boot to a shell in 4MB of RAM while using a ramdisk.
Minoca OS goes open source
Minoca OS goes open source
Minoca OS goes open source
Minoca OS goes open source
Minoca OS goes open source
