From: jacob.ritorto@gmail.com (Jacob Ritorto)
Subject: [TUHS] extend 2.11BSD window(1) to work with relatively enormous terminals
Date: Sat, 15 Nov 2014 15:29:53 -0500 [thread overview]
Message-ID: <CAHYQbfC8td3WAyUC2iYe8nNtZMgJbvtvtqzSGBMdZkNz0hzspQ@mail.gmail.com> (raw)
Hi all,
I've been using window(1) on my simh-emulated 11/73, but it can't handle
terminals much larger than 80x24, failing with "Out of memory."
I'd like to use window(1) to drive a big xterm, like 132x66, for
instance, because I'd like to reduce the number of telnet connections to
the host.
How does one go about analyzing and remediating the memory contention in
this environment?
If anyone's interested, we could set up a pair programming session to
work on it together, which I think would be most instructive, for me, at
least.
Bear in mind that this is just for pdp11 voyeurism / fun.
thx
jake
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20141115/bafae7e4/attachment.html>
reply other threads:[~2014-11-15 20:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAHYQbfC8td3WAyUC2iYe8nNtZMgJbvtvtqzSGBMdZkNz0hzspQ@mail.gmail.com \
--to=jacob.ritorto@gmail.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).