6 ms·
A Pi-Powered Plan 9 Cluster
- kevintb 8y agoVery cool! Like the setup and I always like hearing more about Plan 9 projects.
- abhinai 8y agoI wonder if this post gave some seminal ideas to a new generation of OS or language builders! Really cool stuff.
- mruts 8y agoI’m not entirely convinced that were will be a new generation of OS researchers. This, of course, is unfortunate.
- pjmlp 8y agoPlenty of ideas available in mainframes and safe OS systems that are yet to become mainstream.
- FridgeSeal 8y agoFor those of us unaware of some of the intricacies and unusual/interesting features available in mainframe and other OS’s, could you provide some examples?
- pjmlp 8y agoBeing written in memory safe system programming languages to start with. Burroughs B5500, nowadays sold by Unysis as ClearPath. OS/400, nowadays known as IBM i. Using a database as file system, like OS/400 catalogs. Containers were invented on OS/360, improved on other IBM models, and still offer resource management features not yet mainstream.
- kristianp 8y agoReading this led me to wonder if Go is available on Arm Plan 9. There's a way to cross-compile it [1], it requires a shell script to simulate git [2] (which isn't available on Plan 9) using http calls to github! [1] https://github.com/golang/go/wiki/Plan9 https://github.com/golang/go/wiki/Plan9 [2] https://blog.gopheracademy.com/advent-2014/wrapping-git/ https://blog.gopheracademy.com/advent-2014/wrapping-git/
- ainar-g 8y agoIt is available. At least https://build.golang.org/ https://build.golang.org/ lists plan9/arm as one of builders. Interestingly enough, the source code build help page[1] doesn't list plan9/arm as a valid build target. EDIT: There is an open issue[2] about updating that page. [1] https://golang.org/doc/install/source https://golang.org/doc/install/source [2] https://github.com/golang/go/issues/28142 https://github.com/golang/go/issues/28142
- MisterTea 8y agoThere is a Go port but upstream changes keep breaking builds on 9 so it's been difficult. Same situation lead to Python being neglected though it's still included in 9front but stuck at version 2.5.1. Makes for a nice calculator repl though. Most of that stems from the use of the Plan 9 C library which is not ANSI but has many of the same functions. So to bridge the portability gap ANSI C/Unix/POSIX is via the APE (ANSI/POSIX Environment) library and the cpp preprocessor.
- rcarmo 8y agoI’d love to have read more about the cluster configuration, because it looks like the only machine that actually ran Plan9 was the one with the display... I’ve been lurking in the 9fans mailing-list for years and kept a Pi running Plan9 as a sort of 24/7 “home console” (to log in to other machines) for a long time, but I recently upgraded that to a 3B+ and Raspbian instead due to the lack of a good enough web browser, and having a cluster of my own (now running k3s), I would have liked to see a reference configuration of some sort. The Plan9/Inferno ecosystem has always been fascinating to me, but it’s so closed upon itself that it’s hard to, say, go out into GitHub (or equivalent) and find actively maintained tools (or even blog posts with updated info), and source archives seem to be maintained by fewer and fewer people...
- avhon1 8y agoWhy do you think that only one of the four raspberry pis is running Plan 9? My understanding is that, with Plan 9, you can run it on multiple networked computers, and mount CPU servers, RAM servers, and disk servers from other machines onto your terminal. They seem all set to do just that on this setup.
- rcarmo 8y agoIf you read through the text, it only mentions booting the one machine with Plan9. There is zero detail on the actual clustering part. Just like you outline, I would expect some mention of which machines in the cluster run cpu, auth, venti, etc., since splitting those was actually one of the primary design criteria for real clusters (there used to be a nice doc on the Plan9 wiki for that). Also, Richard’s image (and 9front’s) runs all services on the same node. To break those apart and run a cluster, you really need to reconfigure it, and there is no mention of that either.
- bigato 8y agoThe text is focused on the maker aspect of the project, and not on the software configuration for the cluster which can be found elsewhere. For that second part that you correctly found missing, you'd need to read a little bit more on documentation and other sources. It would be nice though, if he had some links for those interested in further research on the software part.
- Jansi 8y agoTest Comment
- snazz 8y agoPlease stop posting these test comments. You’re being downvoted because they add nothing to the discussion.
- hestefisk 8y agoThis is very cool. I love the simple windowing environment. It would be great to understand how he takes advantage of the clustered setup with only one workspace. How does he do networking etc.
- bibyte 8y agoI am slightly disappointed that they finished it just when the system booted up. Why not show off the power of the cluster ?
- newnewpdro 8y agoPresumably because they didn't actually do much more than get plan9 booting on a raspberry pi sharing an enclosure with other raspberry pis.
- rob74 8y ago"The project provided an excuse to make use of a Vortex Core 47-key keyboard, which together with a mini white HDMI monitor, provided a particularly compact and suitably futuristic feeling setup." I think the word he's looking for is "retrofuturistic" ;)
- rbanffy 8y agoIt's kind of alt-future. We invented something better than Unix. We just didn't want to use it that badly.
- mruts 8y agoAre we talking about Plan 9 or Lisp Machines?
- rbanffy 8y agoBoth fit the bill at different time references. Plan 9 is closer to what we would expect a modern computer would be, with network transparency built-in down to its very core. It's natural to spread your use across multiple machines from a single seat. Authentication, authorization and securing the channel against eavesdropping was not as big a concern then as it is now when every network should be treated as it's public and hostile. I'm not sure how a Lisp machine of Symbolics or LMI heritage or a Smalltalk system would deal with distributed functionality across untrusted networks. From the language PoV, it seems natural to Smalltalk.
- pjmlp 8y agoI surely wouldn't like my GPGPU at the end of a network socket, instead of shared memory IPC.
- rbanffy 8y agoIf the data resides on the same node as the GPGPU and you only do queries on it (as you would with a remote Jupyter or something like it) with little data being moved across the network, there is no reason its memory should be directly visible to the local CPU and little benefit if it is. The only thing is that your OS will have to do some cluster management to make sure data will be close to the programs using it.
- rbanffy 8y agoSomeone should eventually build a browser that runs tabs on multiple nodes of the cluster. Maybe Slack could release a client that does that, running each connection on a separate node.
- sambull 8y agoeh, slack should just die in a fire. If I could name the most hated tool in my organization that would be it. Just set that to crap DND check at 5:30pm.
- FridgeSeal 8y ago> Maybe Slack could release a client that does that, running each connection on a separate node. Why, so it can consume ram on even more machines at once? :P
- phoobahr 8y agothat's the joke.
- Koshkin 8y agoIt’s an old(ish) post (mostly showing how to build the enclosure), and the download link pointing at Bell Labs is dead. Plan9 has a new home at https://9p.io/plan9/ https://9p.io/plan9/.
- driusan 8y agoIf you stumble across a labs URL (like in the article), you can usually just replace "plan9.bell-labs.com" with "9p.io". For instance, the link to Miller's RPi build that was linked to should be updated to http://9p.io/sources/contrib/miller/9pi.img.gz http://9p.io/sources/contrib/miller/9pi.img.gz
- rbanffy 8y agoI wonder if one could run it on a ClusterHAT. https://shop.pimoroni.com/products/cluster-hat https://shop.pimoroni.com/products/cluster-hat