[Kos-cvs] kos-web/contents features_en.i,1.10,1.11

[thomas at kos.enix.org]

Update of /var/cvs/kos/kos-web/contents
In directory the-doors:/tmp/cvs-serv16348

Modified Files:
	features_en.i 
Log Message:
Et hop, la version en anglais y passe aussi.


Index: features_en.i
===================================================================
RCS file: /var/cvs/kos/kos-web/contents/features_en.i,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- features_en.i	29 Dec 2004 20:50:56 -0000	1.10
+++ features_en.i	3 Jan 2005 23:15:30 -0000	1.11
@@ -2,7 +2,56 @@
    start_content_section("Features", "");
 ?>
 
-The main features (and terminology) of the Kid Operating System are :
+
+<p>The <b>KOS</b> operating system has two main interesting features
+that are not present in other classical operating systems :</p>
+
+<ul>
+
+ <li><b>Modular conception</b> : the <b>KOS</b> kernel is split in
+several <i>modules</i> loaded by <a
+ href="http://www.gnu.org/software/grub/">GNU Grub</a> and
+ <i>linked</i> together at boot time by a specific
+ <i>loader</i>. Contrary to <a href="http://www.kernel.org">Linux</a>
+ in which only device drivers and optional components of the kernel
+ are modules, in <b>KOS</b> everything is a module, even the
+ <i>scheduler</i> of the virtual memory management
+ subsystem. Splitting the code into modules enforces clean interfaces
+ between them and clean programming. The modules are ELF object files
+ loaded from the disk or the network by Grub. Our loader then links
+ the modules and runs the resulting program : the <i>kernel</i>. The
+ first operation of the <i>kernel</i> is to initialize the system
+ according to the <i>init levels</i> specified in each module. More
+ information can be found (only in french, sorry) in the <i>Modules
+ dans KOS</i> documentation, available in the <a
+ href="http://kos.enix.org/~d2/snapshots/kos_current/doc/modules-html/">HTML</a>,
+ <a
+ href="http://kos.enix.org/~d2/snapshots/kos_current/doc/modules.ps">PostScript</a>
+ ou <a
+ href="http://kos.enix.org/~d2/snapshots/kos_current/doc/modules.pdf">PDF</a>
+ formats ;</li>
+
+ <li><b>System resource management</b> : <b>KOS</b> provides an
+ <i>interface collector</i> named <i>Karm</i> for <i>Kos Abstract
+ Resource Management</i>. <i>Karm</i> is in charge of the link between
+ user-space applications and the kernel. The idea is to replace the
+ traditionnal fixed and unique <i>file</i> interface that is the basis
+ of the Unix system and the ugliness of the <code>ioctl()</code>
+ system call. Our proposal is a system that allows to export custom
+ and specialized interfaces to user-space applications and
+ libraries. Each <i>resource</i> of the system can be accessed through
+ a set of interfaces specific to this ressource and its nature. For
+ more information, you can also read the report (in Frennch only,
+ sorry) written par Thomas Petazzoni and Mélanie Bats during their
+ work on this subject at the <a href="http://www.utbm.fr">UTBM</a> in
+ the <a
+ href="http://kos.enix.org/pub/tx-rapport.pdf">PDF</a> format.</li>
+
+ </li>
+</ul>
+
+<p>Here are the more classical features of <b>KOS</b> to give an idea
+of the state of the project.</p>
 
 <ul>
  <li><b>Target architecture:</b> PC (Intel 80486 or Pentium
@@ -12,15 +61,6 @@
  ...), ELF32 binary format. Unix host (Linux/x86,
  Solaris/sparc+cross-gcc Ok) highly recommended</li>
 
- <li><b>Modular design:</b> <a
- href="http://www.gnu.org/software/grub/">GNU Grub</a> loads the KOS
- <i>loader</i> and the KOS <i>modules</i> from disk or
- <i>via</i> the network. The KOS <i>loader</i> links the modules
- together and transfers the control to the resulting program: the KOS
- <i>kernel</i>, whose first operation consists in initalizing the
- system according to the <i>init levels</i> specified in the
- modules.</li>
-
  <li><b>Physical memory addressing:</b> mainly paging (segmentation
  only to setup the Flat model). 4GB of physical memory totally
  available to the system (the kernel does not rely on <i>identity
@@ -57,16 +97,12 @@
  <li><b>Address space management:</b> inspired from SVR4 (<tt>vmm</tt>
  module). Demand paging, file/anonymous mapping.</li>
 
- <li><b>System resources management:</b> Interface collector for
- device drivers, called <i>Karm</i>, for <i>Kos Abstract Resource
- Management</i>. <i>Karm</i> is in charge of the link between user and
- kernel by exporting customizable interfaces to the user space. It is
- one of the interesting point in KOS.</li>
-
  <li><b>User-mode:</b> <i>teams</i> having their own address space,
  composed of <i>threads</i>. The teams may share pages in memory. The
  kernel space (0-2GB) is shared by all the teams. First toy user-mode
- application available.</li>
+ application and associated very very very tiny <i>libc</i>. This
+ <i>libc</i> can use the resources and interfaces exported through the
+ <i>Karm</i> system described above.</li>
 
  <li><b>Software and hardware resources supported:</b>
   <ul>