[jacquesm]

Congratulations. I did the same thing in the early 90's and I still think it is the project that I learned by far the most from. I never released it because I think its time has passed but it was a fun exercise. Debugging the early stages of such development is super hard, especially if you are doing it on bare metal instead of on a VM.

Do you have a plan behind this or was it just to scratch an itch?

[halfer53]

Thanks. The OS is roughly 90% compliant with POSIX.1, but there's still a lot of work to make it fully compliant. That would probably be my next goal. This is a hobby project, I will probably spend 1-4 horus every other week to work on this. I am working on optimising memory usage of the file system which is almost completed in a separate branch.

[jacquesm]

Neat. POSIX compliance is a tough nut to crack for some of the features that look pretty innocent on the outside, they can dictate huge amounts of under-the-hood architectural and conceptual elements. My project revolved around a 32 bit capable clone of QnX, which at the time had only been released in a 16 bit version. The company that I did regular consulting for had a bunch of requirements that the stock QnX could not fulfill so in a fit of madness I decided to roll my own. By the time it was finished QnX had finally released their own 32 bit OS.

Keep at it, I'm really curious how what you are making will end up.

[bregma]

That's funny because QNX now only supports 64-bit systems and hasn't done 16-bit systems for decades. You must be (relatively) ancient. Disclaimer: I currently work for the company that owns the QNX IP and would also qualify as (relatively) ancient.

[jacquesm]

Yes, I'm ancient :) 56 on this end. This work was done in the early 90's.

[jordiburgos]

Why do you want to be compliant with POSIX?

Would it affect to the speed of execution or development not to be compliant?