mechazoidal + plan9   123

Git/fs: A native git implementation for Plan 9 | Lobsters
"Along with the plan 9 adaptation (git as a filesystem, of course), git starts to become a rather universal storage format for versioned code."
lobsters  discussion  piperesearch  pmz  git  plan9 
13 days ago by mechazoidal
Rethinking files
"Arguably, an operating system lives and dies by the quality of its nexuses. The quality of Unix's filesystem as an integration and maintenance nexus makes it a pleasing system to work with, and has doubtless earned it much favour.

How do we square this with the view that “everything is a file” is perhaps a mistake? First, let's observe what actual utility the “everything is a file” concept gave us. It seems clear that what it gave us was a common set of verbs with which to operate on files."
("Nexuses" was the previous article)

InPermutation@lobsters: "The piece at the bottom about array support is the other important half of PowerShell. It supports full reflection on objects, which means you never have to grovel around with awk or tr just to get the data out of a column of output. Arrays, hashtables, and objects are all built in to the language."
piperesearch  pmz  plan9  unix  powershell  multipart 
11 weeks ago by mechazoidal
I’m joining Cloudflare
Good news for Steve, etc.
Interesting notes:
- his description of FaaS/edge compute sounds hauntingly familiar like plan 9's CPU servers.
- JS can't be directly compiled to WebAssembly, it needs to go through a subset of TypeScript
webassembly  cloudflare  hosting  plan9  2019 
april 2019 by mechazoidal
oridb / git9 — Bitbucket
"Now, we have a native Plan 9 git implementation. It presents read only access to scripts via a file system mounted on /mnt/git, and manipulates the repository directly. The ability to access the repository directly from the shell using standard tools gives this implementation a very plan9-y feel.

There’s more care given to a consistent and minimalist interface that supports the necessary functionality, which will hopefully lead to a more pleasant user experience. Commands like checkout will not be overloaded with all functionality under the sun."
git  plan9  repo:bitbucket 
april 2019 by mechazoidal
Communication Files: Interprocess IO before Pipes (2017)
Noting that DTSS had a full file-*ish* IPC/comm interface way before plan 9(which gets a mention, noting that people copied the shallow parts but not the core idea)
He mentions dgsh but not CMS pipelines.
A note is that standard unix pipes don't have standardized ways of passing open IO connections outside of stdin/stdout(again, like CMS Pipelines?). Pipes and the pipe combinator were always linked on unix edict made them easier to learn.
paper  pdf  history  unix  plan9  pipes  ipc  piperesearch 
march 2019 by mechazoidal
Notes on the 3rd Edition Plan 9 Kernel Source
Note that the author encourages the reader to read the book via acme, so the included "source" are pointers to on-disk source files, in a real Plan9 system.
pdf  book  plan9  osdev  reference 
february 2019 by mechazoidal
Notes from a 1984 trip to Xerox PARC
Rob Pike remembers: note the usual Pike-isms towards anything not accommodating his minimal style, but also note some future seeds of ideas in Plan 9
history  xerox  plan9  computers 
january 2019 by mechazoidal
Dynamic Linking
"Given that degree of sharing, the low cost of RAM, and the increase in OS complexity, slowness and insecurity in the implementations of dynamic libraries that I've seen, I don't see a need for dynamic libraries. (Remember that the real impetus for adding them to Unix was X11 and its big and badly-factored libraries, which most of us aren't blessed with.)"
osdev  plan9  programming  unix  history 
january 2019 by mechazoidal
Jehanne Operating System - Simplicity awakes
Lots of good stuff: a rebuttal/analysis of the Unix/C "worse is better" approach, a note on how the various concurrent Unix system calls will trip each other up, how the Plan 9 design lessened but did not fully mitigate it, and how he's fixing it in the Jehanne P9 derivative. Also some notes from Italian artists on simplicity philosophy.
plan9  osdev  concurrency  2018  unix  pmz 
november 2018 by mechazoidal
dump.mntmn.com/interim-paper/
(repo: https://github.com/mntmn/interim )
"Interim is, as the name implies, an experiment of combining the homoiconicity of Lisp (manipulation of symbols), the genericity of Plan 9 (everything is a file system) with the minimalism and hackability of home computers. New languages like Rust [Rust2015], Unikernel systems like Mirage OS [Mirage2015] and hardware designs like lowRISC or the Novena laptop [Novena2015] show that it is absolutely possible to build simpler, more open and safer systems than we take for granted today."

facme: note the "list of 'buffers'" and "list of rectangular 'views'": "the same buffer can be interpreted in different ways: listen to an image, look at graphic structure of text, paint into an audio sample."
But of course contrast that with his view on emacs: it wouldn't need to exist if the OS provided the building blocks for integration.
"I argue that an operating system can be designed as a database of well-formed functions that each do one thing well. The functions can then be composed to form ad-hoc "applications". A requirement for this is that unlike in proprietary/closed/binary designs, all source code must be open and all functions reusable in new contexts. Interim OS includes functional building blocks for text display and editing, and an example development environment written in the Interim language:"
plan9  lisp  osdev  research  facme  pmz  2015 
september 2018 by mechazoidal
Integrated development window manager
Duplicating plan9's plumber with a 100-line shell script
plan9  unix  x11 
may 2018 by mechazoidal
Announcing duit: developer ui toolkit
From mjl! Uses devdraw! Could this be adapted anywhere else?
Golang  gui  library  plan9  facme 
april 2018 by mechazoidal
Expanding your Grid (Plan 9 wiki)
" Plan 9 was designed as a distributed system. After you install the distribution from the cd, you have a self-sufficient one machine system, a standalone terminal. We will consider this as "Level 0" - how do you proceed from here to a network of Plan 9 machines and provide Plan 9 services to other clients? "
plan9  piperesearch 
march 2018 by mechazoidal
Structural Regular Expressions
Showing how to implement in Perl with existing regex operators
perl  regex  plan9  presentation  transcript  sam  facme 
november 2017 by mechazoidal
Proceedings of the 6th International Workshop on Plan 9
highlights:
To Stream or Not To Stream (showing using Limbo channels)
A Bluetooth Protocol Stack for Plan 9
IX: A file protocol for NIX (another 9P streaming solution)
paper  pdf  9p  plan9  inferno  osdev  pmz 
august 2017 by mechazoidal
International Workshop on Plan 9
The last was the 8th, in 2013 apparently. Use <n>e.iwp9.org for the previous ones.
plan9  9p  reference 
august 2017 by mechazoidal
Every year at the Plan9 International Workshop, we tussle with how to improve ne... | Hacker News
"Every year at the Plan9 International Workshop, we tussle with how to improve networking performance, particularly for streaming. Every 9p request needs to be rec'd. There's no look ahead. This makes it particularly unsuitable for streaming, for instance. We have tried queued 9p responses, multiple 9p packets in the same tcp packet, extensions to the protocol. Nothing seems satisfactory enough to make it into the core."
plan9  9p  pmz  hn  comment 
august 2017 by mechazoidal
Plan 9 operating system for the Raspberry Pi – demonstration by Richard Miller
"Richard Miller's port of plan9 runs on every RaspberryPi (pi0 to pi3 - where it uses all the cores). This may be the easiest way to experience plan9 and to build a small distributed system. You can experiment with device drivers or do other kernel hacking fairly quickly -- compiling p9 kernel from scratch takes about a minute on a 'Pi. This is good enough if you just want to play with plan9. You need not bother with an x86 system unless you want to use plan9 as your main system or for some serious work."

https://9p.io/sources/contrib/miller/9pi.img.gz
plan9  raspberry_pi  osdev  pmz 
august 2017 by mechazoidal
Using aescbc to store factotum keys
"secstore(1) is traditionally used to store private keys for factotum(4). When an auth server is not used, such as on a stand-alone terminal, a different solution must be found."
pmz  plan9  security 
august 2017 by mechazoidal
Pegasus — another web server for Plan 9 —
"Pegasus is another httpd in Plan 9 world. Pegasus is designed to be a secure and flexible httpd that is based on the novel feature of Plan 9. This paper shows how “per process namespace configuration” can be applied to httpd and shows how the users get benefit from the ability."
paper  web  programming  security  plan9  pdf 
july 2017 by mechazoidal
lojikil comments on: Who Needs Git When You Got ZFS? | lobsters
"coming from a OpenVMS background, I never really saw the point of having a separate tool to give you what the file system already does. I can imagine that this is similar to how the Golang folks want to avoid git too… a good portion of them have Plan9 experience, and we had Venti & Fossil on Plan9, so why have a separate tool? Deliver a vac of FS state as clones, just like we did on Inferno :D"
plan9  inferno  comment  lobsters  piperesearch  pmz  vcs 
june 2017 by mechazoidal
Two Enhancements for Native Inferno
"Here I report on recent work done in the process of moving native Inferno to a tablet PC. One part of the work was the porting of Francisco J. Ballesteros’s new Plan9 USB support to Inferno. The other was a VGA driver that operates with the 640x480x4 mode common to all VGA controllers."
(Ballesteros's support is detailed in "Plan 9’s Universal Serial Bus" paper)
pdf  inferno  graphics  usb  paper  plan9 
june 2017 by mechazoidal
LP49: Embedded system OS based on L4 and Plan 9
while LP49 is effectively defunct these days, this is the original paper on the reasons behind it
plan9  embedded  osdev  pdf  lp49  l4  pmz  paper 
may 2017 by mechazoidal
[9fans] find(1) revisited.
source for two plan9 programs/scripts, 'walk', and 'sor'(stream OR) that can be combined to duplicate find(1) in a much better way. usage: http://marc.info/?l=9fans&m=111558860617241&w=2
plan9  unix  tools  cli  filesystems 
may 2017 by mechazoidal
[9front] Installing firmware for wifi on X220 : plan9
note the comment about putting too much stuff in /lib/firmware can bloat the kernel
plan9  tips  wifi  discussion  reddit 
may 2017 by mechazoidal
One night in Rio – Vacation photos from Plan9 | Arcan
"From this, the prio project has been added to the Arcan family. I wanted this experiment to exhibit three key features, that I’ll cover in more detail:
- User-defined-confined spaces
- Hierarchical connection structure
- Modularity through user-designated roles
"
also note comment on lobsters: "The beauty of the plan9 approach is that it doesn’t cost any extra server-side resources other than what has already been reserved for the parent terminal, and subsequently, you don’t have another client doing things in a hidden window somewhere. It also chains nicely. The downside, as Rob himself admits, being that it was ultimately too simple."
piperesearch  x11  plan9  arcan 
april 2017 by mechazoidal
GitHub - troglobit/editline: A readline() alternative for UNIX without ncurses!
A readline-compatible line editing library, very small. Originally designed for older Unix and Plan 9 (so it might be useful to port this to Inferno)
plan9  readline  library  cli  repo:github 
february 2017 by mechazoidal
GitHub - elewarr/plan9-bcm: Plan 9 BCM
this appears to be a minimal Plan 9 kernel for the Broadcom BCM / Raspberry Pi ?
repo:github  plan9  raspberry_pi  programming  pmz 
february 2017 by mechazoidal
plan9-from-bell-labs / 9-cc - Bitbucket
"Highly portable C compiler suite, including supporting tools, originally developed for Plan 9 from Bell Labs and later also used for Inferno. It targets x86, amd64, SPARC, MIPS, ARM, and PowerPC. ARM64 will shortly be added. [...] The source code of the compiler suite is included in both Plan 9 and Inferno distributions, but this provides an independent source that might be used by other projects."
(Note that this is Forsyth's updated repo of kencc, Ken Thompson's original Unix port of the Plan9 original: http://gsoc.cat-v.org/projects/kencc/ )
plan9  compilers  c  programming  repo:github  inferno 
february 2017 by mechazoidal
Re: [9fans] 3D graphics as a filesystem
"Yeah I prototyped draw3d with 9vx driver to host GPU on Linux system.
MesajGL if 9p file exists it supports mode of that name to transfer to gpu.
It helps if you have DooM handy to try writing it in rc."
! Does this exist anywhere?
plan9  3d  graphics  comment 
january 2017 by mechazoidal
Re: [9fans] NEC building Raspberry Pi 3s into its displays
"I use a Fujitsu thin client as [Plan 9] terminal. These (and other vendors) can be bought on ebay extremly cheaply (half the price of a PI or cheaper), have nice case, Gigabit ethernet, enough USB ports, decent cpu power, replaceable and upgradable ram and a PCI slot."
(Do note that Re-PC in Seattle usually has deals on thin-client boxes as well!)
hardware  comment  plan9  2016 
january 2017 by mechazoidal
sirnewton01/rpi-9front : November 2016 (Elros) RC4
"This release includes an interactive [Acme] tutorial that appears on startup"
raspberry_pi  9front  plan9  repo:github  pmz 
january 2017 by mechazoidal
[9fans] Plan 9 on L4 - Google Groups
Interesting thread on the lp49 port, along with other notes on plan 9 internals
plan9  osdev  discussion 
january 2017 by mechazoidal
Plan 9’s Universal Serial Bus
"This paper describes the system software used on Plan 9 to drive the bus and its devices. How to use the software is not described here, but in the Plan 9 users manual."
usb  inferno  plan9  paper  pdf  osdev  reference 
january 2017 by mechazoidal
Rob Pike on Twitter:
"In Plan 9, it's not "everything is a file", it's "everything has the same interface". And that interface is "file *system*". Very different."
tweet  plan9  reference  osdev 
january 2017 by mechazoidal
Getting started with Inferno
"This document intends to help getting started with Inferno." still updated as of 2016, covers operational stuff not covered in the official papers or books
inferno  plan9  reference  pmz 
january 2017 by mechazoidal
Jehanne
Another fork of Plan 9, this time adopting the Plan9-9k kernel, shrinking and making the base install more modular, and stealing the rest from 9front(with their permission)
plan9  os  osdev  programming 
january 2017 by mechazoidal
forsyth / plan9-9k - Bitbucket
Charles Forsyth: "Source for an experimental 64-bit Plan 9 kernel, and supporting software. It features a revised memory-management system, MCS spin locks, and other changes to system data structures to support full 64-bit addressing. Changes to the scheduler are also planned, to improve support for multicore."
plan9  kernel  osdev  programming  repo:bitbucket 
january 2017 by mechazoidal
Acid your ARM - Lsub
"We have developed jtagfs, a protocol stack and filesystem which enables live debugging of an ARM machine using acid." They use the MPSSE on the Sheevaplug to interact with TAP, but note that this should work on any ARM with Embedded-ICE.
Interesting points:
- "Assembling on the fly has proved to be a very good approach for debugging and testing, providing a low level sniffing interface. "
- "Just by writing some acid code, we were able to to disable and reenable the watchdog as needed."
- "Another interesting experience was debugging some code for traps that had failed to work for a long time and we did not understand why. It turned out that in the end we were using an instruction which was not supported in the machine, but what had stalled us for days was debugged in a couple of hours using jtagfs."
plan9  arm  hardware  pdf  inferno  jtag 
december 2016 by mechazoidal
Inferno for the Sheevaplug
Details on Mechiel Lukkien's port of Inferno to the Marvell-powered Sheevaplug, using work from Salva Peiró (DS port)
pdf  paper  inferno  plan9  embedded  hardware  osdev 
december 2016 by mechazoidal
Maintaining Files on Plan 9 with Mk
∙ Make builds targets when it needs them, allowing systematic use of side effects. Mk constructs the entire dependency graph before building any target.
∙ Make supports suffix rules and % metarules. Mk supports % and regular expression metarules. (Older versions of make support only suffix rules.)
∙ Make supports cyclic dependencies, mk does not.
∙ Make uses special targets (beginning with a period) to indicate special processing. Mk uses attributes to modify rule evaluation.
∙ Mk supports virtual targets that are independent of the file system.
∙ Mk allows non-standard out-of-date determination, make does not.
plan9  mk  make  buildsystem 
december 2016 by mechazoidal
David Hoskin / 9webdraw
"a Web draw(3) server for Plan 9, using the HTML5 <canvas> element."
plan9  9p  websockets  html5  webdev  repo:bitbucket 
december 2016 by mechazoidal
C Programming in Plan 9 from Bell Labs
"Learning programming with Plan 9 is not something that requires complicated textbooks and four years of college study to master. In fact, with just the manual pages and pages of some documentation in hand, someone can quickly master the core concepts. However, there sometimes is a need of a starter’s guide or tutorial to start with or to clear up some uncertainty. That task is what this paper aims to do."
c  programming  plan9  reference  paper 
december 2016 by mechazoidal
Turning off syntax highlighting | Lobsters
"Acme users (all 10 of us) write their own commands when they need them. I don’t know of any collection of commands, sorry, what would be the point? Every environment is different. The philosophy behind acme (plus plumber) is that it’s an integrating environment of arbitrary Unix software (I’m counting Plan 9 as a Unix here), not an integrated environment. It makes it really easy to integrate any reasonably written Unix tool into your workflow, but it doesn’t really provide any such built-in integration by default. You don’t need any collection of commands to use start using acme though. Usually on every new project I start with a blank environment. I add stuff to it only as needs become apparent."
comment  lobsters  piperesearch  acme  unix  editor  plan9 
november 2016 by mechazoidal
The Mouse Trap: This Old Vulnerability #1: Plan 9 devenv Integer Overflow
"Because Plan 9's security model is integrated into the kernel, and there is no way to elevate privileges from one user to another via the normal security constructs we're used to in Linux/etc, an attack must take on one of two forms:
- We must know the cryptographic key(s) of our target user
- We must attack the kernel to subvert its security model"
plan9  security  exploit 
october 2016 by mechazoidal
"Yes, documents, as envisioned in the ‘90s are dead."
"But I would want a data-oriented workflow, rather than an application-centric universes, where each application manages its own opaque data silo, or manages some data stored somewhere unknown in the ...
lobsters  comment  plan9  piperesearch  distributed  from notes
october 2016 by mechazoidal
OSHUG 46 — The Name Game, feat. Plan 9 & Inferno, Dr Charles Forsyth
mostly a general overview of Plan9/inferno basics, and outline of some of the papers he's written.
Misc notes:
- 20:58: note the description of "to jail a process, simply give it a namespace that doesn't have anything you don't want it to", much like Io or Lua.
- at some point he notes that Limbo is similar to the pi-calculus?
- 36:00: how they made a grid scheduler with just 3 people collaborating through the namespace and file system
End: "minimalist, composed, inspiring, bigger on the outside"
piperesearch  inferno  osdev  distributed  plan9  video:youtube  pmz 
october 2016 by mechazoidal
jvburnes/node9 · GitHub
"a hosted 64-bit operating system based on Bell Lab's Inferno OS that uses the Lua scripting language instead of Limbo and the LuaJIT high-peformance virtual machine instead of the Dis virtual machine. It also uses the libuv I/O library to maintain maximum portability, efficient event processing and thread management on POSIX and Windows platforms."
plan9  lua  osdev  os  piperesearch  repo:github 
september 2016 by mechazoidal
arg.h - A suckless alternative to getopt() | Lobsters
"It should be mentioned that this is a re-implementation of the Plan 9 argument parsing interface with some minor extensions."
programming  c  plan9  unix  lobsters  pmz 
september 2016 by mechazoidal
deadpixi/sam
"The version presented here is based on the original (?) port to X from 1989 and has no requirements other than Xlib and freetype, both of which are universally available on modern Linux, BSD, Unix, and Unix-like systems that use X. If you want to run sam without installing a bunch of other stuff, this might be what you're looking for."
(from http://www.deadpixi.com/an-updated-version-of-sam )
sam  plan9  editor  unix  repo:github 
august 2016 by mechazoidal
Using plumbing (Plan 9 wiki)
PR: note how remote resources are imported into a plumber instance
plan9  reference  piperesearch 
june 2016 by mechazoidal
Unix Software from Plan 9
"These are ports of Plan 9's UTF-8, formatted print, buffered I/O, and regular expression libraries, along with mk, a simple replacement for make."
unix  plan9  libraries  software  programming 
february 2016 by mechazoidal
Why Plan 9 is not dead yet, and what we can learn from it
A 2005 presentation illustrating how Unix lost its "simple" device/data model, and Plan 9's key idea: the kernel is a "server multiplexer", and devices in-operation look just like servers to programs. Also with some handy diagrams!
plan9  osdev  pdf  presentation  unix  history  piperesearch 
february 2016 by mechazoidal
The Text Editor sam
" There is one technical reason, though: programmability in editors is largely a workaround for insufficient interactivity. Programmable editors are used to make particular, usually short-term, things easy to do, such as by providing shorthands for common actions. If things are generally easy to do in the first place, shorthands are not as helpful."
plan9  editors  programming  paper  unix  piperesearch 
january 2016 by mechazoidal
Go: More UNIX than UNIX - iRi
" Correctly, Go does not ship with a "file" interface and force everything into it, regardless of how appropriate it is... instead, it ships with a number of interfaces that describe the elements of what a file may do, and lets you easily compose them as appropriate. [...] Which makes Go more Unix than Unix and more Plan 9 than Plan 9"
golang  piperesearch  pmz  unix  plan9  interface  programming 
january 2016 by mechazoidal
Notes on "Plan 9 from Bell Labs" by Rob Pike et al.
looks like this might be old --refers to 8 1/2 instead of rio , no mention of venti(just WORM drives), etc. But general concepts are summarized. Note the similarity to Hintjen's ZMQ comments:
"- Data is communicated mostly as text
- If binary format is necessary, use byte stream with a predefined encoding
- If complex format with data structure, marshall it"
plan9  notes  history 
december 2015 by mechazoidal
9Front.org | the plan fell off
the "actively maintained" plan9 fork, incorporating dryer-than-dead humor.
plan9  os  software 
december 2015 by mechazoidal
9atom
"augments the plan 9 distribution with the addition of a 386 PAE kernel, an amd64 cpu and terminal kernel, nupas, extra pc hardware support, IL and Ken's fs."
The more "vanilla, yet updated" fork of p9? 9front filches patches from them occasionally
plan9  os  software  osdev 
december 2015 by mechazoidal
string interfaces
"One may object that that string parsing is complicated, or difficult, or insecure. Addressing the last issue, there can only be a security concern when the string and the parser originate at different privilege/trust levels. Especially with static strings compiled into a program, this is often not the case. "

@bct: "In other languages this problem is solved with keyword arguments and optional arguments with default values. [...] (Second thought, why isn’t taking a struct as an argument an option?)"
( https://lobste.rs/s/9nlywd/string_interfaces/comments/ihpfnr#c_ihpfnr )
openbsd  api  design  piperesearch  plan9 
october 2015 by mechazoidal
Plan 9 vs. Mach IPC
"The NextBSD slides praise Mach IPC as facilitating separate service namespaces that isn’t a file system, as if that’s a huge disadvantage. Using Plan 9 and Inferno has taught me that 9P with per-...
bsd  unix  plan9  osdev  from notes
august 2015 by mechazoidal
The Ubiquitous File Server in Plan 9 by C H Forsyth
a good overall summary of Plan 9, along with its Big Ideas: "Plan 9’s defining novelty, however, remains its representation of resources in a distributed system."
pmz  piperesearch  plan9  9p  paper  network  osdev 
august 2015 by mechazoidal
LP49
"A modularized federated OS based on L4 micro kernel and Plan9 from Bell Labs." Noted from Genode mailing list that it is a research experiment that ported the Plan9 userland to run on top of an L4 kernel.
http://doc.cat-v.org/plan_9/IWP9/2006/lp49_iwp9.pdf
osdev  plan9  l4  research  dead_link 
august 2015 by mechazoidal
Bell Labs and CSP Threads
"This page is a slice of the history of concurrent programming, focusing on one particular lineage of Hoare's language of communicating sequential processes (CSP)"
Starts with Hoare, mentions the direct evolution of Spin/Promela. Covers the plan9/inferno languages, notes how the lessons were applied to libthread and Go, and also mentions Concurrent ML.
history  plan9  threads  programming  csp  piperesearch  concurrent_ml 
august 2015 by mechazoidal
Commands and channels in Clive: Sam is gone.
PR: note their "conventions" that skip some of Sam's one-use commands, in favor of using the pipeline and 9p(ish) at all levels. Note that the conventions expect their "modified" Go channels as described elsewhere. Also note how much this seems to be unconsciously mimicking CMS Pipelines.
golang  piperesearch  programming  plan9  osdev 
july 2015 by mechazoidal
The Clive Operating System
PR: note how they modified Plan9's basic ideas for their work(esp. file trees and their 9p-ish stuff). In particular, they take Go's channel abstraction and provide forward-error-propagation, instead of simply dying.
paper  pdf  os  osdev  plan9  piperesearch 
july 2015 by mechazoidal
Clive’s ZX file systems and name spaces
PR: note the "Name spaces" section, where they introduce a simple language(styled after find(1)) called "pred": the usage they describe is reminiscent of what Verse was trying to do with the multiple mode subscription system.
programming  paper  pdf  plan9  osdev  filesystems  piperesearch 
july 2015 by mechazoidal
« earlier      
per page:    204080120160

related tags

3d  9front  9p  acme  advocacy  api  arcan  archive_it  arm  assembly  aws  book  bsd  buildsystem  c  class  cli  cloudflare  code  codegen  comment  compilers  computers  concurrency  concurrent_ml  csp  culture  dead_link  design  dht  discussion  distributed  drivers  dsec  editor  editors  email  embedded  exploit  facme  filesystems  framework  gear  git  github  golang  graphics  gui  hardware  history  hn  hosting  howto  html5  inferno  inspiration  interface  interview  ipc  jit  jtag  kernel  l4  libraries  library  lisp  lobsters  lp49  lua  make  metadata  mk  mobile  mouse  multipart  network  networking  notes  openbsd  os  osdev  paper  pdf  perl  piperesearch  pipes  plan9  pmz  post  powershell  presentation  programming  protocol  python  raspberry_pi  readline  reddit  reference  regex  repo:bitbucket  repo:github  repo:googlecode  research  resource  review  rfc  sam  security  slides  smalltalk  software  specification  standard  threads  tips  tools  transcript  tweet  ui  unix  usb  ux  vcs  video  video:youtube  virtualization  web  webassembly  webdev  websockets  wifi  x11  xerox  zmq 

Copy this bookmark:



description:


tags: