BSD's devname() under Solaris

Ask a Question related to UNIX Programming, Design and Development.

  1. #1

    Default BSD's devname() under Solaris

    hi.

    i would like to extract the device name from a dev_t-datatype
    under solaris. under bsd i use devname() to do this but how
    does it work under solaris?

    stephan.
    Stephan Saß Guest

  2. Similar Questions and Discussions

    1. (Help) FTP fails in Solaris 9 but not in Solaris 2.6
      Our Sun E3500 server has been upgraded from Solaris 2.6 (105181-17 ) to Solaris 9 (112233-11). There are no changes in any of the FTP binaries. We...
    2. solaris 10 zone / container question (or Solaris 9)
      I begin to look at zoning in Solaris 10. I have not configured zones yet but need some answers quite quick (tomorrow :-() and hope someone can help...
    3. Question: C2 Security Configuration for general Unix and Solaris/Trusted Solaris (Auditing)
      While reviewing the DoD 5200.28-STD "DEPARTMENT OF DEFENSE TRUSTED COMPUTER SYSTEM EVALUATION CRITERIA" document and looking over "Security...
    4. RPC unknown host with Solaris 9 (not on Solaris 8)
      I am trying to see if a Solaris 8 application will work on Solaris 9. While it mostly works, I am still running into issues with RPC. I get error...
    5. upgrading solaris 2.6 to Solaris 8
      Hello, Last day I upgraded my solaris 2.6 to Solaris 8 on a E220R. After reboot the system boots with solaris 8 but ....it got stucks at...
  3. #2

    Default Re: BSD's devname() under Solaris

    Stephan Saß wrote:
    > i would like to extract the device name from a dev_t-datatype
    > under solaris. under bsd i use devname() to do this but how
    > does it work under solaris?
    i'm completely guessing here, but maybe this is useful:

    Solaris 8:

    root@zeus[/usr/include/sys] $ grep devnm *
    devinfo_impl.h:struct di_devnm {
    root@zeus[/usr/include/sys] $ grep devinfo *

    bpp_var.h: dev_info_t *dip; /* Opaque devinfo
    info. */
    dacf.h:dev_info_t *dacf_devinfo_node(dacf_infohdl_t);
    ddi_impldefs.h: kmutex_t devi_lock; /* Protects per-devinfo data
    */
    ddi_impldefs.h:/* devinfo node needs inital driver binding */
    ddi_impldefs.h: * It then gets attached to the devinfo node as a property.
    ddi_impldefs.h: dev_info_t *dip; /* pointer to devinfo node
    */
    devinfo_impl.h: * This file is separate from libdevinfo.h because the
    devinfo driver
    devinfo_impl.h:/* ioctl commands for devinfo driver */
    devinfo_impl.h: * devinfo driver snapshot data structure
    devinfo_impl.h: di_off_t top_devinfo;



    --
    ----- stephan beal
    Registered Linux User #71917 [url]http://counter.li.org[/url]
    I speak for myself, not my employer. Contents may
    be hot. Slippery when wet. Reading disclaimers makes
    you go blind. Writing them is worse. You have been Warned.

    stephan beal Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139