OSDev.org

I really hate to rewrite this post, as I did so already on the osdever version, but I'll take it on faith that since I can't see my post, can't find my post with search, and all of the other posts look old, that it got reverted out of existence.

Anyway, I'm looking for a team to help take my Viridis operating system and turn it into something useful. Right now it's a basically functional system (paging/mm/multitasking/interrupts/ide read), but I'm looking for some people to join the team and help direct it into something that isn't so basic.

I've already got a few hits on Sourceforge and one new person on the (what is now a) team. We're looking to keep it small, like four or five people, so if you're interested in joing a team with a functional codebase, this is your chance.

Drop me a line: [email protected], [email protected], [email protected] (in order of preference).

That said, I understand that the OS dever's DIY instincts are powerful, and I don't expect an overflow of support, but the power of a group is a great tool to do great things.

I've been thinking about something for a while now.

You see, everybody has different ideas about how to do different things, but there are some kinds of things that are little different in each OS, simply because some things you just need to do, and implementation isn't that important.

Examples: most everybody's drivers should be happy if they are allowed to process interrupts, talk to their device, and arrange DMA transfers to memory. How they're supposed to communicate with rest of the system (or even do the above) differs, but the way they talk with their device need not be so different most of the time. We have this EDI initiative already for this.

I think we could find other things that everybody (or almost everybody) is going the do the same way, and try to share of more of that. Ultimately, it'd be nice if we could get together something like a repository of code that everybody can take basic implementations from, and plug them into their OS.

Solar is doing the PDCLib, so there's another one. What other things could we share?

1) hardware independant things in Process management, IPC mechanisms for those, scheduling. [maybe they will be in sets]

2) also some very common n basic (?), HAL device drivers.

3) network stack implementations.....er.....in tweakable conditions.

I'd been thinking of something similar to this, but slightly more restricitive. You'd define a standard layout of a kernel (i.e. the MM has defined functions that it has to provide, as does IPC etc.) Then implement a benchmarking system into the kernel. Then anyone could implement different ideas for parts of the system without needing a full OS implementation and test how good they are.

Not that well explained... but nvm

Pete