News for hackers. Stuff that matters.
Re:Minix 3.3.0 by VLM on Tuesday September 16, 2014 @10:53AM (#8324761)
"minix has a spot, and that spot is in education,"

Yet they're pushing for reliable embedded hardware. Not all that bad of an idea. Given the nightmare of android security updates (or complete lack there of) this would make a nice embedded controller.

Need RTOS features. For .edu or .com embedded use.

The microkernel idea is pretty much dead outside the ivory tower, as in practice it didn't work, so I wouldn't be so pessimistic about how things turned out.

Re:Minix 3.3.0 by wolfgke on Tuesday September 16, 2014 @11:02AM (#8324822)
> The microkernel idea is pretty much dead outside the ivory tower, as in practice it didn't work,

The L4 microkernel

> http://en.wikipedia.org/wiki/L4_microkernel_family

is really fast and used quite often. See

> http://en.wikipedia.org/wiki/L4_microkernel_family#Commercia...

for details about its usages.

Re:Minix 3.3.0 by valarauca1 on Tuesday September 16, 2014 @11:05AM (#8324850)
>as in practice it didn't work

QNX says, "Hi." Nearly every router with >1GB/s ports run a microkernel.

Blackberry's phones run microkernels.

Yeah its closed source locked down, but its a functioning high performance micro-kernel.

Re:Minix 3.3.0 by jacquesm on Tuesday September 16, 2014 @11:13AM (#8324883)
I've sent a bunch of letters to Quantum software when they still owned it about open sourcing QnX but they never bit. In spite of substantial backing and a pretty good plan (a redhat like model) there was absolutely no interest.
Re:Minix 3.3.0 by mwcampbell on Tuesday September 16, 2014 @12:00PM (#8325156)
> Nearly every router with >1GB/s ports run a microkernel.

Do you mean home wireless routers, or higher-end routers? I thought most home wireless routers these days, including gigabite-capable ones, were running Linux. Can you give specific examples?

Re:Minix 3.3.0 by noselasd on Tuesday September 16, 2014 @01:03PM (#8325508)
Re:Minix 3.3.0 by jacquesm on Tuesday September 16, 2014 @12:02PM (#8325162)
He means non-(pro)consumer stuff.
[deleted]
Re:Minix 3.3.0 by cgh on Tuesday September 16, 2014 @02:07PM (#8325974)
No, Cisco's NX-OS, which runs on Nexus-series ethernet switches and MDS-series SANs, is based on MontaVista Linux. These are not niche products.
Re:Minix 3.3.0 by mwcampbell on Tuesday September 16, 2014 @01:55PM (#8325888)
Oops, missed the greater-than sign in ">1GB/s". That's what I get for reading via text-to-speech with a lot of punctuation excluded.
Re:Minix 3.3.0 by jacquesm on Tuesday September 16, 2014 @11:04AM (#8324837)
> The microkernel idea is pretty much dead outside the ivory tower, as in practice it didn't work

A huge swath of the real time world (process and industrial control, all kinds of embedded gear) runs on microkernels. They're enormously successful, just not very visible.

Re:Minix 3.3.0 by VLM on Tuesday September 16, 2014 @11:17AM (#8324900)
I guess what I'm getting at, is in a fair fight, an open source monolithic always works better than an open source microkernel. Behind closed doors decisions always have other concerns... licensing, support contracts, standardized docs, porting assistance, the list goes on and on.

For example, look at the recent minix release notes listing the well known theoretical advantages of a micro when a driver fails. Then look at the actual release notes where ARM USB is broken and crashes the entire kernel, in practice.

So with a theoretically superior microkernel design, you could restart a crashed driver in theory, although in practice when drivers crash they take the kernel with them. So you could recover from an error although in practice it doesn't work.

With a theoretically inferior monolithic design, you can't (easily) restart a crashed driver. Monoliths work around that problem by not crashing. See linux USB support on ARM. So you can't recover from errors, that don't happen anyway, so in practice it doesn't matter.

In actual deployment it doesn't matter anyway because software of a low enough quality to suffer severe driver problems most likely won't live long in the marketplace, and most driver software issues are a symptom of the device hardware being damaged, destroyed, or removed. So if your mass spectrometer A/D converter was vaporized by literal lightning, it doesn't really matter if the kernel crashes; besides the lightning probably vaporized the CPU at the same time.

One event like this is an anecdote. A couple is a trend. A couple decades of this in the marketplace, well thats something else.

Re:Minix 3.3.0 by jacquesm on Tuesday September 16, 2014 @11:24AM (#8324942)
Minix is not at all the best example of a microkernel, which is why I have yet to see it in production. QnX is an example of a best-of-breed microkernel and the thing is for want of a better word indestructible. We ran large clusters (for the day) of these and there has never been a documented case of a crash of a kernel that was not hardware related. Pretty impressive given the number of transactions that we would push through those boxes.

Device drivers in QnX are completely separate processes that use send/receive/reply to communicate with the kernel, just like every other process. On top of that they have the ability to talk to hardware. If a device driver causes a bus to be locked and never unlocked or if a device driver starts talking to ports that it has no business talking to then that can cause a problem. So as long as hardware is involved device drivers can cause trouble for all the other processes on the system.

But in QnX those are very rare instances, I've never seen one but my QnX days preceded the arrival of USB.

Re:Minix 3.3.0 by taeric on Tuesday September 16, 2014 @11:59AM (#8325143)
Can you share some of what these clusters were doing? Sounds interesting.
Re:Minix 3.3.0 by jacquesm on Tuesday September 16, 2014 @12:00PM (#8325154)
A very large message switch with very harsh penalties in case it was down. At some point in time it brokered a substantial portion of the worlds shipping tonnage.

Privately held company, very small, very wealthy.

Re:Minix 3.3.0 by taeric on Tuesday September 16, 2014 @12:06PM (#8325192)
What sort of messages? And, any logic in routing them? Or is this literally a network switch?

Curious how this stacks up against the likes of Amazon's or Twitter's stuff. Or do they have Qnx based setups, as well?

Re:Minix 3.3.0 by jacquesm on Tuesday September 16, 2014 @12:19PM (#8325275)
> What sort of messages?

Broadcasts of capacity seekers and offerers. Along the lines of 'I have 50 40' containers sitting in Panama, Colón, destination Rotterdam, bids in by 14:00 GMT tomorrow'.

This would then get broadcasted to all parties that were capable of taking on all or part of that load, within a guaranteed delivery time through just about every medium you can think of with the exception of carrier pigeons.

This does not compare at all with Amazon or Twitter, though twitter uses 'Erlang' in their stack somewhere and quite a bit of the philosophy Erlang uses dovetails with the way you build such systems (which is perfectly logical because Erlang came out of Ericsson and they had problems that were mostly synonymous with message switching).

I'm not aware of either using QnX in their setup.

Re:Minix 3.3.0 by taeric on Tuesday September 16, 2014 @01:49PM (#8325859)
Cool. Probably compares more favorably with them than you are letting on. The volume you seem to be implying sounds very impressive.

It does make me wonder if the world should have just gotten better at state machine construction. This seems like if you kept it simple, things would have been straight forward to scale. (Not necessarily easy.)

Which is all to say that I do question how QNX really helped here. Seems more a side detail that neither helped nor hurt the effort.

Re:Minix 3.3.0 by jacquesm on Tuesday September 16, 2014 @02:00PM (#8325927)
Without QnX's network transparency, reliability and message-passing features this project would not have existed. The OS was absolutely instrumental.
Re:Minix 3.3.0 by taeric on Tuesday September 16, 2014 @03:57PM (#8326739)
I find that hard to grok following an admission that erlang could be used to architect systems using similar ideas. :(

That is, that you had a network transparent message passing system with high reliability is the key. That it was implemented at the OS level seems a side detail.

Re:Minix 3.3.0 by jacquesm on Tuesday September 16, 2014 @04:02PM (#8326760)
At that time it was the only way we could have done it that I'm aware of. We're talking 1985-1989 here! Feel free to disagree with decisions made almost 30 years in the past.
Re:Minix 3.3.0 by taeric on Tuesday September 16, 2014 @04:12PM (#8326824)
I'm not disagreeing with the decision at the time. Merely saying that the key was not that it was at the OS level. The key seems more that the rest of the details were in place. (If that makes sense.)

That is, if you were to want to build something like that today, I would remove "at the OS level" from the primary constraints in building this solution. Granted... depending on the rest of the requirements, it is highly possible one might go sans OS and just have an FPGA solution. Odds are, though, that would be overkill and more restrictive in possible solutions than necessary.

This is precisely my thought on microkernels. At face value, what is there not to like? In practice, the idea seems overly restrictive and makes it very hard to do some things that you sometimes wish to do.

Re:Minix 3.3.0 by jacquesm on Tuesday September 16, 2014 @04:27PM (#8326906)
Well, you're arguing against someone with 30+ years in software development who actually built stuff using microkernels and macrokernels and who wrote an OS on top of that. That's as shallow an appeal to authority as you'll ever get from me but frankly what your thoughts are does not trump my personal experience to me. In practice microkernels are not overly restrictive and they make things about as easy as they could possibly be. Those things that I happened to do at the time. (Such as, but not limited to: routers, device drivers, image recognition, mail, networking, a supervisor system, logging, reliable storage and on and on, basically everything that goes into a cluster based chunk of enterprise level software with a very specific goal).

This was not a theoretical exercise, it built a very deep and wide defensible moat, every Monday was a day pushing a record number of messages through the system since its inception, in other words, growth was continuous and downtime unbelievably (by todays standards) low. Which had a lot to do with the intrinsics of the OS.

And you have my word that without QnX as the cornerstone of that development it would have simply never happened. You can believe me, you don't have to but you're asking me for my reasons and then you proceed to dismiss them on the basis of your theories.

Practice > Theory any day.

Re:Minix 3.3.0 by taeric on Tuesday September 16, 2014 @04:38PM (#8326971)
I don't get your point. You are doing an appeal to authority, yet you seem to be literally arguing with history and entire industries as to what can make a very scalable system. Or, is your argument that Twitter would be more reliable if it were done with QNX? What about Amazon? Google? Any behemoth out there?

If that is your argument, then it seems a moot subject. We'll never know. If Twitter had originated on a microkernel based operating system, would it have gotten the traction it did? Beats me. Not even sure how you could approach such a question.

Now, I fully agree with the view that historically a major way to get these was to go with a solution like QNX. My point is merely that the reliability of other solutions is not as far behind as they used to be. To the point that limiting yourself to only run on one of these systems seems overly restrictive. (And again, that is in today's world. Not the one of 20+ years ago. Probably not even the world of 5+ years ago.)

Re:Minix 3.3.0 by jacquesm on Tuesday September 16, 2014 @05:07PM (#8327127)
> I don't get your point.

That's ok. I've spent enough cycles trying to get it across I think. Good night!

Re:Minix 3.3.0 by imanaccount247 on Wednesday September 17, 2014 @03:29AM (#8328916)
>The microkernel idea is pretty much dead outside the ivory tower, as in practice it didn't work,

That would certainly explain the billions of microkernels running in production as we speak. Better tell amazon to shut down their whole webhosting business since microkernels don't work. I'm sure they'll be dissapointed to learn about this.

Re:Minix 3.3.0 by Zardoz84 on Wednesday September 17, 2014 @02:56AM (#8328859)
I belive that AmigaOS was based on microkernel ideas. Not pure, but very near. And it was working very well. My Amiga 1200 boot ups much more faster that Windows or Linux in my moderm quad core machine
Re:Minix 3.3.0 by pjmlp on Tuesday September 16, 2014 @11:46AM (#8325049)
Except most embedded and real time kernels are micro-kernels or hybrid designs.

Talk about being dead.

Re:Minix 3.3.0 by taeric on Tuesday September 16, 2014 @11:51AM (#8325093)
This point is easy to mislead, though. Consider, the android kernel is probably rapidly growing in the realm of what would have once been considered for embedded kernels.

And it isn't like most of us do not like some of the ideas behind microkernels and the like. The empiricist in me has grown to doubt that it is as much of a win as the hopefuls keep talking about. That is, even if someday microkernels make a pretty big comeback, I doubt it will be as dramatic of a change as is always heralded.

Re:Minix 3.3.0 by jacquesm on Tuesday September 16, 2014 @12:04PM (#8325174)
> I doubt it will be as dramatic of a change as is always heralded.

I doubt it will happen. But if it happens the difference will be so large that you will be wondering why we didn't do that decades earlier. It's a bit like those people that work with emacs and lisp at home that then have to go to work and use Java or PHP.

Re:Minix 3.3.0 by taeric on Tuesday September 16, 2014 @04:58PM (#8327085)
I'm one of those people, actually. To the point that I now just use emacs at work. Have slowly started using it for all things. Email, irc, im, etc. Is very very nice. Always amusing to hear folks talk about how limited it is.

But, I still can't deny that the modern IDE has gone a long way to advance what can be done outside of emacs. To the point that I just can't bring myself to think the difference between the LISP world and any other is as large as it is often made out to be.

Re:Minix 3.3.0 by vegggdor on Tuesday September 16, 2014 @03:36PM (#8326622)
Android is not a good example, for one, the usecase is almost no different to the desktop, except for the issue with power efficiency . secondly, the real time part of the system, ie. the controllers, doesn't run android. It rather runs L4 in the baseband processor - a microkernel.
Re:Minix 3.3.0 by taeric on Tuesday September 16, 2014 @03:55PM (#8326729)
I think this response actually came later. Apologies for that to the other poster.

This is pretty much my point. This "embedded systems use microkernels" is easy to paint in such a way that it supports either argument. Comes down almost to the scottsman falacy.

More to the point, if I were to claim that my phone is really running a microkernel, I would be ignoring the majority of the software on my phone. I mean, yes it is true. But it is laughable in that the majority of the programming on the device is not in L4. To a large margin.

Consider, you are at this point merely claiming that a state machine in your device is running in a microkernel. And, to the non-microkernel that runs the majority of the phone, it is but a device. So, we have a non-microkernel running a microkernel as a standard device.

Re:Minix 3.3.0 by vegggdor on Tuesday September 16, 2014 @08:23PM (#8327835)
I'm sorry, i love talking semantics and that's what this discussion is, if you question the meaning of embedded. That word is not well defined, afaict, and i was just trying to add some perspective.

> I would be ignoring the majority of the software on my phone

I'd like to argue that the baseband processor is the biggest part of the phone, save for relaying and converting the microphone input. The rest is just a handheld computer. But that's the True Scottsman you made out. In fact, Android might be a good example, just one that doesn't support your point too well, because the Scottsman Fallacy is working both ways. When we are talking true OS with services and drivers et al, android is relevant, ofc. Still, it might be chosen because of any other reason as well. The reference to Android is akin to an argument of authority.

You can run Linux on L4 as a hypervisor, by the way. I have no clue how that works, but maybe we have a microkernel running the Linux-kernel as a service. :)

Re:Minix 3.3.0 by taeric on Tuesday September 16, 2014 @11:48PM (#8328486)
Agreed on this being a semantic discussion.

I can see the compelling nature of the baseband processor being the largest part of a phone. If only because of the name of the device. The reality, I assert, is that the phone is now just another component inside a pocket computer I happen to carry around. Ironically, it is mainly used from an app called "Phone" on said device.

And, my entire point for this thread is that Android as an example can be used to cut both ways. That was what I meant by saying it could support either argument. (I cede that my opening comment did not make this clear. It was what I meant by saying "this point is easy to mislead.")

I do not see how it is an appeal to authority, though. It is meant to be an appeal to evidence. Just as the claim that "embedded systems use microkernels" is.

Re:Minix 3.3.0 by pjmlp on Tuesday September 16, 2014 @04:02PM (#8326763)
Symbian and QNX, then you have a micro-kernel for the whole software stack.
Re:Minix 3.3.0 by taeric on Tuesday September 16, 2014 @04:19PM (#8326854)
Which feeds right back to my point. How did that work out? :)
Re:Minix 3.3.0 by pjmlp on Tuesday September 16, 2014 @05:35PM (#8327244)
The technical capabilities are not to blame for the political warfare of management.
Re:Minix 3.3.0 by taeric on Tuesday September 16, 2014 @11:39PM (#8328451)
Eventually, this ceases to read as a reason, and falls more into just an excuse. Told by what seems to be more and more of a bitter crowd. :(
Re:Minix 3.3.0 by Demiurge on Wednesday September 17, 2014 @12:44AM (#8328650)
So, you don't find it bitterly ironic that Symbian was replaced by a hybrid kernel based OS (NT) instead of a monolithic one?
Re:Minix 3.3.0 by tacticus on Wednesday September 17, 2014 @06:46AM (#8329391)
Most of the symbian devices are being replaced by android phones not windows phones.

The high end market is android and ios. the middle of the market is android and small amounts of other the low end of the market is android for the most part now as well.

Re:Minix 3.3.0 by Demiurge on Wednesday September 17, 2014 @09:33AM (#8329825)
A lot of Androids are getting replaced with iOS this week. Are you aware it is also hybrid of Mach microkernel and POSIX apis?
Re:Minix 3.3.0 by Symmetry on Tuesday September 16, 2014 @12:00PM (#8325149)
I'm given to understand that on many phones Android runs in the application core on top of an L4 kernel, which provides resources to Android but also controls the various DSP and embedded cores.