71–80 of 196 posts
I hope they don't try to compete with Linux. just do their own thing and see where it goes. usually the competitive edge kills projects like these.
happy to see new kernels popping up!
>Under the hood, Minoca contains a powerful driver model between device drivers and the kernel. The idea is that drivers can be written in a forward compatible manner, so kernel level components can be upgraded without requiring a recompilation of all device drivers. This sounds really smart and it looks great overall <3
Oh please. You have to start somewhere and this is where they're starting. By comparison, Linus' first announcement was: Hello everybody out there using minix - I'm doing a (free) operating system (just a hobby, won't be big and professional like gnu) for 386(486) AT clones. This has been brewing since april, and is starting to get ready. I'd like any feedback on things people like/dislike in minix, as my OS resemble…
Actually there's plenty of docs to read: http://www.minocacorp.com/doc/1375/api/KERNEL_API/ I haven't found something like an architecture overview of the kernel itself, but the docs story isn't bad for a 2-ppl team. Kudos.
can it run on raspberry pi?
The code gives me flashbacks to working with the Windows API. Cool project though and it's nice that they already have a handful of drivers. EDIT: To clarify, I'm not saying it's bad at all, they're just using a very verbose naming convention that I don't particularly like working with.
It looks like they have basically adopted the coding conventions of windows API code, down to the / ++ -- / comments, style of declaring functions, uppercase types etc. Not that it's is a bad thing, just something I noticed. Also things like KeCrashSystemEx look very much like KeBugCheckEx in Windows. There certainly is a lot of inspiration. Edit: I see from Linkedin the OP is actually an ex-MSFTer who worked on Wind…
Earlier quoted context omitted.
Amazing the submissive tone, and lack of confidence in that message. Compared to the holier than thou attitude Linus presents himself in these days. I would have never guessed he wrote that.
I don't think it's lack of confidence. It's just a realistic acknowledgement that it's a small start and in fact was unlikely to be useful. But he wanted feedback on how to make it useful. I think Linus is just a practical person who is good at assessing reality. He doesn't get caught up in grand visions without action. I don't think he is holier than thou now either. He's just busy and forcefully trying to get contr…
The same Linus that fundementally did not believe in source code management for what 20? Years because it made developers "soft"!?
Earlier quoted context omitted.
I felt this way as well (since the mid nineties) until a couple of weeks ago when I read _Social Architecture_ by Pieter Hintjens. It has a strong idealogical flavour. He stresses that you should focus on building a community, with the code and platform as happy side-effects of that community. For that reason, you want GPL because it forces everything back into the community. He gives examples of a friend of his who…
> He stresses that you should focus on building a community, with the code and platform as happy side-effects of that community. Exactly, so license shouldn't matter that much. I'd probably be a lot more interested in it were it BSD licensed, as it is now I have no real desire to play with this new OS.
Minoca OS has been around for a while, but the news is that they're GPLv3. I think that's a great thing! The MIT license is good for software that wants to permeate through everything, but for building a community, the GPL is a good idea.
It seems that for any operating system to be successful, it has to carry around POSIX compatibility like an extremely expensive entry pass. I wonder when we will leave that behind? Or if we ever will? I'm glad POSIX is just a layer in Minoca, and not the base of the system, because these days it really should just be treated like a big wad of glue.
PS: I love the object manager. I don't see any particularly ground-breaking networking stack, though. A plan9-inspired networked file system approach would have been amazing, but it seems this project is content with today's more typical approach. Perhaps it is just trying to be less opinionated about network structure than plan9 was?
PPS: I'm terrible at organizing a comment. Maybe I need a blog.