by moody__ on 7/27/24, 11:52 PM with 85 comments
by jazzyjackson on 7/28/24, 4:32 AM
Plan 9’s filesystem is a very simple network filesystem protocol to share files between systems. They are specifically using 9P2000.L.
They considered using Samba and SMB instead but can’t rely on Samba being installed and usable in the Linux guest OS and didn’t want to ship it because Samba is GPL licensed.
They picked Plan 9 because it’s much simpler to implement. Also Microsoft already had Plan 9 server code for some other Linux container project they’d done.
The \\wsl$\ path is handled in the Windows system by the MUP, an existing hook for network-like filesystems. They added a new one for Plan 9.
The $ is in the name so that it can’t be confused with a computer whose hostname is wsl.
The Plan 9 server in Linux communicates with the Windows Plan 9 client via a Unix socket. (Windows supports Unix sockets; who knew?)
Windows can access your Linux files even if no Linux is instance is running. There’s a new Windows service called LXSManagerUser that mediates user identity and permissions.
by rcarmo on 7/28/24, 8:06 AM
One of the “stupid” ideas I have in my back-burner is to rewrite rio so that it works like Mac OS 7 (the platinum look with window shading), which in my mind was always a very sane and efficient way to manage windows — but time is not on my side…
I have one of my usual lists of resources for it on https://taoofmac.com/space/os/plan9 - comment here if it’s missing anything you particularly like.
by kccqzy on 7/28/24, 1:57 AM
This is IMO the biggest drawback. Why wouldn't any user want the software to be feature rich? In fact, looking at Plan 9, I often feel that the provided software is just a MVP.
by readmemyrights on 7/28/24, 12:01 PM
To talk about the article itself, the only reason plan 9 can achieve such a design is because it's developed and used by the same small group of people. If linux is a bazaar and BSDs are cathedrals, then 9front is a monastery's citadel. Another thing that isn't mentioned is that both linux and BSD (and pretty much anything based on posix) has a lot of third party software that would be hard to maintain along with the rest of the system, if the monks even include it to begin with. And that software could include something like jq which a lot of software depends on and would love to just assume it's there.
And really, what more does someone get from something like this over, say, having a more or less formal standard on what a true plan9 system includes and waving it in someone's face when they choose to ignore it? This is pretty much what modern unices do and it works out great in cases when it's actually important. Most people don't care what commit your system is built from as long as it works as their programs expect it to.
by GianFabien on 7/28/24, 12:58 AM
by tylerchilds on 7/28/24, 1:02 AM
https://web.archive.org/web/20240728004832/https://posixcafe...
by zokier on 7/28/24, 6:26 AM
> Put in another way, if someone wanted the ability to touch every line of code (in the upstream sense), they would have to be a member of some non trivial amount of communities.
On a typical distro you can just download sources and start hacking, you don't need to be member of any community.
While something like Debian might not be monorepo in the strictest sense, on a conceptual level it is very close. They still have all the sources under their control and are not dependent on anything outside. They are at full liberty to accept or reject any patches regardless of where they come from, from "upstream" or "downstream".
This idea that distros are actually independent full-featured operating systems is an idea that I think is getting forgotten way too often. Distros are (or rather can be) much more than mere repackaging of upstream software.
by tbrownaw on 7/28/24, 3:45 AM
by teleforce on 7/28/24, 9:48 AM
[1] Systems Software Research is Irrelevant (2000) [PDF]:
by lagniappe on 7/28/24, 2:30 AM
by pjmlp on 7/28/24, 6:00 AM
I always have the impression the discussion stops on a gas station the middle of the road, instead of on the destination.
by nopoolontheroof on 7/28/24, 12:21 PM
by revskill on 7/28/24, 9:05 AM
by pxmpxm on 7/28/24, 2:20 AM