From: jsteve@superglobalmegacorp.com (Jason Stevens)
Subject: [TUHS] C-news is built
Date: Sat, 11 Mar 2017 12:57:57 +0800 [thread overview]
Message-ID: <DAFBD8E8-4BD1-451A-8B58-397DC1FC1E0A@superglobalmegacorp.com> (raw)
In-Reply-To: <CAH1jEzaFjN91CfgG1w10k2RO1hTZNSqpf6VcrDoRO-ZoG5xT4A@mail.gmail.com>
This is what I've been using for years...
http://gunkies.org/wiki/Mkdisttap.pl
I've been keeping interesting source code tapes here:
https://sourceforge.net/projects/bsd42/files/Package%20Tapes/Source%20Code/
And various binaries I've built under simh:
4.2
https://sourceforge.net/projects/bsd42/files/Package%20Tapes/4.2%20BSD/
4.3
https://sourceforge.net/projects/bsd42/files/Package%20Tapes/4.3%20BSD/
4.3 UWisc
https://sourceforge.net/projects/bsd42/files/Package%20Tapes/4.3%20BSD%20Uwisc/
On March 11, 2017 5:14:12 AM GMT+08:00, Nick Downing <downing.nick at gmail.com> wrote:
>To get files into a 4.3BSD SIMH system the easiest way is with a Python
>script that blockifies the file by outputting a 32 bits length (say
>0x400), then that many bytes, then the length again, and repeat for
>next
>block until done. There is also a Perl version floating around which is
>popular for canned SIMH scripts/packages. Then you mount this file on
>tm0 (if I recall) in SIMH and then in the emulated system it appears at
>/dev/mt0. I normally use tar in conjunction but it's not necessary
>(note
>star is a highly compatible tar implementation, I think it is by Joerg
>from this list, although I use actual 4.3BSD tar compiled for Linux and
>I think gnu tar also works mostly). I can send the details later, I am
>using phone atm.
>Nick
>
>On Mar 11, 2017 4:52 AM, "John Floren" < john at jfloren.net
><mailto:john at jfloren.net> > wrote:
>
>
>Thanks Warren and Geoff,
>
>Two problems:
>
>1. 403 forbidden on that tarball
>
>2. What's the best way to get these files into a running 4.3 system?
>
>Thanks!
>
>John
>
>On Fri, Mar 10, 2017 at 2:49 AM, Warren Toomey < wkt at tuhs.org
><mailto:wkt at tuhs.org> > wrote:
>> OK, Geoff Collyer has built the C-News binaries for the 4.2 emulated
>> systems. They are temporarily at http://minnie.tuhs.org/Y5/
><http://minnie.tuhs.org/Y5/Cnews/> Cnews/
>>
>> Does someone want to try and get them up and running on an emulated
>system?
>>
>> Also, I've build a 4.3BSD version of the emulated uucp systems. It's
>a
>> separate branch at https://github.com/DoctorWkt/
><https://github.com/DoctorWkt/4bsd-uucp> 4bsd-uucp. You can get it
>> by doing:
>>
>> git clone https://github.com/DoctorWkt/
><https://github.com/DoctorWkt/4bsd-uucp.git> 4bsd-uucp.git \
>> --branch 4.3BSD --single-branch
>>
>> Once it's solid enough I will make this the default branch, but I'll
>> leave the 4.2BSD branch there as well.
>>
>> Thanks Geoff!
>> Warren
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170311/fd23dbe4/attachment-0003.html>
next prev parent reply other threads:[~2017-03-11 4:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 9:49 Warren Toomey
2017-03-10 10:29 ` [TUHS] pathalias and mail maps Warren Toomey
2017-03-10 10:49 ` Jacob Goense
2017-03-10 15:45 ` Erik E. Fair
2017-03-10 17:52 ` [TUHS] C-news is built John Floren
2017-03-10 21:14 ` Nick Downing
2017-03-10 21:30 ` Henry Bent
2017-03-10 21:51 ` Nick Downing
2017-03-11 4:57 ` Jason Stevens [this message]
2017-03-10 21:34 ` Warren Toomey
2017-03-10 22:48 ` John Floren
2017-03-11 0:05 ` [TUHS] B-news source code Mary Ann Horton
2017-03-11 0:15 ` Larry McVoy
2017-03-11 2:21 ` Mary Ann Horton
2017-03-11 4:20 ` Dan Cross
2017-03-11 3:01 ` Warren Toomey
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=DAFBD8E8-4BD1-451A-8B58-397DC1FC1E0A@superglobalmegacorp.com \
--to=jsteve@superglobalmegacorp.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).