REQUEST: Listing device driver details on Tru64 Unix

From: <LHERCAUD_at_bouyguestelecom.fr>
Date: Mon, 30 Apr 2001 13:45:27 +0200

        Hi all,

        Regarding this summary, I was thinking it might be a nice feature if
        Tru64 had some "dev" entries in /proc for instance. Solaris and
Linux have it.

        Maybe if we (many) ask for it, Compaq will do it sooner ?

        Regards

        Lucien Hercaud

Lucien HERCAUD
Consultant Systeme UNIX en mission chez Bouygues Télécom
DSI / IPR / IRS / INF

* Tel. Fixe +33 1 3945 4260 * BOUYGUES Telecom
* Tel. Mobile +33 6 0944 2880 * 11 Avenue Maurane Saulnier
* Fax +33 1 3463 8551 * 78944 VELIZY Cedex
* lhercaud_at_bouyguestelecom.fr
mailto:lhercaud_at_mail.dotcom.fr


Reply from Dr.Thomas.Blinn_at_Compaq.com
--------------------------------------

You can't. There is no interface to do this. The closest thing is the
sysconfig interface, but it is generically for all kernel modules, not
just for device drivers, and there is no requirement on the people who
write device drivers that they export any particularly useful data via
that interface (most drivers are NOT configurable in any useful way via
the sysconfig interface).

For instance, if you want to know what drivers were delivered separately
from the base OS component, there is a file in /usr/sys/conf called
.product.list that gets used during a kernel build to incorporate
static-link drivers into the custom kernel;
but some drivers are loaded dynamically after the kernel boots, and they
are usually loaded via commands in a startup script in /sbin/init.d and
you need to know what to look for there..


Reply from alan_at_nabeth.cxo.dec.com
-----------------------------------

        You should also take a look at the manual page for the
        getsysinfo(2) system call. It has a set of codes for
        wandering through the I/O subsystem table, many of which
        have associated drivers. The data structure used by
        these codes may offer a clue what sort of information
        are easily available. Even if you can't a program yourself
        to step through the data structures, you could probably
        use dbx to examine the relevant data structures.

        The Monitor "names" feature uses these routines to generate
        the device listing. The most recent version of Monitor on
        ftp.digital.com (/pub/DEC/monitor.alpha.tar.Z) has an
        improved version of this feature.
Received on Mon Apr 30 2001 - 11:47:06 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:42 NZDT