(sorry for the late reply - just saw this....)

According to Robert Elz:
>
>    From:        Matthew Jacob <mjacob@feral.com>
>    Message-ID:  <Pine.BSF.4.10.10007061149070.20481-100000@beppo.feral.com>
>
>  | What we should have is something *like* prtconf that can print
>  | a device's h/w infrastructure from userland.
>
>I agree, that would be nice,

What, you mean like this:

[root@siren] prtconf
System is a i386 architecture on a Intel Pentium Pro (686-class)
  with 100270080 bytes of physical memory, 96485376 bytes is
non-kernel memory

mainbus0
   pnpbios0
   pci0
      pchb0 (device = 0, function = 0)
      pcib0 (device = 1, function = 0)
         isa0
            com0 (irq = 4, port = 0x3f8)
            com1 (irq = 3, port = 0x2f8)
            pckbc0 (port = 0x60)
               pckbd0
                  wskbd0
               pmsi0
                  wsmouse0
            pcppi0 (port = 0x61)
               sysbeep0
            isapnp0 (port = 0x279)
               pcic0 (port = 0x3e0)
                  pcmcia0
                  pcmcia1
                     wi0 (port = 0x400, function = 1024)
               sb0 (irq = 5, port = 0x220, drq = 1)
                  audio0
            npx0 (port = 0xf0)
            fdc0 (irq = 6, port = 0x3f0, drq = 2)
               fd0 (drive = 0)
      pciide0 (device = 1, function = 1)
         atapibus0
            cd1 (drive = 0)
      de0 (device = 9, function = 0)
      vga1 (device = 10, function = 0)
         wsdisplay0
      ahc0 (device = 13, function = 0)
         scsibus0
            sd0 (lun = 0)
            cd0 (lun = 0)
[root@siren] uname -a
NetBSD siren 1.5_ALPHA NetBSD 1.5_ALPHA (SIREN) #24: Sat Jul 22
21:24:04 CST 2000     toor@siren:/usr/src/sys/arch/i386/compile/SIREN
i386

Most of the above is done by walking the in-kernel device tree, I am
forced to parse dmesg output to get the locators.  My current version
will look for /var/run/dmesg.boot first and use it if it exists,
falling back to dmesg as a last resort.

> and certainly has its uses (for anyone
>who ever decides to do that, bonus points for actually being able to
>print the hardware section of a config(8) format file to match the
>current running system).
>

This is being struggled with - well, something that will build the
_whole_ config file for you.


Hmmm maybe it is time to prod core about putting prtconf into the
tree....

-- 
===============================================================================
Brett Lymn, Computer Systems Administrator, BAE SYSTEMS
===============================================================================