Hi,
I have read that wiki page. There is nothing in it. It says *"Many operating
systems and kernel experts (incl. Torvalds and Rao) have dismissed the label
as meaningless, and just marketing"*. Does it mean that hybrid kernels are
bad? I don't think so.

Doesn't NT kernel serves the purpose for Windows?
Doesn't XNU kernel serves the purpose for Mac OS X?

The "loadable kernel modules" and "fuse" in Linux are actually Micro kernel
features. Right? The monolithic Linux kernel also has now a kind of hybrid
design.


On Wed, Jun 4, 2008 at 10:19 PM, Mahesh Aravind <ra_mahesh at yahoo.com> wrote:

> --- On Sun, 6/1/08, shirish <shirishag75 at gmail.com> wrote:
>
> > Hi all,
> >  I would also like to know what's wrong with hybrid
> > kernels?
>
> As in what's wrong with 3-wheeled cars? Huh?
>
> Have you read http://en.wikipedia.org/wiki/Hybrid_kernel
>
> Somethings are special purpose.  There's no Good or Bad about them.  Some
> things exit because it serves a purpose.  If it doesn't serve the purpose
> it exists for, then it's BAD!
>
> Also, I don't like the idea of Copyrighting email messages -- it FORCES
> people to quote it VERBATIM (have you REALLY read the LICENSE???).  With the
> License agreement attached, and other useless wastes, just to close the legal
> loopholes. (I'm not doing it
>  -- so I'm violating your license -- sue me
> -- we shall meet in court ;)
>
> A work around is to use disclaimers.  That this message puts forth YOUR idea
> only, not your company's etc.  VERBATIM sharing of email messages is
> SICK!!! (S-I-C-K).  The headers, the X-mailer-thingys, and other RFC 822/2822
> nonsenses attached.
>
>
>
> _______________________________________________
> Mailinglist mailing list
> Mailinglist at ilug-cochin.org
> http://ilug-cochin.org/mailman/listinfo/mailinglist_ilug-cochin.org
>
>


-- 
Regards,
Jain M Johny
jainmjo[at]gmail
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://ilug-cochin.org/pipermail/mailinglist_ilug-cochin.org/attachments/20080605/45beed4e/attachment.html
 

Reply via email to