From: brantley@coraid.com (Brantley Coile)
Subject: [TUHS] late research unix question
Date: Tue, 1 Dec 2009 20:11:46 -0500 [thread overview]
Message-ID: <D7D6CB7C-FCCE-4192-96B7-93E3097892BB@coraid.com> (raw)
In-Reply-To: <20091201.174857.1573374699.imp@bsdimp.com>
The protocol isn't the problem. All the binaries that get pushed over
it is the problem. The Jerq down loaded programs to run on the
terminal. That's why sam is in two parts.
Brantley
On Dec 1, 2009, at 7:48 PM, M. Warner Losh wrote:
> Would the bitblit protocol be easier to emulate that then whole
> machine?
>
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
_______________________________________________
TUHS mailing list
TUHS at minnie.tuhs.org
https://minnie.tuhs.org/mailman/listinfo/tuhs
next prev parent reply other threads:[~2009-12-02 1:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 0:30 Norman Wilson
2009-12-02 0:43 ` Al Kossow
2009-12-02 0:48 ` M. Warner Losh
2009-12-02 1:11 ` Brantley Coile [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-01 20:49 Tim Newsham
2009-12-01 22:06 ` Brantley Coile
2009-12-01 23:43 ` Tim Newsham
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=D7D6CB7C-FCCE-4192-96B7-93E3097892BB@coraid.com \
--to=brantley@coraid.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).