altosdev-kernel

[Altosdev-kernel] Getting started..

[Kernel P. <rzh...@he...>]

Hi, everyone!

So far we have heard me, Raz0rSharp and dozzer here. Could the others,
please, post here their ideas about their skills and what part of the
OS they want to develop?

As I have written, I have a (almost) working loader (with shared
libraries support) and memory-allocation routines for the kernel (with
a simple write-only console). As soon as I get it done, we can start
implementing some basic process management (for loading the drivers,
as it's going to be a microkernel, so drivers are all separate
user-mode processes), inter-process communication routines and drivers
themselves. ..Kind of plans for the nearest future..

-- 
Regards,
 Kernel Panic                          mailto:rzh...@he...

P.S. I hope to get the loader working by the end of the week. If I
fail, I'll ask someone for assistance.

Re: [Altosdev-kernel] Getting started..

[Alexey M. <tkt...@cs...>]

> Hi, everyone!
Hi,

> As I have written, I have a (almost) working loader (with shared
> libraries support) and memory-allocation routines for the kernel (with
Why do you need your own loader? Why don't you get ready one; GRUB? It 
performs all what your loader should do.

> a simple write-only console). As soon as I get it done, we can start
> implementing some basic process management (for loading the drivers,
> as it's going to be a microkernel, so drivers are all separate
> user-mode processes), inter-process communication routines and drivers
> themselves. ..Kind of plans for the nearest future..
OK. I agree. We need some kind of skeleton to begin work on different 
parts of kernel and drivers. I understand, that loader in progress, but 
can you post kernel (or your skeleton) here?

-- 
See you later,
 d.

+358 040 817 8540

Re: [Altosdev-kernel] Getting started..

[Benjamin J. <bsj...@mi...>]

I'm done with my coursework for the next 7 months so I'm ready to start
coding...

Raz0rsharp

Alexey Malev wrote:

> > Hi, everyone!
> Hi,
>
> > As I have written, I have a (almost) working loader (with shared
> > libraries support) and memory-allocation routines for the kernel (with
> Why do you need your own loader? Why don't you get ready one; GRUB? It
> performs all what your loader should do.
>
> > a simple write-only console). As soon as I get it done, we can start
> > implementing some basic process management (for loading the drivers,
> > as it's going to be a microkernel, so drivers are all separate
> > user-mode processes), inter-process communication routines and drivers
> > themselves. ..Kind of plans for the nearest future..
> OK. I agree. We need some kind of skeleton to begin work on different
> parts of kernel and drivers. I understand, that loader in progress, but
> can you post kernel (or your skeleton) here?
>
> --
> See you later,
>  d.
>
> +358 040 817 8540
>
> _______________________________________________
> altOSdev-kernel mailing list
> alt...@li...
> https://lists.sourceforge.net/lists/listinfo/altosdev-kernel

Re[2]: [Altosdev-kernel] Getting started..

[Kernel P. <rzh...@he...>]

Hello, Alexey.

On Friday, March 15, 2002 at 6:20:05 PM you wrote:

AM> Why do you need your own loader? Why don't you get ready one; GRUB? It
AM> performs all what your loader should do.
'Cause I don't know if GRUB supports shared libraries. If it does,
then an extra loader is useless, of course =) . Well, at least I'll be
able to reuse the code for an ELF loader.. (Actually, I didn't know of
GRUB when I started writing it.)

AM> OK. I agree. We need some kind of skeleton to begin work on different
AM> parts of kernel and drivers. I understand, that loader in progress, but 
AM> can you post kernel (or your skeleton) here?
Ok, I'm sending it in attachement (it's kind of large file). Hope
it'll be able to go through the sourceforge. Most of the include files
there are taken from FreeBSD 4.2.. Also one sourcefile.. There are
some stupid comments everywhere, just ignore them. If you have any
questions, feel free to ask..

-- 
Regards,
 Kernel Panic                          mailto:rzh...@he...