<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic device path identify in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/device-path-identify/m-p/4705489#M552312</link>
    <description>Dear Team,&lt;BR /&gt;&lt;BR /&gt;How to identify Device path? can u explain brief?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;P.Seenivasan</description>
    <pubDate>Wed, 27 Oct 2010 05:17:18 GMT</pubDate>
    <dc:creator>seenivasan</dc:creator>
    <dc:date>2010-10-27T05:17:18Z</dc:date>
    <item>
      <title>device path identify</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/device-path-identify/m-p/4705489#M552312</link>
      <description>Dear Team,&lt;BR /&gt;&lt;BR /&gt;How to identify Device path? can u explain brief?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;P.Seenivasan</description>
      <pubDate>Wed, 27 Oct 2010 05:17:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/device-path-identify/m-p/4705489#M552312</guid>
      <dc:creator>seenivasan</dc:creator>
      <dc:date>2010-10-27T05:17:18Z</dc:date>
    </item>
    <item>
      <title>Re: device path identify</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/device-path-identify/m-p/4705490#M552313</link>
      <description>Hi,&lt;BR /&gt;ioscan scans system hardware, usable I/O system devices, or kernel I/O system data structures as appropriate, and lists the results. For each hardware module on the system, ioscan displays by default  the hardware path to the hardware module, the class of the hardware module, and a brief description.&lt;BR /&gt;&lt;BR /&gt;By default, ioscan scans the system and lists all reportable hardware found. The types of hardware reported include processors, memory, interface cards and I/O devices. Scanning the hardware may cause drivers to be unbound and others bound in their place in order to match actual system hardware.&lt;BR /&gt;&lt;BR /&gt;Refer the attachment for more info...</description>
      <pubDate>Wed, 27 Oct 2010 05:45:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/device-path-identify/m-p/4705490#M552313</guid>
      <dc:creator>P Arumugavel</dc:creator>
      <dc:date>2010-10-27T05:45:24Z</dc:date>
    </item>
    <item>
      <title>Re: device path identify</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/device-path-identify/m-p/4705491#M552314</link>
      <description>See your other thread:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1453787" target="_blank"&gt;http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1453787&lt;/A&gt;</description>
      <pubDate>Wed, 27 Oct 2010 11:02:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/device-path-identify/m-p/4705491#M552314</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2010-10-27T11:02:28Z</dc:date>
    </item>
  </channel>
</rss>

