From: tim.newsham@gmail.com (Tim Newsham)
Subject: [TUHS] 8th Edition Research Unix on SIMH
Date: Wed, 26 Apr 2017 12:45:17 -1000 [thread overview]
Message-ID: <CAGSRWbiMYzGBCtksT7iK6CiFRU2A5O7dC0ZOSD9Tn+EOpHruJw@mail.gmail.com> (raw)
In-Reply-To: <20170330203031.065891fd@neon.9fans.fr>
Do you know who wrote the /sys/src/games/blit emulator?
There's a piece of code in it that I had to comment out that
I dont understand and I want to ask about it:
}
- write(3, rom, sizeof(rom));
+ /* I dont know what this was for, but it spews garbage
+ * out telnet to the vax, causing it to hang.
+ */
+ //write(3, rom, sizeof(rom));
}
I'm not sure what fd 3 is intended to be, but its the telnet socket in p9p.
On Thu, Mar 30, 2017 at 8:30 AM, David du Colombier <0intro at gmail.com>
wrote:
> This image is ready to be used with aiju's Blit emulator,
> which is available as part of 9front.
>
> http://code.9front.org/hg/plan9front/file/tip/sys/src/games/blit
>
> This emulator works on most Plan 9 distributions. You just
> have to copy the /sys/lib/blit and /sys/src/games/blit
> directories to your system.
>
> With the v8.ini startup file provided, the console will be
> listening on port 8888/tcp once SIMH has been started.
>
> You have to run the emulator and connect to the console:
>
> % cd /sys/src/games/blit
> % mk install
> % games/blit -t tcp!hostname!8888
>
> Once connected, enter your login and password.
>
> login: root
>
> Then, you can launch the mux window system:
>
> $ /usr/blit/bin/mux
>
> Once started, you can run any graphical program.
> Binaries are located in the /usr/blit/bin directory.
>
> For example, here is jim text editor:
>
> http://9legacy.org/img/v8/jim_01.png
>
> --
> David du Colombier
>
--
Tim Newsham | www.thenewsh.com/~newsham | @newshtwit | thenewsh.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170426/ed0ca9a1/attachment.html>
next prev parent reply other threads:[~2017-04-26 22:45 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 18:58 David du Colombier
2017-03-28 19:32 ` Cory Smelosky
2017-03-28 23:50 ` Tim Newsham
2017-04-25 3:16 ` Tim Newsham
2017-04-25 20:34 ` David du Colombier
2017-04-26 3:50 ` Cory Smelosky
2017-03-29 1:06 ` Henry Bent
2017-03-29 1:19 ` Cory Smelosky
2017-03-29 1:35 ` Henry Bent
2017-03-30 14:16 ` David du Colombier
2017-03-30 18:30 ` David du Colombier
2017-03-31 5:05 ` Michael Kerpan
2017-03-31 5:36 ` Kurt H Maier
2017-03-31 14:41 ` Michael Kerpan
2017-03-31 16:34 ` [TUHS] 8th Edition Research Unix on SIMHtuhs Cory Smelosky
2017-04-26 3:05 ` [TUHS] 8th Edition Research Unix on SIMH Tim Newsham
2017-04-26 5:53 ` Noel Hunt
2017-04-26 6:10 ` Tim Newsham
2017-04-26 23:49 ` Tim Newsham
2017-04-26 22:45 ` Tim Newsham [this message]
2017-04-26 23:02 ` Arthur Krewat
2017-04-26 23:21 ` Dave Horsfall
2017-04-26 23:07 ` Kurt H Maier
2017-03-29 0:49 Noel Chiappa
2017-03-29 1:02 ` Grant Taylor
2017-03-29 10:41 ` Steffen Nurpmeso
2017-03-29 2:44 ` Tim Newsham
2017-03-29 1:45 Noel Chiappa
2017-03-29 1:57 ` Steve Nickolas
2017-03-29 4:11 ` Grant Taylor
2017-03-30 11:47 Jason Stevens
2017-03-31 22:31 Nelson H. F. Beebe
2017-04-27 1:04 Norman Wilson
2017-04-27 1:26 ` Kurt H Maier
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=CAGSRWbiMYzGBCtksT7iK6CiFRU2A5O7dC0ZOSD9Tn+EOpHruJw@mail.gmail.com \
--to=tim.newsham@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).