From owner-freebsd-arch Thu Jul 13 0:35:21 2000 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id 8745637BA99 for ; Thu, 13 Jul 2000 00:35:10 -0700 (PDT) (envelope-from nbm@sunesi.net) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13CdW3-000Bvc-00; Thu, 13 Jul 2000 09:34:39 +0200 Date: Thu, 13 Jul 2000 09:34:39 +0200 From: Neil Blakey-Milner To: Boris Popov Cc: Andrzej Bialecki , freebsd-arch@freebsd.org Subject: Re: SysctlFS Message-ID: <20000713093439.A45743@mithrandr.moria.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from bp@butya.kz on Thu, Jul 13, 2000 at 08:17:30AM +0700 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu 2000-07-13 (08:17), Boris Popov wrote: > So, internal fs can have structure like that: > > /bus - newbus tree > /sysctl - sysctl tree Once the "dynamic sysctls" hit the tree, I have been running a sysctl exportation of newbus information for a few weeks (months, possibly). There's also a "sysinfo" console program as a (badly written, since sysctl is a pain to manipulate) reference on how to extract information from it: root0 nexus0 pcib0 npx0 pci0 ... atapci0 ata0 ata1 eisa0: not present vga0 at port 0x3c0-0x3df iomem 0xa0000-0xbffff sc0 atkbdc0 at port 0x60,0x64 ... atpic0 at port 0x20-0x21,0xa0-0xa1 irq 2 sysresource4 at port 0x4d0-0x4d1,0x8000-0x803f,0x7000-0x700f It just grabs the information from the sysctl export: hw.devices.fdc0.desc: NEC 72065B or clone hw.devices.fdc0.children: fd0,fd1 hw.devices.fdc0.state: attached hw.devices.fdc0.irq: 6 hw.devices.fdc0.drq: 2 hw.devices.fdc0.ioport: 0x3f0-0x3f5,0x3f7 Windows-like Device Manager, anyone? Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message