Live data from Hacker News

Security in Plan 9 (2002)

9p.io

31–40 of 74 posts

Re: Security in Plan 9 (2002)

#31
post #16

Plan 9 seems to be disproportionately influential for an OS nobody who's not into systems engineering has ever heard about.

It's a similar story with the Self programming language (https://en.wikipedia.org/wiki/Self_(programming_language). There are many software engineers and computer scientists who never heard of Self, but Self's prototype-based approach to object-oriented programming had a major influence on JavaScript, and a lot of the work done on making fast virtual machines for Self made it in the Java Virtual Machine.

Re: Security in Plan 9 (2002)

#35
post #28

Earlier quoted context omitted.

and /proc Unfortunately, kids these days seem to be afraid of files. For a hardcore unix fan, curl and wget are useless tools when you can just cat /www/url

It's seems nice on a first glance. But how do you set headers and content type for example?

You echo the request into /www/url and cat the response from it

Re: Security in Plan 9 (2002)

#36

Earlier quoted context omitted.

to be fair, it's where UTF-8 debuted

and /proc Unfortunately, kids these days seem to be afraid of files. For a hardcore unix fan, curl and wget are useless tools when you can just cat /www/url

/proc predates plan9, plan9 just made it hierarchical

https://en.wikipedia.org/wiki/Procfs#History

Re: Security in Plan 9 (2002)

#37
post #30
post #19

Earlier quoted context omitted.

virtfs USES 9p.

I think GP meant to say (the extremely confusingly named) virtio-fs, as opposed to virtfs/9pvirtio. Virtio-fs is independent of 9P and has optional support for using shared memory to greatly increase performance, it also maps better to the permissions and metadata of "modern" filesystems IIRC, not sure if 9pvirtio had this problem but I remember coworkers having permissions problems with the 9P bridge in WSL2 (Plan9'…

> Plan9's permission system is very simple and doesn't map well to other VFS's

Plan 9 is a pure VFS OS. 9p uses regular unix permissions which map just fine. The major issue is that since plan 9 is all vfs, there are no crufty unix leftovers like hidden dot files or hard/soft links. User specific configuration files belong in $user/lib and bind replaces hacky links. These old unix hacks were accommodated in 9p2000.u. Further extensions to .u resulted in 9p2000.L which adds some Linux metadata stuff (I cant remember right now, my memory of 9p2000.u/L is fading).

Re: Security in Plan 9 (2002)

#38
post #25

Earlier quoted context omitted.

Already done. https://orib.dev/9hack1.html

Still WIP. We're not yet at a million useful procs.

Ah, by "Already done" I was referring to to the fact that your blog post exists and addresses the performance issues :-)

Re: Security in Plan 9 (2002)

#40
post #13

The 9p filesystem lives on in a few "modern" places, like within WSL, QEMU, and other places where it's a good bridge between a host OS and container or VM.

Unfortunately it's not implemented for Windows hosts. There's a patch in the works but the review of the first submission came back with a lot of requested changes. They're planning another submission though so hopefully it makes it in.
Post reply on HN