Amiga's kernel

[obscurepanic]

In Wikipedia, AmigaOS has an atypical microkernel.

http://en.wikipedia.org/wiki/Amigaos

As I googled it deeper, I bumped into an website and saw a comment:

AmigaOS is a beast on its own. Yes it was designed like a microkernel, with each device and filesystem having their own thread (task), but it doesn't actually have any enforced boundary between userland and kernel land, nor memory protection, which greatly lowers the latency. It's like a single kernel process running each app as a different thread in the kernel.

http://www.haiku-os.org/community/forum/haiku_kernel_architecture_questions_0

How does the kernel really work in Amiga vis-a-vis its architecture?

[obscurepanic]

The quote you have from Wiki/google, just about sums it up.

You mean an application on AmigaOS act like a minicomputer on its own?

What is your question exactly?

How AmigaOS' architecture and kernel really works. I'm not too familiar with Amiga, so I was curious. Even the previous example quote was a wee bit to understand.

Why being atypical? No huge difference between the kernel and userland? What points are very different from a generic UNIX monolithic kernel?

Thank you.

[obscurepanic]

I found an interesting old article about this (with several spelling errors). http://www.cunningham-lee.com/misc/amiga_exec.html

someone, who obviously comes to this forum just to ask some technical questions probably out of pure interest and sees his thread mutating within few replies into war of fractions must really think everybody is gone insane here! hope he'll never return to read this all.

Pardon?

Consider I'm from East Asia, I am very bitter towards the quasi-total dominance of Microsoft from servers to desktop. I just couldn't care much about the rantings here as long as I can ease my Microsoft hate a bit.