8 ms·
HelenOS: portable microkernel-based multiserver operating system
- the-dude 9y agoWell it is obvious this is no Beowulf cluster.
- ty_a 9y agoSerious question, are Beowulf clusters still a thing?
- zrail 9y agoSure. They're not really called Beowulf clusters anymore, but even at the beginning there wasn't any particular defining characteristic other than a cluster of commodity servers running some kind of software that made them work together. You could consider the clusters at LHC, the render farms at Weta and Pixar, and (if you squint) the non-web clusters at Google and Facebook to all be spiritual descendants of the original Beowulf cluster. https://en.wikipedia.org/wiki/Beowulf_cluster https://en.wikipedia.org/wiki/Beowulf_cluster
- GauntletWizard 9y agoHuh. I always thought that Beowulf was an actual piece of software. But apparently it's only a capability set, and by its definition every Mesos and Kubernetes installation counts. Cool.
- pjmlp 9y agoAh, still remember the early days of the LHC Computing Grid.....
- bogomipz 9y ago>"... the non-web clusters at Google and Facebook to all be spiritual descendants of the original Beowulf cluster." I was intrigued by this comment. Could you elaborate on this? Are there specific concepts from Beowulf that FB's Tupperware and Google's Borg borrowed?
- zrail 9y agoThe entirety of the Beowulf concept is a cluster of commodity machines networked together that can work together to perform some kind of task. It's pretty general. The original Beowulf-style clusters ran things like mosix to present a single system image for applications but as far as I can tell that was never a defining characteristic.
- bogomipz 9y agoThanks, yes that's pretty broad, makes sense. Cheers.
- rbanffy 9y agoSometimes a very little thing ;-) https://shop.pimoroni.com/products/cluster-hat https://shop.pimoroni.com/products/cluster-hat
- sannee 9y agoThis shows a pet peeve of mine: the Raspberry Pi does not have USB available in a way which would allow a HAT to interface with it in a more sensible way than wrapping around a cable from the "external" ports. I wonder if there is a pair of 90 degree USB connectors which would height-match a standard .1" header.
- topspin 9y agoPerhaps the "Compute Module" is the thing to use for Raspberry Pi clusters. Probably fit 100+ in 1U with no cables at all.
- rbanffy 9y agoI'd love to see a revision/extension of the Pi connector adding the Ethernet signalling. This would make it easy to build clusters using any board compatible with the ecosystem. The SOPINE (a Pine A64 cousin https://www.pine64.org/?page_id=1491 https://www.pine64.org/?page_id=1491) seems to have the Ethernet signals on the edge connector, making a cluster much easier to build out of a single backplane. The Rock64, an A64 successor, has the Ethernet on pins, but the position is a bit awkward. But yes. At least the USB should be available on the expansion bus.
- nobodyorother 9y agoYeah, it's like a more prophetable Cassandra cluster.
- deleted 9y ago[deleted]
- bantunes 9y agoGood to see multiserver microkernels back on HN. Have significant advances been made to make message passing better in modern CPUs?
- snvzz 9y agoIf you're worried about performance, see http://blog.darknedgy.net/technology/2016/01/01/0/ http://blog.darknedgy.net/technology/2016/01/01/0/
- zerebubuth 9y agoAn example from the linked blog post: > It strikes me that anti-microkernel sentiment most vocally originates as a sort of tribal affiliation mechanism by Linux users to ward off insecurity. I think the post would be a better reference and stand a greater chance of correcting common misconceptions if it didn't include so many ad-hominem attacks against those who don't agree with the post's author. As-is, it just appears to be a continuation of a long-running flame-war.
- snvzz 9y agoI agree. Unfortunately, I am not aware of a compilation of misconceptions on microkernels article that's more valuable than this one.
- vmateixeira 9y agoLoad issues?
- agumonkey 9y agohttp://archive.is/w6Li0 http://archive.is/w6Li0 to the rescue (1 week old though)
- vmateixeira 9y agoThanks :)
- shp0ngle 9y agoAh, HelenOS. The popular MSc thesis factory at my old school. Good times. edit: just look at all the theses that were made out of it. :) http://webcache.googleusercontent.com/search?q=cache:geWe63MvkSAJ:www.helenos.org/wiki/Documentation&num=1&strip=1&vwsrc=0 http://webcache.googleusercontent.com/search?q=cache:geWe63M...
- msla 9y agoInteresting blog post related to this: https://utcc.utoronto.ca/~cks/space/blog/tech/AcademicMicrokernels https://utcc.utoronto.ca/~cks/space/blog/tech/AcademicMicrok... > microkernels are small in both scope and (hopefully) code size. Small projects are achievable projects in academic research. > a microkernel is naturally limited in functionality, so you have an excellent reason to not implement a lot of things. This drastically reduces the scope of your work and gives you a great excuse for not coding a lot of boring, routine infrastructure that's necessary for a usable system. > (Note that in academic research you basically cannot afford to implement things that will not result in papers, because papers are your primary and in fact only important output.) > microkernels are (strongly) modular, which makes it easier to farm out work among a bunch of students, postdocs, and research assistants. A strong division of labour is important not just for the obvious reason but because it increases the number of papers that all of the people working on the project can collectively generate. If everyone is involved in everything you probably get one monster paper with a monster author list, but if people are working mostly independently you can get a whole bunch of papers, each with a small number of authors. > (And if someone wants to get a MSc or PhD thesis out of their work, they have to be working on their own.) > microkernels have a minimal set of primitives, which makes it easy to write papers about them. You don't have to try to describe a large, complex OS and what makes it interesting; you can simply write a paper about the microkernel primitives you chose (and perhaps some clever way that you implemented them and made them acceptably fast). > there are lots of choices for viable primitives and thus lots of different microkernel designs, which means that it's easy to do new work in the field; all you have to do is pick a set of primitives that no one has used yet. > there is a strong liking for elegant minimalism in basically all parts of academic computer science. The minimalism of microkernels plays right into this overall attitude. > the whole 'normal kernel on microkernel' idea of porting an existing OS kernel to live on top of your microkernel gives you at least the hope of creating a usable environment on your microkernel with a minimum amount of work (ie, without implementing all of a POSIX+ layer and TCP/IP networking and so on). Plus some grad student can probably get a paper out of it, which is a double win. > the drawbacks of microkernels are mostly at the pragmatic levels of actual performance, which academics mostly don't care about and don't get called on. You can excuse relative performance figures against something like Linux or FreeBSD by saying that your microkernel has not had the kind of optimization that those OSes have had, or that the performance loss is worth it for some benefit that microkernels are supposed to give you. > in academic computer science you do not have to actually prove any claims that your microkernel is more reliable, easier to write software for, or the like than traditional kernels. In fact it's not clear how you would prove such claims; productivity and reliability claims are notoriously hard to validate because there are so many variables involved.
- ww520 9y agoIs it possible to run it in VirtualBox to try it out? User space device drivers should significantly shorten the development time.
- chrisper 9y agoI just tried it out. It works in Virtualbox. Just use the amd64 ISO image.
- throwaway7645 9y agoAre python, C, and C++ the only supported langs?
- oldandtired 9y agoIf C is supported then so are a heap of other languages because they are implemented via a C compiler.
- throwaway7645 9y agoYes, but is it super straight forward to then implement say Python & Perl? Or does someone have to do a bunch of work?
- snvzz 9y ago>python Is already there. >perl There'd be porting effort, if not using their POSIX compatibility framework. Else, effort would be put in making it build.
- iomotoko 9y agoRegarding microkernels: [0] Minix 3: still around, great resource for learning, especially since there is a great book about it by Tanenbaum himself. Btw: it utilizes NetBSD's pkgsrc infrastructure, so quite a lot of applications should run [1] RedoxOS: effort to create a unix-like microkernel OS using the Rust programming language, pretty interesting. Hope it win gain some traction, the idea itself is neat [2] QNX: RIM/Blackberry's proprietary RTOS used in embedded systems (for example cars), also BlackberryOS is based on QNX [3] GNU/Hurd: not sure how much software runs on it, the "most usable" form is probably trying to run the Debian GNU/Hurd distribution [0] http://www.minix3.org/ http://www.minix3.org/ https://www.amazon.com/Operating-Systems-Implementation-Paperback-January/dp/B010TT8WIS https://www.amazon.com/Operating-Systems-Implementation-Pape... [1] https://www.redox-os.org/ https://www.redox-os.org/ [2] https://en.wikipedia.org/wiki/QNX https://en.wikipedia.org/wiki/QNX [3] https://en.wikipedia.org/wiki/Debian_GNU/Hurd https://en.wikipedia.org/wiki/Debian_GNU/Hurd (kind of keep track of various operating systems as a hobby, always interested what's out there for some reason)
- snvzz 9y agoLook into http://www.microkernel.info/ http://www.microkernel.info/ Note one of these doesn't belong (hurd), as unlike everything else, it is first gen and effectively dead.
- bogomipz 9y agoCan you say why it is effectively dead? I see a recent-ish release: http://www.gnu.org/software/hurd/news/2016-12-18-releases.html http://www.gnu.org/software/hurd/news/2016-12-18-releases.ht...
- throwaway7645 9y agoWithout knowing much, GNU Hurd has been in development for ages, yet is pretty far behind everything else out there in terms of usability. I think it is still active (remember a recent HN post), but it's progress is seen as being slow.
- 9y ago
- exikyut 9y agoSlightly OT, general microkernel question: Is it possible to viably do zero-copy message-passing? As in, the kernel lets you know you have a new message, but the message buffer is the same one the calling/sending process built. The main thing I wonder about is security. Maybe the memory manager could allow only the sending process to write to the memory region containing the message! Or maybe that would be really hard to get right. Once refcounting declares that only the sender has an active lock on the message, it could be deleted.
- snvzz 9y agoidk about HelenOS. On seL4, you may have a capability to a frame of physical memory in 2 processes, and use that as "shared memory" between them.
- rurban 9y agoSure see e.g pony-lang. Reference capabilities guarantee all three safeties, even with shared memory. You just aren't allowed to do much with it, depending on ownership.
- deleted 9y ago[deleted]