Plan 9 seems to be disproportionately influential for an OS nobody who's not into systems engineering has ever heard about.
Security in Plan 9 (2002)
31–40 of 74 posts
Re: Security in Plan 9 (2002)
#32Re: Security in Plan 9 (2002)
#33Re: Security in Plan 9 (2002)
#34Re: Security in Plan 9 (2002)
#35Earlier 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?
Re: Security in Plan 9 (2002)
#36Earlier 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
Re: Security in Plan 9 (2002)
#37Earlier 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'…
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)
#38Re: Security in Plan 9 (2002)
#39Re: Security in Plan 9 (2002)
#40The 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.