From: gtaylor@tnetconsulting.net (Grant Taylor)
Subject: [TUHS] 8th Edition Research Unix on SIMH
Date: Tue, 28 Mar 2017 19:02:09 -0600 [thread overview]
Message-ID: <66d1ab6c-1396-fa83-cb9d-2d87ab463be3@tnetconsulting.net> (raw)
In-Reply-To: <20170329004914.D997818C083@mercury.lcs.mit.edu>
On 03/28/2017 06:49 PM, Noel Chiappa wrote:
> But if people just have to press a button (basically), they won't learn
> anything. I guess I'm not understanding the point of the exercise? To say they
> have V6 running? So what? All they did was press a button. If it's to
> experience a retro-computing environment, well, a person who's never used one
> of these older systems is going to be kind of lost - what are they going to
> do, type 'ls -ls' and look at the output? Not very illuminating. (On V6,
> without learning 'ed', they can't even type in a small C program, and compile
> and run it.) Sorry, I don't mean to be cranky, but I'm not understanding the
> point.
Conceptually I agree.
However, I've had to teach enough people to know that they need a way to
boot strap themselves into an environment to start learning.
Thus I find having a streamlined process available to them to be
beneficial. Then once they have gotten a taste, presuming they like it,
they can go back and attempt to do more complicated things.
I do consider what (I believe) Warren put together for the UUCP project
to be a very good start. Simple how to style directions that are easy
to follow that yield a functional system.
Conversely, take a look at what's involved in IPLing a minimal MVS 3.8j
system in Hercules. (Ignoring the turn key packages.)
--
Grant. . . .
unix || die
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3717 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170328/9d8da5e0/attachment-0001.bin>
next prev parent reply other threads:[~2017-03-29 1:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 0:49 Noel Chiappa
2017-03-29 1:02 ` Grant Taylor [this message]
2017-03-29 10:41 ` Steffen Nurpmeso
2017-03-29 11:19 ` [TUHS] Release of 8th, 9th and 10th Editions Unix (was: Re: 8th Edition Research Unix on SIMH) Steffen Nurpmeso
2017-03-29 2:44 ` [TUHS] 8th Edition Research Unix on SIMH Tim Newsham
-- strict thread matches above, loose matches on Subject: below --
2017-04-27 1:04 Norman Wilson
2017-04-27 1:26 ` Kurt H Maier
2017-03-31 22:31 Nelson H. F. Beebe
2017-03-30 11:47 Jason Stevens
2017-03-29 1:45 Noel Chiappa
2017-03-29 1:57 ` Steve Nickolas
2017-03-29 4:11 ` Grant Taylor
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-04-26 3:05 ` 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
2017-04-26 23:02 ` Arthur Krewat
2017-04-26 23:21 ` Dave Horsfall
2017-04-26 23:07 ` 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=66d1ab6c-1396-fa83-cb9d-2d87ab463be3@tnetconsulting.net \
--to=gtaylor@tnetconsulting.net \
/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).