On 12/4/06, йцу ддд <address@hidden> wrote:
In my opinion, be better if we make a some simple Jari environment
first(basically it is scheduler + process manager + elf file loader +
very simple file system (like linux initramfs) + very simple irq
handling + some user process (sh, statically linked with libc.)
execute feature. It may be work without MM in first time(and it may be
good on MMUless embedded systems) and it is someone basis for the more
Jari development.
mm is very significant thing in any system, so other components uses mm functionality.
we can make some stubs, but it can make much garbage in mm. so it should be implemented at first, next sheduler, at next other least significant features.
but it will be better if we determine some server API to make kernel server in userspace of our OS'es. and them correlate different parts of project. low level + middle level + high level
PS: Sorry for my terrible english.
On 12/4/06, Dan Kruchinin <
address@hidden> wrote:
> ---------- Forwarded message ----------
> From: Dan Kruchinin <address@hidden>
> Date: Dec 4, 2006 4:54 PM
> Subject: jari booting proccess
> To: address@hidden.
>
> i think we should to discuss jari booting proccess.
> for current moment we use grub as bootloader.
> but i think, that it'll be better to write our own loader.
> but we should give to user possibility to use bootloader, that he want.
> It can be grub, lilo or some other.
> so, in this case, our bootloader should to intercept management and do some
> things, thats jari really need.
>
> so, gentlemens, your comments =)
>
>