<?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 Re: RHEL5 and /proc in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/rhel5-and-proc/m-p/4459867#M37498</link>
    <description>The drivers included into Linux kernel tend to use /sys, but some external driver packages (e.g. the HP-packaged QLogic HBA driver) may still use /proc.&lt;BR /&gt;&lt;BR /&gt;If the thing you wish to manipulate exists within /sys, use it; else use /proc as before.&lt;BR /&gt;&lt;BR /&gt;MK</description>
    <pubDate>Wed, 15 Jul 2009 05:26:35 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2009-07-15T05:26:35Z</dc:date>
    <item>
      <title>RHEL5 and /proc</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rhel5-and-proc/m-p/4459865#M37496</link>
      <description>Dear all,&lt;BR /&gt;&lt;BR /&gt;how far is it true that RHEL5 does/should not use /proc based device manipulation. &lt;BR /&gt;In other words, we should use /sys based manipulation for FC related devices. Correct ?&lt;BR /&gt;&lt;BR /&gt;cheers</description>
      <pubDate>Wed, 15 Jul 2009 04:18:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rhel5-and-proc/m-p/4459865#M37496</guid>
      <dc:creator>ossupport55</dc:creator>
      <dc:date>2009-07-15T04:18:15Z</dc:date>
    </item>
    <item>
      <title>Re: RHEL5 and /proc</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rhel5-and-proc/m-p/4459866#M37497</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;on our Centos 5.2 == RHEL 5.2,&lt;BR /&gt;&lt;BR /&gt;the fc manipullation is in /sys&lt;BR /&gt;&lt;BR /&gt;/sys/class/fc_host&lt;BR /&gt;&lt;BR /&gt;host*/&lt;BR /&gt;&lt;BR /&gt;for example :&lt;BR /&gt;&lt;BR /&gt;/sys/class/fc_host/host3/device/scsi_host:host3&lt;BR /&gt;&lt;BR /&gt;mikap</description>
      <pubDate>Wed, 15 Jul 2009 04:30:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rhel5-and-proc/m-p/4459866#M37497</guid>
      <dc:creator>Michal Kapalka (mikap)</dc:creator>
      <dc:date>2009-07-15T04:30:23Z</dc:date>
    </item>
    <item>
      <title>Re: RHEL5 and /proc</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rhel5-and-proc/m-p/4459867#M37498</link>
      <description>The drivers included into Linux kernel tend to use /sys, but some external driver packages (e.g. the HP-packaged QLogic HBA driver) may still use /proc.&lt;BR /&gt;&lt;BR /&gt;If the thing you wish to manipulate exists within /sys, use it; else use /proc as before.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Wed, 15 Jul 2009 05:26:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rhel5-and-proc/m-p/4459867#M37498</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2009-07-15T05:26:35Z</dc:date>
    </item>
    <item>
      <title>Re: RHEL5 and /proc</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rhel5-and-proc/m-p/4459868#M37499</link>
      <description>Thanks guys for the replies.&lt;BR /&gt;&lt;BR /&gt;Well, what i was baffled was the new implementations of RHEL5, qlogic driver actually does stuff through /proc. Should i use that or is it safe for me to use the inbox driver?&lt;BR /&gt;&lt;BR /&gt;Since i'm planning to use fibreutils what is recomended ?&lt;BR /&gt;&lt;BR /&gt;cheers folks</description>
      <pubDate>Wed, 15 Jul 2009 11:08:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rhel5-and-proc/m-p/4459868#M37499</guid>
      <dc:creator>ossupport55</dc:creator>
      <dc:date>2009-07-15T11:08:14Z</dc:date>
    </item>
    <item>
      <title>Re: RHEL5 and /proc</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rhel5-and-proc/m-p/4459869#M37500</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;i think it's up to you.&lt;BR /&gt;&lt;BR /&gt;mikap</description>
      <pubDate>Wed, 15 Jul 2009 11:09:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rhel5-and-proc/m-p/4459869#M37500</guid>
      <dc:creator>Michal Kapalka (mikap)</dc:creator>
      <dc:date>2009-07-15T11:09:38Z</dc:date>
    </item>
    <item>
      <title>Re: RHEL5 and /proc</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rhel5-and-proc/m-p/4459870#M37501</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;I would simply install drivers and use their default location.  /proc is aptly named, contains process information, kernel parameters and other such things.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 15 Jul 2009 11:27:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rhel5-and-proc/m-p/4459870#M37501</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2009-07-15T11:27:30Z</dc:date>
    </item>
  </channel>
</rss>

