Poe's Law strikes again. I can't tell if you're making a joke or not.

Assuming you're being serious: no. Linux distributions do not work this way because Linux was itself deliberately designed to be unlike Minix.

Minix is not a linux distribution.

If you do not know about Minix and Microkernels, you probably want to dig into the famous debate between Tanenbaum and Torvalds.

http://oreilly.com/catalog/opensources/book/appa.html

http://en.wikipedia.org/wiki/Tanenbaum%E2%80%93Torvalds_debate

A "Linux distribution" - by definition - use the Linux kernel - as there is no "Linux" system/os. So RedHat, Debian/GNU Linux, Ubuntu and Android are all "Linux distributions" (although, GNU/Linux is usually a better term [edit: Android, afaik does not use a lot, if any GNU code]). FreeBSD, Nexenta (open source Solaris with a GNU userland), Debian/kfreeBSD and Debian/HURD are not Linux distributions, but they are operating system distributions. The latter one would be similar in the sense that HURD is a microkernel.

Minix is very good for learning internals of operating system. In my second year of undergrad, I went through the code of minix and and it was a great learning experience. I could learn a lot about the internals of operating system by looking at real working code rather than just reading theories. The Linux code is too complicated for beginner. I think, Linux can not replace minix in educational world.

Andrew Tanenbaum explains: http://www.youtube.com/watch?v=bx3KuE7UjGA

Minix is a true microkernel architecture, but also a complete and practical OS. The analogy to NetBSD is a good one, since they're both largely didactic devices, but they demonstrate radically different internal operating system architectures.

Minix is a microkernel architecture. Many of the services which in other OSes live in kernel space are pushed out into standalone processes.

The main goal is to improve reliability. Bad drivers or bad hardware are the leading cause of lockups these days. If you isolate the drivers, file system etc from one another, you can prevent the whole system from dying. Minix3 goes further than its predecessors by adding a "reincarnation server", which periodically pings other servers and kills/restarts them if they've become unresponsive.

Minix essentially does at a single-system level what cloud architectures try to do at a multi-system level: assume that the parts are unreliable, isolate faults and recover by restarting sub-units.

To me the more interesting possibility is that in a microkernel world you could solve a number of classic OS/system software bunfights. Databases, for example, tend to fight a bit with OSes about the best way to buffer data or flush to disks. In a microkernel system you can arrange matters so that the database provides its own memory and disk management. It's just another process; nothing special.

Here's the report that was written about the design: http://www.minix3.org/docs/jorrit-herder/osr-jul06.pdf

Mainly research and education. MINIX is meant to be (though I haven't read the code since the first edition printed in Tanenbaum's book) a clean, simple project for students and researchers to begin hacking on easily . In this day and age, research OSes don't become mainstream ones, but MINIX could be a good target for research which would make its way to the more widespread OSes if successful.

The above is stating the obvious, so I presume you are asking about commercial/embedded use. The answer is probably similar - if you want a nice clean base to start from and want a general-purpose UNIX rather than a realtime system, and you don't need much from the userland beyond classic UNIX tools. Perhaps your work involves hacking at the system level, or you're keen on having a microkernel architecture. It's a bit niche but could be a very suitable base for an embedded project.