9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] /sys/include/ip.h 5c(1)
Date: Wed,  7 Oct 2009 08:59:28 +0100	[thread overview]
Message-ID: <27411a3a7e98126b126be12b7260da59@hamnavoe.com> (raw)
In-Reply-To: <200910062115.n96LFdYE020163@skeeve.com>

> Just like you wouldn't have wanted to redo the microcode
> in your Vax 11/750, even if you could have.

Speak for yourself.  I don't know about the VAX, but writing
microcode for the Perkin-Elmer 3220 was fun and useful as well.
It was nicely integerated into Unix, so different processes
could have their own bits of microcode swapped into the control
store when they were dispatched.  Real Programmers weren't
afraid of going down to the bare metal in those days.




  parent reply	other threads:[~2009-10-07  7:59 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<85b966411695929ce06c3edd6e3fd77f@plan9.bell-labs.com>
2009-10-06 16:21 ` erik quanstrom
2009-10-06 16:55   ` geoff
2009-10-06 17:21     ` ron minnich
2009-10-06 18:16       ` W B Hacker
2009-10-06 18:36         ` ron minnich
2009-10-06 18:50           ` W B Hacker
2009-10-06 19:13             ` Lyndon Nerenberg - VE6BBM/VE7TFX
2009-10-06 20:03               ` ron minnich
2009-10-06 20:58                 ` Wes Kussmaul
2009-10-06 21:15       ` Aharon Robbins
2009-10-06 21:32         ` ron minnich
2009-10-07 21:07           ` Aharon Robbins
2009-10-06 21:51         ` C H Forsyth
2009-10-07  0:19           ` Dave Eckhardt
2009-10-07  0:24             ` ron minnich
2009-10-07  1:59               ` W B Hacker
2009-10-08 16:04                 ` ron minnich
2009-10-07  7:59         ` Richard Miller [this message]
2009-10-08  7:35           ` Skip Tavakkolian
2009-10-08 10:44             ` Richard Miller
     [not found] <<4ACED151.8060901@conducive.org>
2009-10-09 15:12 ` erik quanstrom
2009-10-09 18:25   ` lucio
     [not found] <<a17983cabc815054d953faf2696761f2@vitanuova.com>
2009-10-08 22:42 ` erik quanstrom
2009-10-08 23:11   ` Steve Simon
     [not found] <<13426df10910080904l5dc8f3d0sc88ec19f28939a99@mail.gmail.com>
2009-10-08 16:17 ` erik quanstrom
2009-10-08 20:55   ` C H Forsyth
2009-10-09  4:00     ` lucio
2009-10-09  5:59       ` W B Hacker
     [not found] <<18f3fced1ebb90eb9c977b47bbcce424@vitanuova.com>
2009-10-06 22:16 ` erik quanstrom
     [not found] <<13426df10910061136w616f7cf9m2b566606663a9f50@mail.gmail.com>
2009-10-06 18:48 ` erik quanstrom
     [not found] <<13426df10910061021g3b033abbia134769baee934d3@mail.gmail.com>
2009-10-06 18:06 ` erik quanstrom
2009-10-06 18:16   ` ron minnich
     [not found] <<e7fdc0d20910050644x50fc7ad2hc943a075648fdabd@mail.gmail.com>
2009-10-05 13:50 ` erik quanstrom
2009-10-06  5:44   ` Rodriguez Faszanatas
2009-10-06 16:16     ` geoff
2009-10-06 17:18       ` Steve Simon
2009-10-07  6:24       ` Rodriguez Faszanatas
2009-10-10  1:23         ` Ethan Grammatikidis
     [not found] <<e7fdc0d20910050205l7bfaa624m33a32f7a5269ff9a@mail.gmail.com>
2009-10-05 13:16 ` erik quanstrom
2009-10-05 13:44   ` Rodriguez Faszanatas
2009-10-05  9:05 Rodriguez Faszanatas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=27411a3a7e98126b126be12b7260da59@hamnavoe.com \
    --to=9fans@hamnavoe.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).