[Info-vax] device nameing on a PWS500au

[FredK]

"H Vlems" <hvlems at freenet.de> wrote in message 
news:5ff84717-453b-4ab5-a66a-ef1a1f6dcf97 at z41g2000yqz.googlegroups.com...
On Dec 8, 10:44 pm, Steven Schweda <sms.antin... at gmail.com> wrote:
> Jim Mehlhop wrote:
> > I seem to remember an article (but I can't find it) about this. Here is
> > the situation on the console of the PWS500 my disks show up as dkb0-600
> > but when I boot vms they show up as dkC0-600. Seems to me there was
> > something in sysgen but I can't find it right now. Does anyone else
> > remember this?
>
> I don't remember much, but knowing how to spell "naming"
> makes it easier to find.
>
> http://groups.google.com/group/comp.os.vms/browse_thread/thread/27095...

Does that work too on a DEC 3000 model 400?
Hans


I believe the answer is yes.  The problem is that the typical way that you 
would walk the bus topology would be "depth first" - that is, when you hit a 
"device" (actually at this point the device is represented by an ADP) that 
is actually some type of bridge or subordinate bus - you would walk down it 
first, before stepping to the next peer on the current bus.  But the way the 
ADPs are built allows you to walk across the device list getting every 
device at the same level, and then the next, etc, without having to follow 
the child pointer.

I think the rationalization of the guy who wrote the original code was that 
he wanted to avoid recursive calls during the boot.  I worked with Tony to 
fix this, and I'm pretty sure (man this was a long time ago) that the 
Turbochannel was also fixed.