The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: iking@killthewabbit.org (Ian King)
Subject: Another happy customer (was Re: [pups] Bootable media for 2.11BSD)
Date: Sat, 8 Feb 2003 10:48:36 -0800	[thread overview]
Message-ID: <000401c2cfa2$b05e3210$450010ac@dawabbit> (raw)
In-Reply-To: <000401c2cecd$9d4186d0$7f0010ac@pepelepew>

It's amazing what happens when you follow the directions - thanks for your
help, folks.  I have 2.11BSD up and running on my 11/73 (booted off the
disk, even), and it's currently untarring the last big chunk of /usr/src.
(The docs mention that TK50s are slower than snot - believe it!)  The system
has two RD54s <woohoo!>, but I'm following the 'default' installation for
now until I have everything running and have successfully rebuilt the
kernel; then I'll probably move /usr and /tmp over to the second RD.  I also
need to dig into the machine a bit more - the bootloader tells me I have an
11/83, so I'm suspecting the CPU was changed at some point.

For the record, I live in Seattle, and I can now produce bootable TK50s with
2.11BSD.  :-)

-- Ian
----- Original Message -----
From: "Ian King" <iking@killthewabbit.org>
To: "Robin Birch" <robinb at ruffnready.co.uk>
Cc: <pups at minnie.tuhs.org>
Sent: Friday, February 07, 2003 9:23 AM
Subject: Re: [pups] Bootable media for 2.11BSD


> Yup, that's what I get for trying to be clever.  :-)  I built and ran
> maketape, and the 11/73 likes the resulting tape (boots).  So I'm remaking
> the tape with the tar's on it (per the instructions).
>
> I also happened to look at my work email, and saw the recent thread on
this
> same subject - doh!
>
> Maybe we should add something to the /2.11BSD distribution README with the
> caveats we've learned?  -- Ian
>
> ----- Original Message -----
> From: "Robin Birch" <robinb at ruffnready.co.uk>
> To: "Ian King" <iking at killthewabbit.org>
> Cc: <pups at minnie.tuhs.org>
> Sent: Friday, February 07, 2003 3:20 AM
> Subject: Re: [pups] Bootable media for 2.11BSD
>
>
> > Use the maketape program in the sys/pdpstand directory.  You can build
> > this on most things and use it to create a bootable tape with the
> > standalone system which contains all of the tools to set the system up.
> >
> > Cheers
> >
> > Robin
> >
> >
[snip]
> >
> > --
> > Robin Birch
> >
>
> _______________________________________________
> PUPS mailing list
> PUPS at minnie.tuhs.org
> http://minnie.tuhs.org/mailman/listinfo/pups




  reply	other threads:[~2003-02-08 18:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-07  8:18 [pups] Bootable media for 2.11BSD Ian King
2003-02-07 11:20 ` Robin Birch
2003-02-07 14:11   ` Chuck Dickman
2003-02-07 14:32     ` David Evans
2003-02-07 14:57       ` Chuck Dickman
2003-02-07 15:01         ` David Evans
2003-02-07 17:00     ` Robin Birch
2003-02-07 17:23   ` Ian King
2003-02-08 18:48     ` Ian King [this message]
2003-02-08 21:47       ` Another happy customer (was Re: [pups] Bootable media for 2.11BSD) David Evans
2003-02-07 13:53 ` [pups] Bootable media for 2.11BSD David Evans

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='000401c2cfa2$b05e3210$450010ac@dawabbit' \
    --to=iking@killthewabbit.org \
    /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).