Відео

The presentation program is phil9's spit: shithub.us/phil9/spit/HEAD/info.html For the actual video recording it's a bit of smoke and mirrors, this is actually recorded via OBS using a full drawterm session. It's possible to make proper recordings now with the work sigrid has done, but considering drawterm is what I live out of most of the time anyway this ends up being easier for me.

The font used here is classic VGA. Sometimes also called "DOS VGA" or "IBM VGA".

The best way to get started with the system is to just try using it and experimenting. Once you feel more comfortable with using the system I would suggest trying to dig in to some of the code for programs. There really isn't a great all-in-one book I would suggest, but many of the papers in /sys/doc go into more of the narrative of the design considerations.

I think Go has helped people discover Plan 9 but I don't believe having go available on Plan 9 has changed the ecosystem much. I also wouldn't quite call it a continuous commitment really, I would say the Plan 9 support in Go is more on life support, with a lot of testing there being mostly an after thought. Things break subtly and sometimes will stay like that for multiple versions of go. A couple years ago they even had a proposal to remove Plan 9 support altogether. I am very thankful to the folks that do fix the bugs as they are discovered, but the code in general still needs exercised a lot more.

Thank you. These slides are made in Plan 9 using a program called spit.

I guess it depends on which portion of the topics covered were unclear to you. A lot of this talk is designed to contrast against conventional UNIX and Linux designs to build upon the familiar to showcase how Plan 9 differentiates itself. There are plenty of materials that go in to depth on the UNIX side of things but not many books that I would recommend that I feel cover Plan 9 design sensibilities. There are a nice collection of papers however that go in to some more narrative of the design, but those typically assume some background information with UNIX as well. I can also provide some further clarification here in the comments myself if you have specific questions.

Not exactly the book to follow together with these great videos, but I think "Introduction to OS Abstractions Using Plan 9 from Bell Labs" is a good one.

This will be covered soon. I likely want to lay the ground work for what a namespace is first, discussing the none user is its own can of worms that is properly best discussed within the context of 9p authentication.

@kittyfangz5262 thanks

I imagine if one can build a recent Go then one probably can piggy back on a Go package manager for some tasks (limited to one language, but still), but I don't know if 9front people use Go that way

The software ecosystem is not generally large enough right now to warrant this type of solution. For even the most involved of external software (netsurf and treason) at worst you have some script that builds a handful of projects. Part of this is as you mention the static compilation nature of Plan 9, but the other is just that for the most part we write a lot of our own software and the base system has quite a lot. 9front generally about as "batteries included" as openBSD is, if not a bit more. I would say that we're right on the cusp of needing something a bit more sophisticated. There was an attempt at some point in time to have a ports tree (akin to pkgssrc in netbsd or ports tree in freebsd) however it has generally bitrotted simply due to the lack of use of its programs, so I would say that serves as some evidence that we're not quite there yet. It's interesting that you mention Nix, because there is an aspect to that more then just the package management itself. That being the nixos modules that allow nix to define an entire linux "deployment" with just nix. If you are careful you can use something like /cfg/$sysname , but it's not quite all in one as nix is. I've been interested in exploring what it would look like to do something more with this for 9front.