Chronos

[Lionel]

Chronos (Version 0.0.0.1-d)
Chronos is a i586 hybrid kernel written in C, with inspiration from XNU/Mach, and by extension, BSD and Unix. The project Audentia was Chronos' predecessor, and inherits structure from it, nothing more. It will be designed to rely on kernel extensions (NOT drivers, drivers entirely separate!), and use message passing. It will have daemons, along with shared libraries. Currently, the project is being developed in my spare time, which isn't much with school. Currently, the kernel has no resemblance to it's inspirations, and is being formed and optimized(Just using better formulas). Currently, IRQ support is being implemented.

Downloads
The code is hosted on GitHub, and should be updated about every day.

Screenshots

[brain]

I would take a look but your github is 404 where do I get it?

[VolTeK]

I would take a look but your github is 404 where do I get it?

Go find a tutorial. That is basically 'Still' all the OP has ready.

To find these tutorials please search the wiki.

[Lionel]

Github? This isn't hosted on it.

[JackScott]

By poking around you can solve the 404: https://github.com/Lionel07/Chronos

However the repository doesn't have any content in it yet.

[VolTeK]

Then again. Why defend him. He is running two projects when one isn't complete to begin with, it wont matter in a month or two.

I'm only being an @$$, because this is the equivilant of posting a,

"Yes i finally got code i learned from a tutorial to work, now here's what i might do.

I believe in posting anything when a 'close-to' version 1 is done. Or at least, that's what i am doing. Why show a skeleton, every ones skeleton comes out looking similar.


When he realizes that running two at one time, that basically will do the same thing. One will die off.
..or they both will


I realize ^ sounds very mean, and i apologize. I may just remove this post out of kindness.

[SDS]

Then again. Why defend him. He is running two projects when one isn't complete to begin with, it wont matter in a month or two.

I would hope you would notice (emphasis mine)

Chronos is a Objective Kernel written in C++, which was previously known as Audentia.

before taking aim at someone else's apparent inconsistency.

OTOH, there is clearly more than a little bit to do. For goals to be "irq, pit" doesn't say much about the notion of "inspired by XNU/Mac OSX", or the tagline of "The different operating system". I can't see any design concepts at all...

[VolTeK]

I would hope you would notice (emphasis mine)
Lionel wrote:
Chronos is a Objective Kernel written in C++, which was previously known as Audentia.

before taking aim at someone else's apparent inconsistency.

Something a little more, to the point.

I am Renaming my current Operating system to a new project with a new list of features i am currently working on or have planned.

I can rename my brother, to a new name like tom. However the government wants to know this as well, not 10 years down the line.

[Lionel]

I updated the poorly written first post, sorry.
For the people who were looking at my sig, not to be rude, but it says Audentia, not Chronos.
And just to reiterate, this isn't Audentia, it's Chronos, completely different Kernels, though Chronos did take the printf code, and that's why I posted this in a new topic.

Cheers~
Lionel

[brain]

Do you plan to update your Sig with a link to chronos for those of us too lazy to dig around?

[Lionel]

Already done.

[brain]

Cool, any ETA until theres something we can play with, e.g. a shell or such?

[Lionel]

After I implement IRQ's, I'll enable timing, then keyboard support, then start on a basic shell.

[eino]

Just a thought: shouldn't you build a dynamic memory allocation before rushing into doing a shell of any kind? Would propably make your life easier when moving to the shell.

[amd64pager]

Are you planning to write your kernel in such a way that it is compatible with new and old hardware?My microkernel(just wrote the physmem manager now)is supposed to be fully 64-bit ,no compatibility for 32-bit,ACPI,SMP and APIC support to be in the first version.And oh yes,how did you implement the functions that print info to the screen?Are there handlers which hook onto the interrupt handler or does the interrupt handler do it?
In my kernel,the interrupt handler registers a delayed procedure call(DPC).And after some time(maybe 2 HPET ticks) the DPC executor executes the function call.