DOORS\\AQUA KERNELХ7

Hello, All Why did it bring me back to memories :eek: so I decided to jot down a couple of lines here. This is by no means the final version! These are just the first drafts of the kernel systems. If anyone has any questions, suggestions, additions, I’m always happy listen. :rolleyes: Comrades at the "AM/KG" level, please do not strain your remaining mental convolutions :mad: File: DOORS2006.rar http://zx.pk.ru/attachment.php?attachmentid=2522

Hello, breeze evil thing. By the way, I also have some ideas about sedimentation, but a little different steppe Call me and we’ll discuss it ^_~

Hello, breeze Gee, breeze, roll up man pages for them :)

Hello, breeze bre> comrades at the "AM/KG" level, please do not strain your balance bre> mental convolutions Ampere per kilogram? If only you, comrades, could at least publish your creation in a form that can be read by those same others. It doesn't even matter in kilograms or amperes.

Hello icebear ice> Hey, breeze, roll up the man pages for them :) definitely! :rolleyes: 2ALL: apparently there’s nothing special to write :sleep: since there’s such a sea of answers, advice, wishes etc etc :confused: although on the other hand, whoever wanted to wrote in a personal message... :rolleyes:

Hello, breeze In the generally accepted sense, a process and a subroutine are different things.

Hello, captain cobalt IMHO there are a lot of details in the text, and the system architecture is not visible behind them... about what the core is, through what (unified) interfaces it communicates with drivers and processes, all that remains is guess. using specific set/get functions to work with each driver... hmmm... you can simply replace the drivers with function libraries, anyway the slightest changes in parameters (for example, you will need another parameter add), and you will have to rewrite and rebuild everything. something like ioctls IMHO it would be more suitable.

Hello, captain cobalt cap> In the generally accepted sense, a process (process) and a subroutine (subroutine) - cap> these are different things. if you criticize, suggest! if you make an offer, take action! :mad:

Hello, breeze I propose to use the terms in their generally accepted meaning. Or give them definitions. Otherwise, the texts turn into a meaningless set of words.

Hello, captain cobalt I didn't quite understand something %SUBJ% There is a description of... what? Cores? Or kernel calling functions? Are there any translator libraries for the presented call commands (high-level)? If these are low-level instructions, how are parameters (registers, memory, indexes)? Why are the console and kernel "integrated"? Are these different things? How does memory management work at the application (thread) and system levels? Memory representation? Why is there a page organization? How many threads are there in system? Is the system multitasking? Is there any ready-made code (at least partially)? Requests: the subject lacks structure, more consistent presentation What is clearly missing: all resources are represented from the point of view of the system, which manages them and from the point of view of the flow that requests these resources from systems, everything is mixed up here, we need to separate it somehow.

Hello,GriV Gri> I didn’t quite understand something %SUBJ% ask :eek: we answer! :mad: Gri> There is a description of... what? Cores? Or kernel call functions? the minimum set of kernel functions that are planned to be used... Gri> There are libraries that translate the presented call commands Gri> (high-level)? is this a question or a statement? :o Gri> If these are low-level commands, how are parameters (registers, Gri> memory, indexes)? this will happen a little later, when it will already be implemented directly in code! Gri> Why are the console and kernel “integrated”? Are these different things? Whooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo this is the wrong console :D this is a console for output and input primary teams!!!!! Look how it was done in FreeBSD when at startup you can Press spacebar and you'll fall out into the console! where you can upload/download kernal, LIBs, indicate where BOOT is from, mount something and several others minimal commands! and what you mean is called SHELL!!!! where already The user interface works! Gri> How is memory managed at the application (thread) and system levels? that you are some kind of evil :( explain the question...Gri> Memory representation? Why is there a page organization? But because I wanted it so bad :eek: why crush it into small particles? clustering of 16 is quite sufficient... in general it is selected with minimal cost per occupancy bitmap. Gri> How many threads are there in the system? hmm... I think not much. There are no streams in the form you think here! Explain why you need this :) I think it will be possible to reconsider my opinion... :cool: Gri> Is the system multitasking? hmm... I would say that it rather has the ability to launch simultaneously a certain number of processes. if processes are considered as tasks, then apparently yes :rolleyes: Gri> Is there already ready-made code (at least partially)? yes. Gri> Requests: the subject is not structured enough, more consistent Gri> expound well, I would call it just a draft, an outline for implementing the code... and not as an unfinished document :eek: Gri> What is clearly missing: all resources are represented from a point of view Gri> system that manages them and from the point of view of the flow that these Gri> asks the system for resources, but here everything is mixed up, something needs to be done Gri> divide.hmm... I already wrote, I’ll ask again: more about the flows... :rolleyes: