Re: devolopin a mew lang........



On Friday 30 June 2006 01:44, I stood up and spoke the following words
to the masses in /comp.os.linux.misc...:/

The kernel manages the hardware, which is a trait of monolithic
kernels - not to be confused with "monolithically compiled kernels",
but to be seen in contrast with a microkernel design or an exokernel
design.

As I've explained in another post recently the differences are the
following:

(a) A monolithic kernel manages process scheduling, memory management
and hardware access.
(b) A microkernel manages process scheduling and memory management.
(c) An exokernel manages process scheduling.

That which is present in (a) but not in (b) and (c), or present in (a)
and (b) but not in (c) takes place in what we call userspace. [...]

And just for in the event that someone decides to jump in and claim me
wrong or "refusing to accept my defeat" or something of the likes - I
seem to have attracted the attention of two people with egos larger
than their courtesy - the sentence "... takes place in what we call
userspace" pertains to those things that are _not_ part of said kernel
design.

In microkernels, this "taking place in userspace" pertains to hardware
access. In exokernels, it pertains to both hardware access and memory
management.

For those interested in the fairly new and lesser-known concept of
exokernels, MIT have recently developed an experimental UNIX-like
operating system based upon an exokernel design. I haven't looked into
the details, but my guess is - it would be the most logical approach -
that the exokernel functions as a kind of hypervisor for virtualized
and concurrently running copies of the operating system software.

You can read more about it here - I myself haven't read it all too
thoroughly and certainly not recently ago...:

http://pdos.csail.mit.edu/exo.html

--
With kind regards,

*Aragorn*
(Registered GNU/Linux user #223157)
.



Relevant Pages

  • Re: design of the unix operating system - maurice bach
    ... >>i dont really understand why someone decided that kernels shouldn't be ... > It's harder to design such an OS, and hard to implement it correctly. ... And, when Unix was originally designed, there were no multi-processor ... Enterprise Technology Solutions, TD Bank Financial Group ...
    (comp.unix.programmer)
  • Re: Howto resolve which interface a NICs is mapped to ( nic2if )
    ... This method is broken by design when you decide to activate eth1 before eth0. ... Isn't it rather that modutils for 2.4 kernels uses modules.conf while module-init-tools for 2.6 kernels uses modprobe.conf? ...
    (comp.os.linux.networking)