The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: bill@cs.scranton.edu (Bill Gunshannon)
Subject: [pups] 2.11 on an 11/44
Date: Thu, 27 Feb 2003 12:33:25 -0500 (EST)	[thread overview]
Message-ID: <20030227122420.S43050-100000@server1.cs.uofs.edu> (raw)
In-Reply-To: <Pine.LNX.4.21.0302271756420.8407-100000@Tempo.Update.UU.SE>

On Thu, 27 Feb 2003, Johnny Billquist wrote:

> On Thu, 27 Feb 2003, Bill Gunshannon wrote:
>
> > On Thu, 27 Feb 2003, Johnny Billquist wrote:
> >
> > > What do you see at boot time? Does it show all three RL02s and the
> > > mscp-controller along with disks?
> >
> > Actually, I am surprised by the lack of information provided.  I guess
> > the newer BSD's have spoiled me.  :-)
>
> [stuff deleted...]
>
> Hmmm. It's been a while since I ran 2.11, but I'm pretty sure you should
> see something about the controller at boot. That it attaches, it's csr and
> what vector it will use. The same way you observe the RL11 controller.

Hmmmm.  Curious.  I looked at the conf for GENERIC and it had all the
disks.  Maybe I need to build a kernel under SIMH and then move it over
to the real box.  Should be a trip, I've never built a kernel under 2.x.
Wonder how close it is to todays BSD's where I do it al the time.

>
> Seems like you don't have the controller available from the OS.
> Have you used the controller anywhere else, so that you know it's
> functioning, and that the CSR is set right?

Yup.  Had RSTS on it when I got it and I tried RT-11 from an
RL and was able to init Packs, copy files and even boot as a DU.
HA LI from the RSTS Startup reports iit's offspring as RA8x disks.


>
> About the RL drives, I guess we'll just have to assume that you don't have
> more than two units generated in the system,

The same kernel mounts all 4 RL02's under SIMH.  :-(

>                                             unless you have some very
> funny hardware problem.

Maybe I need to crawl in back and check out everything.  Could the
terminator getting knocked loose cause this??  It's interesting that
it isn't a particular drive that doesn't whow up, it is the highest
numbered unit.  Unless I am looking at this wrong.  Do the numbers
assigned by the Unit Plug coincide with the dev number or does it
just assign devices sequentially for each drive it sees?  In other
words, if I had a unit with a 0 plug and a 3 plug would that show
up as /dev/rl0 and /dev/rl3 or as /dev/rl0 and /dev/rl1?
Hope that's understandable....


bill

-- 
Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolves
bill at cs.scranton.edu     |  and a sheep voting on what's for dinner.
University of Scranton   |
Scranton, Pennsylvania   |         #include <std.disclaimer.h>




  reply	other threads:[~2003-02-27 17:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-27 15:08 Bill Gunshannon
2003-02-27 15:55 ` David Evans
2003-02-27 16:28 ` Johnny Billquist
2003-02-27 16:42   ` Bill Gunshannon
2003-02-27 16:59     ` Johnny Billquist
2003-02-27 17:33       ` Bill Gunshannon [this message]
2003-02-27 20:25         ` Bill Gunshannon
2003-03-01 21:36 ` Robin Birch
2003-02-27 15:57 Fred N. van Kempen
2003-02-27 16:02 ` Bill Gunshannon
2003-02-27 17:06 Steven M. Schultz
2003-03-01 14:06 Norman Wilson
2003-03-03  6:42 Steven M. Schultz

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=20030227122420.S43050-100000@server1.cs.uofs.edu \
    --to=bill@cs.scranton.edu \
    /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).