From: ggs@shiresoft.com (Guy Sotomayor)
Subject: [TUHS] [pups] Ancient Unixes
Date: Mon, 24 Apr 2006 14:00:27 -0700 [thread overview]
Message-ID: <1145912427.9595.28.camel@linux.site> (raw)
In-Reply-To: <20060424204843.2831915B@minnie.tuhs.org>
On Mon, 2006-04-24 at 16:44 -0500, Norman Wilson wrote:
> Bill Cunningham:
>
> I am copying all I can from the unix archive and will burn it to cd
> because I know how precious they are. But what I was thinking was v5,6,7 for
> example. Take them and add USB support. Linux would be a good example from
> which to draw from. Because it's Posix. Much more could be adde to /dev.
>
> =======
>
> Has anyone ever made a UNIBUS or Qbus USB card?
The problem isn't so much the hardware, it's the software. A USB stack
(OHCI/UHCI) isn't exactly small and I doubt you could create a driver
stack that would fit in a PDP-11's 16 bit address space (ie TCP/IP is a
stretch in that it only works on systems with 22-bit addressing and I'd
say that a USB stack is *at least* as complicated as a TCP/IP stack).
--
TTFN - Guy
next prev parent reply other threads:[~2006-04-24 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 21:44 [pups] [TUHS] " Norman Wilson
2006-04-24 21:00 ` Guy Sotomayor [this message]
2006-04-24 21:51 ` [TUHS] [pups] " Toby Thain
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=1145912427.9595.28.camel@linux.site \
--to=ggs@shiresoft.com \
/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).