Hi, I'm the developer of venom OS, a small x86 pmode OS hosted on sourceforge http://sourceforge.net/projects/venom-os/
The project is still being worked on but the updates are slow. I've redesigned some of the internals and the updates will appear on sourceforge over the next few months.
Right now I'm looking for interested people for development and support for the following areas.
OS Development -
File system
Memory management
Task management
Security
Shell & utils
User apps
Extra support -
Webpage design
OS and apps testing
The last update was a bug fix snapshot of v0.2.2 which is working and stable but very simple. The idea to reach v0.50 is to have it working in a stable DOS 6.xx like environment. This means a cli, a working filesystem, some simple tools and apps and the basic system services without full security. Eventually v1.0 will include the security and a gui.
I have design ideas for the final project including the cli & gui native language, installation packages, filesystem, tools, apps and libraries.
If there is anyone new to OSDev or someone looking to support a small project in its early stages please contact me thru here or sourceforge.
Thanks,
B.ZaaR
Venom OS developers & support wanted
Venom OS developers & support wanted
"God! Not Unix" - Richard Stallman
Website: venom Dev
OS project: venom OS
Hexadecimal Editor: hexed
Website: venom Dev
OS project: venom OS
Hexadecimal Editor: hexed
Re: Venom OS developers & support wanted
I don't have the time (or interest) to participate in a project, but I can provide some pointers on asking for help.
I'd suggest telling people of the design goals that set your project apart from the rest, think about it, why would anyone join a project that is identical to a thousand other projects? Also, the programming API of the kernel needs to be solid or at least present, that way integrating a new developer doesn't require a hack-job to get a working development environment going.
I'd suggest telling people of the design goals that set your project apart from the rest, think about it, why would anyone join a project that is identical to a thousand other projects? Also, the programming API of the kernel needs to be solid or at least present, that way integrating a new developer doesn't require a hack-job to get a working development environment going.
Website: https://joscor.com
Re: Venom OS developers & support wanted
The design goals of venom is to be a daily use OS with focus on multimedia, gaming, security, stability, ease of use and the ability to highly customise the interface to the users desire. Both CLI and GUI with full OS functionality available in either mode. The system API and device drivers (kernel system) run the PC while the interface is seperate so any configuration can be used on top when the kernel is stable.
The basic system API is present with the option to expand on driver API (part of the design, not just an undefined driver API). Some POSIX compatibility but this is not a unix clone.
This is working towards v3.0 not a start up idea without some fundamental code. The internal structure is very simple atm and hopefully can stay that way even when security features are added later.
The basic system API is present with the option to expand on driver API (part of the design, not just an undefined driver API). Some POSIX compatibility but this is not a unix clone.
This is working towards v3.0 not a start up idea without some fundamental code. The internal structure is very simple atm and hopefully can stay that way even when security features are added later.
"God! Not Unix" - Richard Stallman
Website: venom Dev
OS project: venom OS
Hexadecimal Editor: hexed
Website: venom Dev
OS project: venom OS
Hexadecimal Editor: hexed
-
- Member
- Posts: 199
- Joined: Sat Jun 28, 2008 6:44 pm
Re: Venom OS developers & support wanted
*imagines Lua userspace in one gigantic script file*b.zaar wrote:The design goals of venom is to be a daily use OS with focus on multimedia, gaming, security, stability, ease of use and the ability to highly customise the interface to the users desire. Both CLI and GUI with full OS functionality available in either mode. The system API and device drivers (kernel system) run the PC while the interface is seperate so any configuration can be used on top when the kernel is stable.
The basic system API is present with the option to expand on driver API (part of the design, not just an undefined driver API). Some POSIX compatibility but this is not a unix clone.
This is working towards v3.0 not a start up idea without some fundamental code. The internal structure is very simple atm and hopefully can stay that way even when security features are added later.
Re: Venom OS developers & support wanted
I have another tip for you: stay away from SourceForge unless you're really planning on creating a site. Google Code is so much more convenient for other people wanting to join your project. Not that SourceForge is bad but it's just so slow...
When the chance of succeeding is 99%, there is still a 50% chance of that success happening.
Re: Venom OS developers & support wanted
No replies in a while, eh?
I will help... but I don't have a sourceforge account.
I will help... but I don't have a sourceforge account.
Current work on a OS: SauOS (project homepage: http://code.google.com/p/sauos/)
Re: Venom OS developers & support wanted
hi, I like Venom, very nice look and feel, very retro, I have a stable computer and heaps of commercial webdev and general dev experience, I'm spread a little thin with projects at the moment but I can take on some of the roles if you can recognise it wont be my primary project, I have a googlemail for contact right now if you want to discuss this privately PM me and we'll see what I can do + I'm also working on my own OS
there are only 1 0 types of people in the world, (un)fortunately Base 2 allows for a lot more than just 0 and 1
Re: Venom OS developers & support wanted
Hi, quick update... yes venom is still looking for developers.
At the moment Im designing a filesystem. It uses allocation groups, bitmaps, extents and B+ trees and comes in 16, 32 & 64 bit formats. Eventually it will support compressed folders, extended attributes and journaling but these are not yet in the base specification.
If anyone is interested in helping with this side of things I'll have a new mkimage tool available soon.
Also a new boot loader and 2nd stage boot loader will need to be written. I would like to make the 2nd stage boot loader use multiboot configurations and have the kernel use them so that grub can also be used to load the kernel.
This is the current focus for v0.3.0
At the moment Im designing a filesystem. It uses allocation groups, bitmaps, extents and B+ trees and comes in 16, 32 & 64 bit formats. Eventually it will support compressed folders, extended attributes and journaling but these are not yet in the base specification.
If anyone is interested in helping with this side of things I'll have a new mkimage tool available soon.
Also a new boot loader and 2nd stage boot loader will need to be written. I would like to make the 2nd stage boot loader use multiboot configurations and have the kernel use them so that grub can also be used to load the kernel.
This is the current focus for v0.3.0
"God! Not Unix" - Richard Stallman
Website: venom Dev
OS project: venom OS
Hexadecimal Editor: hexed
Website: venom Dev
OS project: venom OS
Hexadecimal Editor: hexed
Re: Venom OS developers & support wanted
Hi
I just tested. It crashes in Qemu with a reported double fault. It works in Bochs. I couldn't easily crash it.
clange
I just tested. It crashes in Qemu with a reported double fault. It works in Bochs. I couldn't easily crash it.
clange