Kernel Development Letter 2000-001
a.k.a. KDL/001/2000
RE: "Kernel Development and Specifications" Version 0.1
Freedows OS Project
January 27th. 2000
by Fabin L. Arce Jofr (fabian@arco-net.com.ar), General Consultant, Freedows OS Project.
Table of contents
-----------------
1. Introduction
2. Objectives
3. Work that is already done
1. Introduction
The Freedows OS Project is in a major process for reorganization of itself and its members.
The kernel development is one of its objectives; the Cache Kernel model that Freedows is going to take for its core system actually is going to become an open design, and the project
has to modify the specifications to make it more accurate to the project's needs.
This KDL calls members of the Freedows OS Project to rewrite these specifications, one
of the more near objectives of the Freedows OS Project, to make it easy to follow some guidelines when it's time to finally develop the core OS.
2. Objectives
The main objective of the current stage of the Freedows OS Project is make a working core kernel. That process needs to be done with specifications -- these could be done in a way that developers can understand them and develop
accordingly. The Freedows OS Project Specifications will be a point of start for the development, and like I said, will act as guidelines for that.
Freedows has a main development scope: the development of a core kernel system based in the Cache Kernel model, being able to emulate other OSes through Application Kernels. That objective is going to be divided into stages, where the development of specifications is the first, as following:
Development Map
---------------
1. Specifications and Guidelines
2. Core kernel development
3. Alpha Testing of the core kernel
4. Application kernel development
5. Beta testing of the application kernels
6. Working model of an operating system ready
7. Beta testing of the working model
8. Operating System Public Release
These stages should be followed carefully and made through the specifications created in Stage 1.
3. Work that has been done
There has been work done that belongs to Stage 1 of the development map. Though the Freedows OS Project has begun that stage, it still needs a more focused work guide. In early 1998, some work related to current stages 1 and 2 has been done though; that work that is publicly available can be adapted to our new development target.
Copyright (C) 2000 Freedows OS Project. All rights reserved.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Perhaps I'm being a bit anal retentive already, but could we come up with a set of documents to at least take a look at? Somebody has done some work. Let's have a basis for discussion other than some banter on newsgroups, listservers, and IRC.
Reece, you'll see I have technical writing in my background. Not that I like to write -- I hate it with a passion -- but I end up doing it at every gig I get because none of the captives did any documentation on the project before I started working on it. <sigh> Such is the nature of things, I guess. That's what they pay the Big Money for.
If we need someone to organize and write up docs for the work that has already been done I volunteer. I'd rather do this work than sit and
whine about not having anything to do. Eh?
---
The Old Fart
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
One area that could really use some work from someone with technical writing background <hint hint> ;-) would be breaking up the Stanford Cache Kernel Document, and making it easier to understand. I think I'm one of the
few people that actually understands it, and it's not really helping the development process much to have it like that.
I'm also working on a new general system spec (which I'll have ready "soon"), which requires a lot of discussion.
There are also some old specifications from prior development, which we could discuss as well, however I'm not certain we should run ahead and adopt those as our current design; I've looked at some of them, and they seem to
be sort of, non Cache-Kernelish.
Reece
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Gotcha. I got the doc from http://www-dsg.stanford.edu/papers/cachekernel and expect to start working on it this week. Does anybody have any requests for specific clarifications, expansion, or other editorial content? Let me know.
---
The Old Fart
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Kernel Development Letter 2000-001
a.k.a. KDL/001/2000
RE: "Kernel Development and Specifications" Version 0.1
Freedows OS Project
January 27th. 2000
by Fabin L. Arce Jofr (fabian@arco-net.com.ar), General Consultant, Freedows OS Project.
Table of contents
-----------------
1. Introduction
2. Objectives
3. Work that is already done
1. Introduction
The Freedows OS Project is in a major process for reorganization of itself and its members.
The kernel development is one of its objectives; the Cache Kernel model that Freedows is going to take for its core system actually is going to become an open design, and the project
has to modify the specifications to make it more accurate to the project's needs.
This KDL calls members of the Freedows OS Project to rewrite these specifications, one
of the more near objectives of the Freedows OS Project, to make it easy to follow some guidelines when it's time to finally develop the core OS.
2. Objectives
The main objective of the current stage of the Freedows OS Project is make a working core kernel. That process needs to be done with specifications -- these could be done in a way that developers can understand them and develop
accordingly. The Freedows OS Project Specifications will be a point of start for the development, and like I said, will act as guidelines for that.
Freedows has a main development scope: the development of a core kernel system based in the Cache Kernel model, being able to emulate other OSes through Application Kernels. That objective is going to be divided into stages, where the development of specifications is the first, as following:
Development Map
---------------
1. Specifications and Guidelines
2. Core kernel development
3. Alpha Testing of the core kernel
4. Application kernel development
5. Beta testing of the application kernels
6. Working model of an operating system ready
7. Beta testing of the working model
8. Operating System Public Release
These stages should be followed carefully and made through the specifications created in Stage 1.
3. Work that has been done
There has been work done that belongs to Stage 1 of the development map. Though the Freedows OS Project has begun that stage, it still needs a more focused work guide. In early 1998, some work related to current stages 1 and 2 has been done though; that work that is publicly available can be adapted to our new development target.
Copyright (C) 2000 Freedows OS Project. All rights reserved.
Hi...
I will be attempting to get a preliminary proposed general system spec revamped, and posted here very soon for our discussion.
I would like very much if we could open some discussion on this, as well as Fabian's letter.
Reece
Perhaps I'm being a bit anal retentive already, but could we come up with a set of documents to at least take a look at? Somebody has done some work. Let's have a basis for discussion other than some banter on newsgroups, listservers, and IRC.
Reece, you'll see I have technical writing in my background. Not that I like to write -- I hate it with a passion -- but I end up doing it at every gig I get because none of the captives did any documentation on the project before I started working on it. <sigh> Such is the nature of things, I guess. That's what they pay the Big Money for.
If we need someone to organize and write up docs for the work that has already been done I volunteer. I'd rather do this work than sit and
whine about not having anything to do. Eh?
---
The Old Fart
Hi...
One area that could really use some work from someone with technical writing background <hint hint> ;-) would be breaking up the Stanford Cache Kernel Document, and making it easier to understand. I think I'm one of the
few people that actually understands it, and it's not really helping the development process much to have it like that.
I'm also working on a new general system spec (which I'll have ready "soon"), which requires a lot of discussion.
There are also some old specifications from prior development, which we could discuss as well, however I'm not certain we should run ahead and adopt those as our current design; I've looked at some of them, and they seem to
be sort of, non Cache-Kernelish.
Reece
Gotcha. I got the doc from http://www-dsg.stanford.edu/papers/cachekernel and expect to start working on it this week. Does anybody have any requests for specific clarifications, expansion, or other editorial content? Let me know.
---
The Old Fart
Any new development on the documentation?
cheers,
IGUN
Am I too late for anything